An update: The issue is getting worse. Today, I checked the website again on incognito and found that a lot of products were affected by the issue. So I deactivated the English and Swedish in WPML and cleared the cache. The issue seems to not be present any more. However, if the website cannot be translated without having this kind of troubles, I think removing WPML is the option I'll choose. Do you think you can find and fix the issue?
It seems there might have been a misunderstanding in my previous message. The issue persists when the "LiteSpeed Cache" plugin is active. Could you please confirm if the issue disappears when the "LiteSpeed Cache" plugin is temporarily deactivated? From what I see, only other caching mechanisms, like "Riised Performance," have been deactivated.
1) Please test the behavior with LiteSpeed Cache turned OFF.
2) Let me know if the issue is temporarily resolved once this plugin is deactivated or if you notice the behavior on other products.
To clarify the other points:
The deactivation wasn’t necessary, as the issue resolves when LiteSpeed Cache is deactivated. There’s no need to revisit previously established information.
I must just also point out that this is not something connected directly to WPBakery elements.
It seems there might be some confusion here. I said the issue only affects the frontend via WPBakery, confirming it’s caching-related. The database URL is correct, and there’s no issue with the permalink saved in the database.
I also must point out that the issues started somewhat at the same time you warned about some issues with WooCommerce. Could it be there is a connection?
I don’t recall sending a warning about a WooCommerce issue. Could you clarify what you mean by "a recent WooCommerce issue warning"? I'd be happy to look into it further with more details.
...I think removing WPML is the option I'll choose. Do you think you can find and fix the issue?
Could you verify this again on your end? If the issue persists, we can explore reaching out to the LiteSpeed authors for assistance. Since the problem disappears without caching, and the database values are correct, this doesn’t appear to be an issue with WPML.
I can test tonight what happens without LiteSpeed.
Here is the mail about the issue. I remebmered incorrect, it wasn't issue with Woocommerce, it was with WordPress:
Hi Diana,
WordPress 6.7 introduced some issues that might affect multilingual sites. WPML does not cause these issues but they may impact translations on your site, and we want to help you address them.
Symptoms You May Notice
1. Missing translations for strings: When using the site in languages other than English, some translations for strings (not your content, only theme and plugin strings) may be displayed in English.
2. PHP Notices: You may see the error in your debug log and if debug display is enabled, you might also see notices on your site’s front-end making your site appear broken. An example (domain name depends on the plugins you use):
PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce domain was triggered too early.
What You Should Do
To minimize the impact of these issues:
• Update all plugins and your theme: Keeping everything up to date may resolve some issues, though some problems might persist.
• Disable Debug Display on the front-end: Prevent errors from appearing on your site by turning off debug display.
What’s Next?
The WordPress team is aware of these issues and we expect a fix in WordPress 6.7.1. As soon as the update is available, we will test it thoroughly and share our findings with you.
Testing and Feedback
We’ve tested WordPress 6.7 extensively across multiple sites and configurations. While the issues seem to be unrelated to WPML, if you suspect WPML is contributing to a problem on your site, we encourage you to reach out. Open a support ticket so we can investigate and assist you.
We appreciate your patience and understanding. Please don’t hesitate to contact us if you need assistance or have further questions.
Thank you for clarifying what you meant. In your case, this isn't relevant. This applies only to strings, not page content, as they are stored in different database tables. This issue occurred due to a WordPress core change, but most plugins (like WooCommerce) are now compatible again.
Please let me know once you tested the issue without LiteSpeed cache.
I tested the website without the LiteSpeed cache. I did not stumble upon messed up URLs. While this isn't a guarantee that there weren't any - you experienced yourself that they can be overseen when examining the website, it might point to a cookie-cache problem. Can there be a solution that does not include removing LiteSpeed cache? It is simply the only plugin making the website work as it should with WPML on.
I’d recommend keeping it deactivated for a few days and seeing if any other issues arise. I wouldn’t say it’s a cookie-related problem, as I also tested this with my browser set to block cookies by default ("Do Not Track" mode) logged-out.
I don’t see an immediate need to remove LiteSpeed. The next step should be to reproduce the issue from scratch so we can prepare a code workaround for LiteSpeed Cache and potentially get it merged into their codebase.
It is simply the only plugin making the website work as it should with WPML on.
