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.
