Problem: The client was experiencing a 503 error in WordPress when using WPML, along with a PHP Fatal error related to the function
get_requested_lang()
. After reinstalling WPML, a new error appeared regarding the premature loading of translations, indicated by the function
_load_textdomain_just_in_time
. Additionally, the client noted slow loading times in the WooCommerce settings when WPML was active. Solution: We identified that the issues were not directly caused by WPML but were related to the latest changes in the WordPress core and possibly other third-party plugins or themes. We recommended the following steps: 1. Check the errata page for known issues: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/ 2. Re-upload the WPML plugin to ensure all files are correctly installed. 3. Create a full site backup before making any changes. 4. If the problem persists, we recommended opening a new support ticket for further assistance.
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: You are trying to translate the 'Name' field label on the WooCommerce Checkout page, but it is missing in the WPML String Translation after being accidentally deleted. Solution: To resolve this issue, we recommend trying the following methods: Method 1: Navigate to WPML > String Translation. At the bottom of the page, enable the checkbox labeled "Look for strings while pages are rendered". Then, visit the front end of the page where the 'Name' string appears, and return to WPML > String Translation to search for the string again. Method 2: If the string is not found in the WPML > String Translation, it might be categorized as an admin text string. You can find and translate admin text strings by following the steps outlined in our documentation: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
If these steps do not resolve your issue, or if the solution becomes outdated, 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 necessary, please open a new support ticket at https://wpml.org/forums/forum/english-support/ for further assistance.
Problem: You have successfully translated ACF custom fields, but they do not appear on the translated pages. Solution: We recommend installing the Advanced Custom Fields Multilingual (ACFML) plugin to ensure that your translated custom fields appear correctly on translated pages. For detailed guidance on installing and configuring ACFML, please visit this documentation.
If the solution provided here does not resolve your issue or seems outdated, 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where switching to the Spanish language on their website redirects them to the homepage instead of the translated Activity page. They have set up WPML and translated a custom post type (CPT) 'Cooking Classes' but encounter redirection and 'Invalid post type' errors. Solution: We recommend the following steps to troubleshoot and resolve the issue: Ensure that the custom post type 'Tours' is properly configured for translation in WPML. Go to ACF > POST TYPES > TOURS > EDIT, select WPML translation Editor, and click the + sign to translate it. If these steps do not resolve the issue or if you encounter further problems, it might be due to outdated information or a different configuration. 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.
