Problem: You are experiencing a Divi Timeout Error when trying to edit translated Divi Builder Template pages in the backend, resulting in a 404 page instead of the template. This issue occurs when the WPML plugin is active. Solution: To resolve this issue, follow these steps: 1. Ensure you edit the Divi Template in the site's default language using the Divi Theme Builder. 2. To translate the template, go to WPML > Translation Management. Use the post type filter to select your template's post type (Header, Body, or Footer Template). 3. Create a translation job for the template and access it at WPML > Translation to translate the template using the WPML Translation Editor. 4. Avoid editing translations directly in Divi when using the WPML Translation Editor as your translation method. If you prefer to create translations directly in Divi, change the translation method to "WordPress Editor" in the right sidebar of the WordPress Editor.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket at WPML support forum.
Problem: After migrating a staging website to the live version, hreflang links still point to the staging site, causing issues with search engine indexing. Solution: If you're experiencing hreflang links pointing to your staging site after migration, we recommend the following steps: 1. Update URLs in Database: Use a tool like Better Search Replace or WP-CLI to replace all instances of the staging URL with the live URL. For Better Search Replace, install and activate the plugin, go to Tools > Better Search Replace, search for the staging URL and replace it with the live URL, select all tables, perform a dry run first, and then run the actual replacement if everything looks good. For WP-CLI, use the command:
2. Clear Caches: After replacing URLs, clear any caches like page cache, object cache, or CDN. 3. Check Your Theme and Plugin Files: Ensure that your custom themes or plugins do not contain hardcoded staging URLs. Update them to dynamically use the site’s current URL. 4. Re-crawl and Verify: Re-crawl the live site with Screaming Frog to confirm that the hreflang tags now point to the live URLs. If this solution does not apply to your case, or if it seems outdated, 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. We highly recommend opening a new support ticket if you need further assistance: WPML Support Forum.
Problem: The client is unable to translate certain items in the navigation bar from English to Dutch, specifically 'Africa, Asia & Europe' under 'destinations' and titles within 'itineraries'. These strings are not appearing in the WPML string translation section. Solution: We recommend the following steps: 1) Export the Divi layout. 2) Delete the 'Menu-1-Destinations' in both languages and clear the basket. 3) Start from scratch, using English as the outgoing language. 4) Import your existing layout and then translate it to Dutch. 5) Begin the translation via the Translation Management, filtering for 'Layout' as described here.
If this solution does not resolve your issue or 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 here.
Problem: The client was experiencing timeouts in the Divi Builder due to conflicts with a plugin. Despite trying different PHP versions (7.4, 8.0, and 8.2), the issue persisted.
Solution: We tested by setting up a fresh sandbox site with WPML and Divi, and imported specific layouts which were then able to be edited without issues. We recommend the client to export all problematic layouts and import them again, ensuring to not override existing default website templates or assignments. It's crucial to take a full backup of the site and database before proceeding.
If this solution does not resolve the issue or seems outdated, please check related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we encourage opening a new support ticket.
Problem: The client's website content was incorrectly assigned to English after copying the Dutch content from an old website to a new one. Solution: We recommended two approaches depending on whether the client had already translated any content: 1. If no translations were made, we suggested re-installing WPML. 2. If translations existed, we advised duplicating the content in bulk from English to Dutch and then deleting the English content. We provided a documentation link for assistance: https://wpml.org/documentation/translating-your-contents/displaying-untranslated-content-on-pages-in-secondary-languages/#how-to-duplicate-pages-and-posts-in-bulk. After the client shared the necessary credentials, we proceeded with re-installing WPML and asked for confirmation that the issue was resolved and the languages were correctly assigned.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, we highly 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 with us.
