Home›Support›English Support›[Resolved] Wp-admin error: Some taxonomies in your site are forced to be untranslatable.
[Resolved] Wp-admin error: Some taxonomies in your site are forced to be untranslatable.
This thread is resolved. Here is a description of the problem and solution.
Problem:
I have this error in wp-admin as show in the screenshot. I report this below:
Some taxonomies in your site are forced to be untranslatable. This is causing a problem when you're trying to run a multilingual WooCommerce site.
A plugin or the theme are probably doing this.
What you can do:
1. Temporarily disable plugins and see if this message disappears.
2. Temporarily switch the theme and see if this message disappears.
It's best to contact WPML support, tell that you're getting this message and offer to send a Duplicator copy of the site. We will work with the theme/plugin author and fix the problem for good. In the meanwhile, we'll give you a temporary solution, so you're not stuck.
How I can solve it. Solution:
By going to WPML -> Settings -> Taxonomies Translation and set some default WP taxonomies as translatable, the admin message seems to be gone.
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.
I have this error in wp-admin as show in the screenshot. I report this below:
Some taxonomies in your site are forced to be untranslatable. This is causing a problem when you're trying to run a multilingual WooCommerce site.
A plugin or the theme are probably doing this.
What you can do:
1. Temporarily disable plugins and see if this message disappears.
2. Temporarily switch the theme and see if this message disappears.
It's best to contact WPML support, tell that you're getting this message and offer to send a Duplicator copy of the site. We will work with the theme/plugin author and fix the problem for good. In the meanwhile, we'll give you a temporary solution, so you're not stuck.
Hi Laura, just try it in my staging site to disable almost all plugin. I only leave active the plugins that are necessary like yours and woocommerce. You could find some useful information of my site (also if you want to try or access) in the other ticket I open, as the login information and staging site: https://wpml.org/forums/topic/the-automatic-translation-has-been-stuck-for-a-long-time/
- if needed, do we have your authorization to make a copy of the website and migrate it into another server? In order to perform more complex tests without compromising the original
Moreover, if you want to test a possible solution in the meanwhile, you can try to delete the 'wpml_notices' key in the _options table - in case this is just a false positive message. Please ensure to have a backup before trying it.
Yes the site is the one of this reply, you have the authorization to backup or copy the site into another server. There's also a link in a staging server.
I also create today a backup with duplicator pro,
here is the link where you could download (please hide it after you download): hidden link
And the installer.php (remember to rename the extension) hidden link
I just tried it and it works.
I also test you solution but deleting the wpml_notices inside the database but it didn't work.
Thanks
I forget that to try to resolve I activate the translation for woocommerce brands (that is one of the other official plugin). Could I deactivate it the translation without any issue?
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello there,
Thank you for the confirmation.
About your question: "Could I deactivate it the translation without any issue?"
If you do not have any translation for this, yes, you can turn it as non-translatable. If this is not exactly what you asked, could you please clarify it a bit more?
Now, about the main issue here, our team is already checking it and as soon as possible we'll provide you with updates. Thanks for your patience and understanding in the meantime.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello there,
Thanks for your patience.
We tried to make a smaller package of the website, since the one you provided could not be used due to its size. But it seems we have a lot of permission restrictions, for instance to install new plugins and even successfully migrate the website into another server.
Another procedure we tested was to update WooCommerce and WCML, but with no luck. May I kindly ask you to review the permissions issue and and perhaps give the updates a try in your end?
Hi Mateus, I know the site is big. Yesterday I tried for you to recover my backup and it works...
About your account in the site, the wpml account I mean, you have all the permission as me, administrator, I only create for you a personal account to set the language in English, to simplify communication with you when we talk about something like menu link ecc.
I can provide my personal account and the server account with no problem, give me the appropriate form. In addiction if you provide me your flow about testing and recover the site and limitation I can check for you.
I also can duplicate the site another time (in the other conversation I give you access to the main and develop) from my AWS lightsail instance in few clicks. Let me now
Sorry, I just restore another backup, the old staging instance is gone, it didn't work anymore. I recreate a new one with the same credential as before
