Home›Support›English Support›[Waiting for user confirmation] Backend WooCommerce non viene visualizzato in italiano
[Waiting for user confirmation] Backend WooCommerce non viene visualizzato in italiano
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Background of the issue:
Nel back end di WordPress, nonostante la lingua selezionata sia italiano, la lingua visualizzata per WooCommerce è inglese. Ho aggiornato i plugin, i permalink e ho installato e attivato il plugin WooCommerce multilingua.
Symptoms:
La lingua visualizzata per WooCommerce nel back end è inglese invece di italiano.
Questions:
Perché WooCommerce non viene visualizzato in italiano nel back end?
Come posso risolvere il problema della lingua nel back end di WooCommerce?
I'm answering in English because this ticket was opened on the English forum. If you need to continue in Italian let me know I will transfer this ticket to the Italian forum.
I'd like to ask you to follow these steps to solve the problem:
- Create a full backup of the site
- Apply the workaround described in this errata page: https://wpml.org/errata/wordpress-6-7-mo-files-not-loaded-and-leading-to-missing-translations-on-front-end/
- If the issue persists, then go to WPML -> Themes and plugins localization -> In the first section there are two checkboxes, apply the opposite configuration to the first checkbox (if it is selected, then unselected and vice-versa)
Let me know if the issue disappeared.
Important note: I recommend you contact your hosting providers and ask them to upgrade the PHP version at least to v8.1 or v8.2
I applied the code you suggested on the WPML errata page, and everything is now working as expected.
Just to clarify, is this solution a temporary workaround, or do you plan to include it in a future update? Should I continue applying this fix manually, or can I expect it to be addressed in the next release?
