ATE

Problem:
The client is experiencing issues with WooCommerce pages (Account, Cart, Checkout) not displaying in selected languages and the mobile language switcher behaving abnormally (opening sideways, hiding options).
Solution:
1. Verify and translate WooCommerce pages:
- Navigate to Pages in WordPress admin.
- Locate the Cart, Checkout, and My Account pages.
- Ensure there is a translation for each language using the plus (+) icon to add translations if missing.
2. Translate Cart and Checkout strings:
- Go to WPML → Translation Dashboard.
- Under Other texts (Strings), select your theme or WooCommerce domain from the All domains dropdown.
- Translate any missing Cart/Checkout/account-related strings.
3. Adjust menus and links:
- Ensure WordPress menus for each language link to the correct translated pages.
- Update any hard-coded links to use WooCommerce functions like

wc_get_page_id('cart')

for WPML to switch URLs automatically.
4. Fix mobile language switcher:
- Navigate to WPML → Languages → Language switcher options.
- Try a different style (dropdown vs. list) if using a menu language switcher.
- Consider using the built-in WPML switcher if using a widget or custom switcher.
- Adjust theme CSS if it affects the switcher dropdown visibility.
5. Disable language redirect notices:
- Check theme and plugin settings for any language redirect options and disable them.

If these steps do not resolve the issues, or if new issues arise, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML support forum.

Problem:
Some pages display as 100% auto-translated in the backend, but when viewed in the Arabic version, they still appear in English.
Solution:
If you're experiencing this issue, we recommend you try the following steps:
1. Edit the pages in the original language.
2. Make a small change to the content.
3. Save the changes.
4. Go to WPML -> Translation Management, select the content, and send it for translation.
5. Double-check if the content was correctly translated.

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 the issue persists, please open a new support ticket at WPML support forum.

Problem:
The client experienced a loss of translation credits after refreshing their staging website and switching from the WPML Advanced Translation Editor (ATE) to the Classic Editor. They were concerned about the loss of previously used credits and the inability to reuse translations.
Solution:
We advised the client to switch back to the WPML Advanced Translation Editor, which includes a translation memory feature. This feature allows previously translated content to be reused without additional charges, potentially resolving the issue of lost credits. We provided documentation on how WPML tracks translations (here) and on the Advanced Translation Editor (here). We also suggested creating a full site backup before making changes to the settings.

If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest checking related known issues (here), 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:
You are experiencing issues with the Advanced Translation Editor (ATE) in WPML while working on larger Elementor pages/templates. Specifically, you encounter error messages stating 'Unable to retrieve job details' and 'File Size Limit exceeded – Failed to parse because your job is above file limit of 1MB'. This prevents you from opening or reviewing translations in ATE.
Solution:
If you're encountering these issues, we recommend checking if your page contains custom JS code, as WPML might attempt to translate it, leading to these errors. To resolve or restart translation jobs without losing existing translations, consider reducing the size of the Elementor pages/templates by removing or simplifying any unnecessary elements or custom code. If these steps do not resolve the issue, it might be due to an outdated solution or a different problem not covered here. 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 with us for further assistance.

Problème :
Vous essayez de traduire automatiquement vos chaînes personnalisées, mais vous rencontrez l'erreur "Call to undefined function env()". Vous souhaitez savoir pourquoi la fonction env() n'est pas définie et comment résoudre cette erreur de traduction.
Solution :
Nous vous recommandons d'augmenter la valeur de WP_MEMORY_LIMIT dans votre fichier wp-config.php pour résoudre le problème. Ajoutez la ligne suivante avant la ligne /* C'est tout, n'éditez plus ! Bonne publication. */:

define('WP_MEMORY_LIMIT', '256M');

Si cette solution ne résout pas votre problème ou si elle semble dépassée, nous vous conseillons de vérifier les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.