Problem: The customer translated the placeholder 'Search here..' from the 'Ajax Search Lite' plugin into French, English, and traditional Chinese. The default language of the site is French. Despite translating the placeholder into multiple languages, the French translation ('Chercher') appears in all languages instead of the respective translations. This issue corrects itself when the 'Auto-register strings' option is activated but reverts back to displaying the French translation when the option is deactivated. Solution: If you're experiencing this issue, we recommend you try the following steps: - Go to WPML > Theme and plugin localization - Check the "Automatically load the theme's .mo file using 'load_textdomain'" box - Add the textdomain (probably "ajax-search-lite and/or ajax-search-pro") to the "Enter textdomain" field then save - Scroll down and scan the theme/plugin - Go to WPML > Support > Troubleshooting - Click on "Show custom MO Files Pre-generation dialog box" - Refresh the page (It should display the MO files dialog box) - Regenerate the MO Files
If this solution does not resolve the issue, it 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problème :
Le client rencontre un problème avec des pages protégées par mot de passe qui retournent une erreur 404 sur son site WordPress utilisant WPML. Même après avoir désactivé l'option "Permettre les pages de connexion et d'inscription" dans les paramètres WPML, le site renvoie une erreur 500. Le client souhaite résoudre l'accès aux pages protégées par mot de passe sans avoir à traduire les pages d'inscription et d'authentification ou modifier les règles du serveur.
Si ces étapes ne résolvent pas le problème, ou si la solution semble obsolète ou inapplicable à votre cas, nous vous recommandons de consulter les problèmes connus et de vérifier la version de la correction permanente. Assurez-vous également que vous avez installé les dernières versions des thèmes et des plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur le forum de support WPML.
Problem: The client is experiencing a 404 error when trying to access password-protected pages on their WordPress site using WPML.
Solution: We attempted to reproduce the issue on a test site without success, indicating that the problem is not due to WordPress password protection and WPML compatibility. We then: 1. Deactivated all plugins related to Simple membership without success. 2. Deactivated Locotranslate to check for a conflict with translation plugins. 3. Switched the theme to WP 2019, which resolved the error. Upon inspecting the client's parent theme's functions.php file, we found a custom function named wpb_password_post_filter at line 472. Commenting out this function resolved the 404 error. This function is not part of WordPress or WPML, so we advised the client to either remove or modify it and to contact the theme's author for further assistance.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still facing issues, 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.
