If you're experiencing a PHP error related to the WPML plugin with a warning like 'unserialize(): Error at offset 69 of 223 bytes in wp-includes/functions.php:650', it might be due to an issue with the WPML_Notices class.
Solution:
We recommend that you first ensure you have a full site backup. Then, update your WooCommerce and WPML String Translation to the latest versions, as these updates include fixes for similar issues. You can read more about the related improvements here: https://make.wordpress.org/core/2024/10/21/i18n-improvements-6-7/. After updating, clear all types of caches on your site to see if the problem resolves.
If this solution does not apply to your case, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket with us at WPML support forum.
The client reported errors related to the function
_load_textdomain_just_in_time()
being called incorrectly in various plugins, indicating that translation loading was triggered too early, which should ideally happen at the init action or later.
Solution:
We acknowledged that this is a known issue and our developers are currently addressing it. We recommended the client to refer to our Errata and support forum for more details:
We advised the client to upgrade to the latest versions of all relevant plugins, including WooCommerce (9.4.3) and WPML String Translation (3.2.17), after ensuring a full site backup. This step is crucial to verify if the issue still persists.
If this solution does not resolve the issue or seems irrelevant due to being 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 continues, please open a new support ticket.
Problem: If you're unable to translate the text of your homepage images, even though caption translation is activated and if using Avada image carousel widget. Solution: We recommend you follow these steps: 1. Navigate to WPML > Settings > Custom XML Configuration. 2. Add the following code:
3. Make a small change to the default language page and save. 4. Re-translate the page. After these steps, the image title and caption should be available for translation.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking the related 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.
Problem: The client is experiencing issues with WP Job Manager where candidates' applications are not visible in Spanish and English, despite being visible before without translation. The client is seeking solutions to make them visible again without translating or duplicating the content and inquires about automatically duplicating job applications and resumes. Solution: To resolve the visibility issue without translating or duplicating content, we recommend setting resumes to display as translated by going to WPML → Settings > Post type translation, finding the resume post type, and setting it to 'Translatable – use translation if available or fallback to default language'. There is no option to automatically duplicate content; however, there is an option to automatically translate content using the 'Translate everything' mode.
If this solution doesn't look relevant, please open a new support ticket at WPML support forum.
Problem:
When using WP Job Manager, the categories are visible in all languages simultaneously, which is not the desired behavior. The categories should only appear in the language in which the job is posted.
Solution:
First, ensure that the taxonomy 'job_listing_category' is set to be translatable: 1. Navigate to WPML > Settings. 2. Scroll down to Taxonomies translation. 3. Change the translation preference of 'job_listing_category' from 'Not translatable' to 'Translatable'. After this change, you will need to translate the terms since they are currently registered under the primary language. To translate them: 1. Go to WPML > Taxonomy Translation. For more information, please refer to our documentation on Translating Post Categories and Custom Taxonomies.
If this solution doesn't look relevant to your issue, please open a new support ticket in our support forum.
