Problem: The Slider Revolution (SR7) homepage slider works correctly on the English version of the site but fails on the German and Romanian translations. The issue manifests as the slider not appearing on the frontend of the translated pages, and JavaScript errors indicating 'Cannot read properties of undefined (reading 'slide')' are observed in the browser console. Solution: We have identified that the current version of Slider Revolution (SR7) is not fully compatible with WPML. To resolve this issue, we recommend downgrading to a previous version of Slider Revolution that is known to be compatible. You can confirm the compatible versions and detailed steps for setting up multilingual sliders by referring to our guide on creating multilingual sliders with Revolution Slider and WPML.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, you can contact us directly through the WPML support forum.
Problem: After a recent WPML update, the Translation Editor no longer recognizes newly added or updated file links as translatable fields in both the Advanced Translation Editor (ATE) and the Classic Translation Editor. This issue affects file links embedded using Divi modules, where previously these links appeared as "Link Option Url, Url" fields allowing for language-specific versions. However, links embedded before the update are still recognized correctly.
Solution: If you're experiencing this issue, we recommend trying to locate the URLs by typing "http" in the top right section of the Advanced Translation Editor. This might help in identifying the links that are not automatically recognized as translatable fields post-update.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket.
