Problem: The client reported two issues: 1. Text on the homepage added under 'TestHome' does not translate when switching languages. 2. The 'Apus Listings Search Form' Elementor widget does not translate its content accordingly. Solution: For the first issue, we recommended the following steps to ensure the text translates correctly: 1. Go to WPML → String Translation. 2. Enable the option to auto-register untranslated strings. 3. Navigate to the page where the untranslated strings are displayed. 4. Return to WPML → String Translation, disable the option, and check if the given text has been registered. 5. Translate the text. For more details, visit https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/ For the second issue, it appears the 'Apus Listings Search Form' Elementor widget is not registered for translation. We suggested registering the widget using the Multilingual Tools Plugin. Here are the resources to assist with the process:
If these solutions do not resolve your issues or seem outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: When switching the site language to English and clicking on the logo, instead of redirecting to the homepage, it leads to a different page or shows a 404 error. Solution: This issue occurs because the homepage has not been translated into the secondary language (English). When the site is translated, the homepage URL changes to include language parameters, such as
https://your-site.al/?lang=en
or
https://your-site.al/en/
. To resolve this, you need to translate the homepage into English. Once translated, clicking the logo in the English version will correctly redirect to the English homepage instead of showing a 404 error.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: If you're experiencing issues where translating your website from Albanian to English in the WPML dashboard backend destroys the layout of your page, it might be due to the non-transfer of custom fields that contain layout settings. Solution: We recommend following these steps to ensure that the layout settings are preserved in the translation: 1. Navigate to WPML → Settings → Custom Fields Translation, and activate the option labeled "Show 'Multilingual Content Setup' meta box on post edit screen." 2. Edit the original page with the broken layout. 3. At the bottom of the page, click on "Show system fields". 4. Identify the custom fields related to your theme that might contain layout settings and set them to "Copy". 5. Make a slight modification to the original page and save your changes. 6. Complete the translation using the WPML translation editor. For more detailed guidance on translating custom fields, visit Translating Custom Fields. If the problem persists, please provide debug information by following the instructions here: Provide Debug Information.
Please note that this solution might be irrelevant if it's 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 you still need assistance, please open a new support ticket at WPML support forum.
