Problem: The client reported two issues on their production site: URLs for French and Spanish product sub-menus were in English, and the French translation of some product or product category pages caused the search bar to disappear and display odd icons. Solution: We suggested the client to record a screen capture using Loom to better illustrate the issue. It was identified that the code blocks for the French header were broken, which likely caused the display issues. We recommended replicating the issue on a sandbox site for further debugging without affecting the production site. The client was also advised to create a separate staging environment with minimal plugins to isolate the problem. After navigating to specific admin pages and completing the translation, the header issue was resolved.
Please note that this solution might be outdated or not applicable 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is using the AVADA theme for the mega menu option on their site and has noticed that the main category menu item names are not getting translated in both languages, despite being translated already in the WPML String Translation and Taxonomy Translation sections. Solution: 1. We recommended translating the links manually using the Advanced Translation Editor. The client should use the search form in the Advanced Translation Editor to locate and translate the links. 2. For static links, which the client is using, manual translation is necessary. We provided guidance on how to manually translate these links. 3. We suggested using dynamic content options for links, as explained in the Avada documentation (https://avada.com/documentation/how-to-use-dynamic-content-options-in-avada/), which would allow WPML to adjust the links automatically. 4. We also advised searching for category names or slug titles that might not include http or https, and translating them accordingly. 5. We manually saved some translations for the client that were not previously saved, ensuring they are now 100% complete for both languages. 6. We added custom XML configuration to help translate all links, instructing the client to search, translate, and save all links.
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 (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 open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with bulk translations using WPML, resulting in a 504 error even when translating a single post. Credits are being utilized despite these errors, and URLs are showing a '?' at the end of the slug after using WPML. Solution: We recommend increasing the
1
max_execution_time
to 300. This adjustment was tested by sending 20 jobs at once and it worked as expected. It's also advised to consult with your hosting provider to explore why the 'Bad Gateway' error occurs, particularly to check if large queries are being restricted by the server. Starting with smaller batches of up to five may also help mitigate the issue.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
