• Hello,

    I found out that I can’t enter WPML translation interface. After a long session with WPML support they discovered that all that was needed to make WPML return to work is disable the “Add Admin CSS” on our website. I did so and WPML was back to work.

    How can this issue be resolved?

    Thank you

Viewing 1 replies (of 1 total)
  • Plugin Author ImageScott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Hi @balvan64,

    In order to troubleshoot this, we should first determine if there is a plugin-level conflict, or if the CSS you defined using the plugin is preventing things from being shown.

    So firstly, activate the Add Admin CSS plugin and go into its settings and delete anything that you’ve configured. (Create a copy of the CSS you may have provided if you want to add those back in later.) No CSS files should be linked and the “Admin CSS” field should be empty. Save those changes and try to access the WPML translation interface. Does it load? If not, then there is a plugin-level conflict that is out of your hands. Let me know if this is the case, and if you happen to have any error log entries from when you tried to access the WPML translation interface that may report any errors. (If none of that makes sense to you, simply report back that your issue was just from activating the plugin.)

    If the WPML translation interface loaded after you’ve activated the Add Admin CSS plugin and cleared its settings, then the conflict is probably with the CSS you defined. I’d reintroduce CSS in chunks or rule by rule, each time saving the changes and reloading the WPML translation interface page to see when it stops appearing. Hopefully you eventually introduce CSS that causes the issue, so you’ll know what it is and can change/omit it.

    If you are unfamiliar with CSS or don’t understand what I’m suggesting, feel free to say so but please provide a copy of the CSS you configured with the plugin and I can try to debug the problem.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.