Problem: 1) The client is experiencing an issue with joining segments in translations, which requires redoing the joins every time an edit is made in the original language. 2) The client wants to preserve the URL slug in the original language for translations, but the slug is being automatically generated based on the translated title.
Solution: 1) We acknowledge the inconvenience caused by the joining segments issue and confirm that our development team is currently working on a solution. 2) To ensure the URL slug is copied from the original language, please follow these steps: - Go to WPML -> Settings -> Translated documents options -> Page URL - Select
Copy from original language if translation language uses encoded URLs
- Navigate to WPML -> Languages -> Edit languages - Set
Encode URLs
to
Yes
- Test this configuration by creating a new page and translating it to see if the issue is resolved.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. 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. Should you need further assistance, please do not hesitate to open a new support ticket. You can reach out to us through the WPML support forum.
Problem:
If you're experiencing an issue where an Elementor button points to a page and does not switch to the respective language when changing languages, staying directed at the default English language instead.
Solution:
First, ensure that the template containing the button is translated. Follow these steps:
1. Navigate to Templates -> All -> Header in your WordPress dashboard.
2. Use the translation editor to translate the header template.
After translating the header template, the button should correctly point to the translated post. For further guidance, we recommend checking our guide on translating Elementor templates.
If the button still does not work correctly after these steps, or if you encounter additional issues such as with the query loop, we suggest opening a new support ticket for each separate issue.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. We highly recommend checking related known issues on the WPML known issues page, 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.
