Problem: The client is experiencing an issue where WPML loads indefinitely when trying to delete all content from the deactivated 'English' language on their website. Despite deactivating all plugins except Elementor and switching to the default WordPress theme, the content does not disappear, and the loading continues in a loop. Solution: We recommend the following steps to resolve the issue: 1. Ensure that no security plugins or cache/optimization plugins are active, as these could block the WPML actions. 2. If the problem persists, disable all other plugins and use the default WordPress theme to see if the issue is related to a specific plugin or theme. 3. Check if the content numbers are decreasing over time; if they are, the process is working but needs more time. If not, there might be a deeper issue. 4. Be aware of a known bug where taxonomies are not removed when deleting content from the database. This needs to be done manually. More information can be found here: WPML Errata on Taxonomies. If these steps do not resolve the issue, or if the solution seems outdated or irrelevant to your specific case, we highly recommend checking related known issues at WPML 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.
Problem: The client is experiencing issues saving and translating pages using WPML and Visual Composer, encountering a PHP Fatal error. This error is related to a protected method invocation in Visual Composer when integrated with WPML. Solution: We recommend following the steps outlined in the WPML errata for resolving issues with Visual Composer and PHP Fatal errors. First, ensure to back up your database before making any changes. You can find the detailed instructions here: Visual Composer Fatal Error when translating a page in PHP 8.0.x.
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 open a new support ticket at WPML support forum.
Problem: You are trying to add a new custom field using ACF, but encounter an error stating 'Uncaught InvalidArgumentException: item should be a Collection or an array or an object' when attempting to save it. Additionally, an E_ERROR occurs in the WPML plugin. Solution: We recommend applying the solution described in the following WPML forum topic: WPML forum topic. Also, check the errata page for a related issue here: WPML errata page.
If this solution 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is trying to reinstall all default plugins language files for Germanized and Germanized Pro, as all DE, FR, and IT translations have disappeared. Solution: If you're experiencing missing translations for Germanized and Germanized Pro, we recommend re-importing the .po files that come with the plugin. It's important to ensure that the strings are registered under the correct text domain in WPML. Strings should be registered based on the text domain parameter attached to them. For instance, strings defined with the text domain 'germanized-pro' will appear under that filter, and those with 'germanized' will appear under the respective filter.
If the issue persists or seems related to strings being registered under the wrong text domain or language, we suggest verifying the settings and, if necessary, adjusting them directly in the database.
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 problem continues, please open a new support ticket at WPML support forum for further assistance.
never loads. Solution: If you're experiencing this issue, we recommend removing the database key that might be causing the problem. You can find detailed instructions on how to do this on our errata page: https://wpml.org/errata/language-switcher-css-still-points-to-the-old-url-after-sites-migration/. Alternatively, you can use WP-CLI to delete the option directly using the following command:
If this solution does not apply because it's outdated or not relevant 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 for further assistance.
Problem: The client was facing issues with translating the footer into French on their WordPress site. The English footer was appearing instead of the French one, despite attempts to edit it directly in the footer editor. Additionally, there was a PHP error related to the Complianz GDPR plugin, indicating that translation loading was triggered too early. Solution: We advised the client not to edit the translation directly from the footer editor but to use WPML > String Translation to manage footer translations. For the PHP error, it was identified as a known issue with a fix available in the newer version of the Complianz plugin. We provided links to the relevant documentation and updates:
We corrected the language settings for the footer strings from English to French to resolve the translation issue.
If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, 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 further assistance is needed, please open a new support ticket at WPML French Support Forum.
Problema: Stai utilizzando il plugin Query Monitor che mostra errori PHP deprecati e un avviso DOING IT WRONG. Gli errori includono la conversione automatica di false in array in wpml-sticky-links, la creazione di proprietà dinamiche in wpml-cms-nav, e un avviso che la funzione _load_textdomain_just_in_time è stata chiamata in modo errato. Soluzione: I plugin WPML CMS Nav e Sticky Links sono principalmente plugin legacy e potrebbero non essere necessari, specialmente CMS Nav dato che molti temi offrono funzionalità simili. Le deprecazioni segnalate non sono errori critici ma indicano solo che il codice non è più supportato in PHP; gli sviluppatori sono già a conoscenza e rilasceranno un aggiornamento in futuro. Per l'avviso su _load_textdomain_just_in_time, introdotto da WordPress 6.7, consulta questa pagina per maggiori informazioni, anche se al momento non esiste una soluzione definitiva.
Se la soluzione proposta risulta non pertinente, perché potrebbe essere superata o non applicabile al tuo caso, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di verificare i problemi noti su questa pagina, di controllare la versione della correzione permanente e di confermare che hai installato le ultime versioni di temi e plugin. Per assistenza ulteriore, visita il forum di supporto WPML.
Problem: If you're experiencing a critical error after updating WPML from version 4.6.11 on a staging site running PHP 8.2, it might be due to a file naming conflict in the Yoast WHIP vendor library on case-sensitive servers. This issue does not appear on local copies or the live website.
Solution: We recommend the following steps to resolve this issue: 1. Navigate to the WordPress Dashboard > Plugins. 2. Deactivate and delete the WPML plugin. 3. Reinstall the latest version of WPML from our official website.
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 problem persists, please open a new support ticket.
Problem: The client is using the chauffeur booking system plugin and has issues with translating the plugin into Croatian and English using .po files. They encountered an error indicating that the function
_load_textdomain_just_in_time
was called incorrectly, suggesting that translations were loaded too early in WordPress.
Solution: 1. We identified that the error related to
_load_textdomain_just_in_time
is a known issue with the latest WordPress core, not directly related to WPML. For more details, see the errata page: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/ 2. We recommended increasing the WordPress memory limit to at least 128MB, which can help with processing translations. This can be done by adding the following code to the wp-config.php file:
3. To import .PO files using String Translation, follow the guide here: https://wpml.org/documentation/getting-started-guide/string-translation/#import-export-po-files 4. To make the plugin's strings available for translation in WPML, go to WPML -> Theme and plugins localization, select the plugin, and scan it for strings. The strings should then appear in WPML -> String Translation.
If this solution does not resolve your issue or seems outdated, we 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.
