Problem: If you're experiencing issues with ATE where it opens but gets stuck loading, and eventually displays an 'Execution Expired' error, this might be due to specific translation units containing large sections of encoded data. This problem was identified when the ATE failed to load the homepage, despite other pages working correctly. Solution: We recommend checking any content-heavy sections on your page for encoded data. For instance, if you have custom CSS in blocks like sliders where images are embedded directly as encoded (base64) data, update this to use a standard image URL from your Media Library. This change should reduce the size of the translation unit, allowing the page to be sent to ATE without issues. After making these adjustments, please attempt to send the page to translation again.
If this solution does not resolve your issue or seems outdated, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket.
Problem: If you're experiencing an issue where WPML seems to be stripping the semicolon from the custom URL field link in your website, particularly noticeable when hovering over a CTA button where the URL changes unexpectedly. Solution: We recommend checking the setup in your page builder and content template. Specifically, you should: 1. Go to the Advanced Translation Editor for the affected page. 2. Search for the URL in the search bar at the top section and ensure the translated version is correct. 3. If the issue persists, the problem might not be directly related to WPML but rather to how the URL is being handled in your content template. For instance, if you are using Elementor with a Toolset custom field, ensure that the URL is not inserted as a raw shortcode. Instead, use Elementor’s dynamic link source to correctly reference the custom field. 4. Apply this change in both the original and translated templates to ensure consistency across languages.
If this solution does not resolve the issue or seems irrelevant due to updates or different configurations, 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 problems persist, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to see the translated strings on the frontend, even though they are translated in the WPML String Translation. The strings are related to admin texts (options saved in the database). Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Navigate to WPML → String Translation → Translate texts in admin screens. 2. Search for the option related to the plugin, which usually starts with 'wcrp_' or similar. 3. Select the relevant fields (labels) and add them for translation. 4. Return to the String Translation page and translate those strings. This process should ensure that the translated values appear on the frontend.
Please note that this solution might be outdated or not applicable to your specific 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 at WPML support forum for further assistance.
Problem:
Updating English translation on ACF option page results in the following fatal error .../httpdocs/wp-content/plugins/acfml/classes/Options/EditorHooks.php rivillä 328
Solution:
Make sure to enable WPML string Translations plugin to solve the issue.
