Problem: The client was unable to open the Elementor editor for a translated page/template, resulting in a 403 Forbidden error and an uncaught TypeError. Solution: The client said he had found a folder named /he/ on the server. Removing this folder solved the problem. If this solution is 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 issues persist, please open a new support ticket at WPML support forum.
Problem: The client is experiencing two main issues with a translated contact form. First, the dropdown options in the form are not fully displayed in the translated version. Second, the link to the privacy policy page is not correctly pointing to the translated version of the page. Solution: 1. For the dropdown options not displaying correctly, ensure that the options are correctly added and formatted in both the default and translated forms. You might need to update the default form to match the format shown in this demo, and then resend the form for translation. 2. For the incorrect privacy policy link, the link should be translated through the Translation Editor. In the Translation Editor, find the paragraph where the link is added, unlock the field with the lock icon, update it with the translated page link, and save the translation. If these steps do not resolve the issues or if the solution 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 the problem persists, please open a new support ticket.
