Problem: The client is experiencing issues with the ATE UI not maintaining the selected version preference (old UI), as it reverts to the new UI after some time or following updates.
Solution: We suspect the issue might be related to browser caching. When switching between the new and old UIs in ATE, a parameter in the URL (i.e.,
ui=gen3
for new and
ui=legacy
for old) dictates which UI version to display. This setting should persist unless manually changed. We recommend clearing your browser cache to ensure this setting is applied correctly. Additionally, keep your plugins and themes updated to benefit from the latest fixes and improvements.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If problems persist, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client reported that after moving their website and assigning different keys to both sites, WPML continuously prompted them to select which site is the copy. This issue arose because the site at https://www.sceproject.it was using the same credits for automatic translation as the other site. Solution: We identified that the domain https://www.sceproject.it had an organization attached to it, whereas the https://newsceproject.rrulb.com/ did not. We advised the client to select "mark it as a copy" on the https://newsceproject.rrulb.com/ site if the popup appeared there. This action resolved the issue.
If this solution does not apply to your case, or if it seems outdated, we recommend checking the related 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: You are trying to translate a custom post type 'Staff' using WPML and Bricks Builder, but the layout disappears when viewed in the Italian language. Solution: Ensure that the Bricks Template used for your 'Staff' custom post type (CPT) is translated. Set the post type 'bricks_template' to 'Translatable - only show translated content' in the WPML settings under Post Type Translation. For detailed guidance on setting template conditions in Bricks Builder, visit Bricks Builder Template Settings. Additionally, check for any known issues with Bricks Builder and WPML at WPML Known Issues with Bricks Builder.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise checking related 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, please visit WPML Support Forum.
Problem: The client wants to have two different page layouts for different languages using WPML but encountered issues after initially using the translation editor. Solution: We recommend completing the translation by clicking the save button on each element to copy it from the original. After saving, delete the entire translation. Then, you can duplicate the page and follow the workflow as explained in our video tutorial here: https://www.loom.com/share/aa51354bb1ec448abf610a4d1149aeae.
If this solution does not resolve your issue or seems outdated, please check for related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if needed. For further assistance, you can contact us directly at WPML support forum.
Problem: The client is trying to translate posts made in Gutenberg using WPML and wants them to appear as one single text box in the Advanced Translation Editor. However, the translation is separating the content into different paragraphs. Solution: 1. In the Advanced Translation Editor, click on the settings icon (gear icon) located at the right top corner. Here, you will find an option to show 'Bigger segments'. 2. If the content still appears as separate paragraphs, you can use the merging chain to merge the paragraphs. Here is a helpful screenshot: https://prnt.sc/C5d-_x9J6en8 3. It is important to note that each paragraph in Gutenberg is treated as its own block, which WPML detects and maintains the same structure. Therefore, the largest segments that can be displayed are based on these individual blocks.
If this solution does not resolve your issue or seems outdated, we 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to translate text using WPML, but after translating several posts, the fields are no longer visible in the advanced translation editor. Solution: We found that the missing fields are part of the Bricks template, which has not been translated. To resolve this issue, please navigate to Bricks -> Template in your WordPress dashboard and translate the Post Detail template.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise checking the related 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, please visit our support forum.
Problem: The client is experiencing issues with page layout breaking when translating pages using WPML with Bricks Builder. The layout differences between the original and translated versions are significant. Solution: We identified that the title issue was due to the 'acf_hero_title' field not being updated in the Advanced Translation Editor. Updating this field should correct the title in the translated version. For the style issues, it relates to a known problem described in our errata for Bricks Builder where translated content does not display correctly on the frontend. We applied a temporary workaround as described in the errata. Please check the following demonstration video for a guide on how to apply these fixes: https://www.loom.com/share/2a64a15e6c254656bd835e1170da90bb If you're experiencing this issue, we recommend trying the steps outlined above. However, this solution might be 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 at WPML support forum.
Problem: The client wants to know if they can export pages using WP All Export PRO to a Google Sheet, translate them, and then re-import them as Excel to manage multilingual content. Solution: We recommend using the WPML Export and Import Addon plugin to facilitate the export and import process of multilingual content. Here are the steps to follow: 1. Export pages with WP All Export PRO to a Google Sheet. 2. Translate the content in the Google Sheet. 3. Save the translations as an Excel file. 4. Import the Excel file using a compatible import tool. For detailed guidance on using the WPML Export and Import Addon, please refer to the documentation and video tutorial here: https://wpml.org/documentation/related-projects/wpml-export-and-import/ Additionally, you can find more information about exporting with WP All Export here: https://www.wpallimport.com/documentation/how-to-export-wordpress-csv-excel-xml/
If this solution does not apply to your case, or if it 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 further assistance is needed, please open a new support ticket at WPML support forum.
