language direction

Hi @dorsaf ,

hope you’re fine. Sorry for the late answer. It seems that you’re problem come from css generation.

in translate page you load this css : siteground-optimizer-combined-css-98126e00344d8dfa5c6db2c9da5e6c39.css and on default language you load this css : siteground-optimizer-combined-css-ae55c276cefed9c1cb0670bc9704f585.css

Can you try to disable you’re plugin who generate minified version of your CSS. It able me to see where the problem come from

Best

hi

I don’t know what the plugin is, but i found plugin named “code Snippets” and i disactivate it.

thank you.

I contacted weglot but they couldn’t help me and they told me to contact a wordpress expert.

@dorsaf

You should not have sent any login credentials to your site.

@glx77

I archived your reply. Could you stop doing that please? I would really feel bad if your account was banned from this site for you actions.

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.

Given the number of such review replies you’ve posted, you’ve been placed on “modwatch” until we’re convinced such postings have stopped. Your account has *not* been banned, we just want to check things for a while before they’re public. If you wish to take issue with this, contact moderators via the #forums channel on slack (https://make.www.ads-software.com/slack)