Problem: After installing WPML and attempting to manually edit a translated blog post using the WPML editor, the client found that clicking on any text within the editor resulted in a blank white page. Solution: We verified that the Advanced Translation Editor functions correctly on the client's site. The issue was that the Advanced Translation Editor was initially disabled for the page in question. We recommend enabling the Advanced Translation Editor when you encounter this issue. If you're experiencing similar problems, ensure that the Advanced Translation Editor is activated for the specific page you are trying to edit.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket.
Problem: The client is concerned about using a custom permalink structure (/blog/%postname%/) with WPML and whether it will cause issues, given that WPML recommends using /%year%/%monthnum%/%postname%/ for permalink structures.
Solution: We reassured the client that using the custom permalink structure /blog/%postname%/ should not cause any problems with WPML. WordPress supports the /%postname%/ directive well for all post types, and adding /blog/ simply prepends this to each post slug. For example, a standard post in English might appear as https://www.example.com/blog/hello-world/ and in Spanish as https://www.example.com/es/blog/hola-mundo/. Pages and custom post types will behave correctly too, with the language code consistently appearing right after the domain. We recommend testing any new configurations on a staging or development site before implementing them on a live site.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have the latest versions of themes and plugins installed. If problems persist, we highly recommend opening a new support ticket here.
