Problem: The client reported that after adding local landing pages with a Custom Post Type (CPT), some pages in French were not accessible anymore, showing 404 errors. The issue seemed related to URL conflicts between the CPT and existing pages. Solution: We recommended the client to first try re-saving permalinks in Settings → Permalinks to flush rewrite rules and to temporarily disable the Yoast SEO Premium to test if redirection rules were interfering. After further investigation, it was found that the issue was due to a conflict where the same slug was used for both a CPT and a page. The solution involved ensuring unique slugs for CPTs and pages. We advised checking and editing slugs at WPML > Settings > Post Types Translation.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was unable to translate the text of a page created with a template using ACF & CPT UI plugins, despite being able to translate slugs and meta titles/descriptions. Solution: We recommended that the client access the template used for the page by hovering over 'Edit with Elementor' on the top admin bar when the page is open. Alternatively, the client can navigate to WPML → Translation Dashboard, locate the template, and send it for translation. For more details, we suggested visiting the WPML documentation on Elementor compatibility.
If this solution does not resolve the issue or seems outdated, or if it does not apply 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. Should further assistance be needed, please open a new support ticket at WPML support forum.
Problem: After migrating a multi-lingual site to a new production server, the backend became very slow, primarily due to frequent API calls made by the WPML Multilingual CMS plugin, resulting in '426 Upgrade Required' errors. Solution: First, ensure that all WPML plugins are updated to their latest versions. Next, within the WPML settings, switch the translation editor as this might resolve the issue temporarily. Additionally, check WPML logs for repeated API requests and review server resource usage to identify any loops or redundant external calls. If these steps do not alleviate the problem, it may be due to a bug that our developers are currently investigating. In this case, switching the translation editor as per the instructions in WPML → Settings should serve as a temporary workaround.
Please note that this solution might become outdated or may not apply to your specific situation. If the issue persists, 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 necessary, please do not hesitate to open a new support ticket.
