Documentation request

Problem:
You are using WPML to translate your website and have encountered two issues: 1) WPML automatically appends '-ar' or the Arabic page title to the slug in Arabic translations, despite wanting to keep the slug in English for both languages. 2) You experience a 'too_many_requests_error' on Arabic product pages, which does not occur in English.

Solution:
For the issue of WPML appending '-ar' to slugs in Arabic translations, WordPress does not allow two categories with the same slug, which is why WPML adds the language code. However, you can bypass this by manually editing the slug. For guidance on how to do this, please visit Translating Post Categories and Custom Taxonomies.

Regarding the 'too_many_requests_error', this might be caused by redirection issues. You can check the product URL for redirection problems at Redirect Checker. It's also advisable to disable any unnecessary redirections or adjust server settings.

If these solutions do not resolve your issues or if they seem 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 at WPML support forum for further assistance.

Problem:
The client is unable to view pay-as-you-go invoices in the 'Payment history and invoices' tab as expected. Instead, they encounter a message stating 'No sites available.' This issue arises because the client's website URLs (production, staging, and local) are listed under separate Organization IDs in the backend.
Solution:
We reviewed the client's website URLs and found multiple entries in our system. To resolve the issue, we connected all entries under a single Organization ID that is most active with Pay As You Go services. This adjustment should allow the invoices to appear correctly in the 'Payment history and invoices' tab with the next generated invoice. If the problem persists, we recommend following the steps outlined in the documentation on using the Advanced Translation Editor when moving or using a copy of your site.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. We also 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. For further assistance, you can contact us directly through the WPML support forum.

Problem:
The client experienced a navigation issue on their website after selecting the Portuguese language option. The navigation broke, likely due to menu items being duplicated during a migration to new hosting.
Solution:
We manually corrected the menu for the Portuguese language by accessing the menu settings at WP > Appearance > Menu. We removed the duplicate menu items, which resolved the issue. If you're experiencing similar issues, we recommend checking your menu settings for any duplications and manually correcting them if necessary.

Please note that this solution might be 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 the problem persists, please open a new support ticket.

Problem:
The client was experiencing issues with WPML's auto-translate functionality where URLs were not correctly translated to reflect the new language, and certain English keywords were being automatically translated when they needed to remain untranslated.

Solution:
1. To ensure URLs are correctly translated, we recommended following the steps in our guide on translating page slugs, which can be found here: Translating Page Slugs Guide.
2. To prevent specific English keywords from being translated, we advised adding them as terms in the Glossary. Detailed instructions are available here: How to Create and Manage Glossary Entries.
3. For issues with untranslated elements in Elementor, we provided an XML configuration to register the necessary widgets and fields. This involved adding custom XML code under WPML -> Settings -> Custom XML Configuration tab.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific 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 further assistance is needed, please do not hesitate to open a new support ticket at WPML Support Forum.

Problem:
Wenn Sie auf Ihrer Seite mehrere benutzerdefinierte Felder mit demselben Namen verwenden, kann dies zu Konflikten führen. Dies betrifft insbesondere den Einsatz von Advanced Custom Fields (ACF) in Kombination mit WPML.
Solution:
Stellen Sie sicher, dass jedes benutzerdefinierte Feld in Ihren verschiedenen Feldgruppen einen eindeutigen Namen hat. Wenn Sie denselben Feldnamen für mehr als ein benutzerdefiniertes Feld verwenden, kann dies zu Problemen führen, da nicht alle Feldwerte im Erweiterten Übersetzungseditor angezeigt werden. Weitere Informationen finden Sie in unserer Dokumentation: Advanced Custom Fields (ACF) multilingual.

Sollten diese Schritte das Problem nicht lösen, empfehlen wir, den Feldnamen im Block und in der Gruppe anzupassen und erneut zu testen. Wenn das Problem weiterhin besteht, empfehlen wir, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen zu überprüfen (bekannte Probleme), die Version der dauerhaften Lösung zu überprüfen und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.