Problem: You are trying to translate an HTML/CSS table using the Advanced Translation Editor, but encounter issues where the CSS styling is lost during the translation process. Previously, the editor only showed the strings of each cell for translation, but now it affects the styling. Solution: The issue arises from the mix of CSS and HTML in the translation process. The Advanced Translation Editor is not designed to handle CSS, JavaScript, or PHP; it strips out HTML markup and merges it again after translating the strings. To resolve this, you should use the field for "Custom CSS" on the advanced tab of the HTML widget.
Alternative:
1. Remove the link tag and the CSS from the HTML you are translating to ensure the translation works as expected. 2. Separate concerns by including the CSS in a "Hello Elementor Child Theme". You can set up the child theme following this guide: Setting up the "Hello Elementor Child Theme" 3. Include the stylesheet in the theme file functions.php:
4. Move your CSS to a file at /css/custom-table.css.
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.
Problem: The client switched to the Advanced Translation Editor (ATE) but wanted to edit old translations that were done with the Classic Translation Editor (CTE) without losing them. They encountered issues where the CTE was not available for previously translated pages, and only a basic text field with HTML appeared instead of the usual editing options. Solution: We advised the client to ensure that the option 'Use also for old translations created with the classic editor' in WPML > Settings > Translation Editor is not checked. This setting should force old pages to use the CTE. However, for pages already edited in ATE, it's not possible to revert to CTE. For a broader solution, we provided SQL queries to update the database to set the editor to CTE for translations that were manually edited or initially set to use another editor:
UPDATE wp_icl_translate_job SET editor = 'wpml' WHERE editor LIKE 'wp'
This SQL command changes all entries marked as edited with the WordPress editor to indicate they were edited with the CTE. Similar updates can be applied for entries marked as ATE by modifying the condition in the SQL query.
If these steps do not resolve your issue or if the solution seems outdated, 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 open a new support ticket.
Problem: You are experiencing an issue where the classic translator replicates the first text field to every text field on a page after updating the plugins. Solution: We recommend updating your WPML plugins to the latest version (v4.7.2) to resolve this issue. You can update the plugins by navigating to Plugins -> Add new -> Commercial tab in your WordPress dashboard.
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 problem persists, please open a new support ticket.
Problem: If you're experiencing issues where changes made to your pages are not immediately visible on the live site, even after saving or translating from scratch, this might be due to a caching conflict with Elementor. Solution: First, ensure you back up your entire site. Then, follow these troubleshooting steps: 1) Navigate to WPML>>Support page and click on the Troubleshooting link. 2) On the Troubleshooting page, execute the following actions in the *Clean up* section, waiting for confirmation after each: - Clear the cache in WPML - Remove ghost entries from the translation tables - Fix element_type collation - Set language information - Fix WPML tables collation - Assign translation status to duplicated content - Fix terms count - Fix post type assignment - Cleanup and optimize string tables - Show custom MO Files Pre-generation dialog box>>Generate .Mo files If the issue persists, disable the Element Caching option in Elementor by going to Elementor>>Settings>>Features tab. We have also released an errata for this issue, which can be found here: https://wpml.org/errata/elementor-translated-pages-show-stale-content-after-being-updated/
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is unable to translate the form fields of WPForms using WPML String Translation as they do not appear in the translation interface. Solution: 1. Access the
wpml-forms-config.xml
file located in
.../wp-content/plugins/wpml-wpforms/
. 2. Edit line 57 of the file. 3. Replace the existing
4. Make a minor change to your form and attempt to translate it again. This should allow the previously missing address fields to appear for translation.
