I am trying to translate my website without creating a ton of unnecessary translated terms.
I turned off translation of "Translation priority" taxonomy in settings, but it is still translated automatically. When I added German language and translated a couple of pages, new terms in this taxonomy appeared. And they appeared not in German language, but next to English terms.
1) Can you please check that the "Copy taxonomy to translation" checkbox is unchecked, to do so please:
- go to WPML-> Settings -> Posts and pages synchronization (section)
- un-check the checkbox next to "Copy taxonomy to translation" and save changes
*check the attached image
After try again and see if there is any new term showing up.
2) The new terms of the taxonomy appear in both languages next to each other, when you have set the default language or secondary language from the top language switcher on the wp-admin bar?
1) I would suggest:
- you check if any of the terms being translated are set to any page/post
- if there is please change it on the post/page
- delete the translation of the terms you don't want
- clear the cache of your website
After, check if the issue happens.
2) If the issue is still happening, I would require you to try to test if the issue happens in a staging/testing site with minimal setup, meaning:
- set a default WP Theme
- enable only WPML Plugins
- disable all other plugins
Note: Please make sure you have a full backup of your website if you want to test on a production site, in order to prevent any data loss.
Here is the translated term, it is not assigned to any post/page.
I deleted it, and turned on translation for "Translation priority" taxonomy in WPML settings.
Now behavior is better, it just created a translation of taxonomy term "required" with slug "required-de". Now it does not act as a separate term, but acts as a translation of "required" term. Interesting that the term itself was not translated.
I believe that this is correct behavior of WPML, problem is that it will bloat database with dozens of unnecessary records. Every term of any involved taxonomy will be duplicated with new slug -de, -es, -it, -pt etc.
By default, when adding a new language to the website, only the statuses ("Required", "Not needed", "Optional") should be present, these statuses get translated based on the secondary languages you have on your website. Unless you need to add other terms to the "Translation priority" based on your translation workflow, no other terms should be created or appear.
When the translation for the "Translation priority" taxonomy in WPML settings is activated, it sets a status for the posts/pages, but this doesn't impact database performance.
While having the translation option on for the "Translation priority" taxonomy in WPML settings, please:
- go to WPLM -> Taxonomy translation
- on the dropdown of "Select the taxonomy to translate" select "Translation Priorities"
- check the list of terms that will show up if it is what you have in use on your website
Could you please try turning off the translation option for the "Translation priority" taxonomy in WPML settings and see if it still creates translations?
Okay, let's go step by step.
1. I understand what is translation priority for, and I use it. It's a necessary feature.
2. I did not create any other terms manually, standard terms set is enough for me.
What is the problem:
WPML is creating lots of unnecessary translations for taxonomies and their terms.
I do not want to translate slugs on my website.
So, if I have /category/news in English, for German I need /de/category/news
As for internal taxonomies (like aforementioned Translation priority), of course I do not need to translate them too. It makes absolutely no sense.
So, I turned off all taxonomies translations in WPML settings.
After that, when I send a page with Tanslation Priority set to Required, the "Required" term gets translated and is mixed with English terms of Translation Priority taxonomy. Note: I use automatic translation with Deepl.
I strongly think this is a bug in WPML and it must be fixed.
If taxonomy translation is turned off, it must not be translated in any case.
Next, there is workaround. If I set "Translation Priority" translation to "Translatable.
use translation if available or fallback to default language", then "Required" term is not translated automatically anymore. That's good.
BUT there is another problem: a duplicate of original term is created with the same name "Required", but with different slug. English is "required", German is "required-de".
I do not need this additional taxonomy term.
There are two problems with this approach:
1. It bloats DB with lots of terms with -de, -es, -it etc. additions at the end.
2. Slugs of translated versions are also spoiled.
Example:
Original address /category/news
German page which I need: /de/category/news
German page which WPML makes: /de/category-de/news-de
So, I suppose that correct configuration must be: All Taxonomies Translation are set to "Not translatable". Taxonomies, terms, slugs are not translated and not changed and not duplicated.
Thank you for providing a detailed explanation of the issue you're facing. I truly appreciate your patience.
I would require you to try and recreate the issue on a testing site in order to further investigate the issue.
Use the link below to access the testing site: hidden link (one-click login)
- WPML is already installed/activated, please configure it the same as on your website
- upload only the necessary plugins to recreate the issue (if needed)
You can also try these settings on the testing site and see if there is any change:
1) Avoid Slug Translation:
- Go to WPML > Settings
- Scroll down to the "Slug Translation" section. Check that the checkbox next to "Translate custom post and taxonomy base slugs (via WPML String Translation)". By turning this off, WPML will not translate the slugs, and they should remain consistent across languages.
2) Turn Off Taxonomy Translation:
- Still within WPML > Settings, navigate to the Taxonomies Translation section
- Set all the taxonomies that you don't want to be translated to "Not translatable"
This way, WPML won't prompt you or auto-translate these taxonomies.
Please let me know how it goes or if you need any help.
Ha-ha, I entered the sandbox. I just turned off "Translation Priority" translation and I already get mixed German and English terms in the dropdown. I didn't even start translation.
I managed to reproduce the problem in the sandbox.
1.Turned off appropriate settings in WPML
2. I got German an English terms mixed in one dropdown
3. Deleted German Translation Priority Terms
4. Set Translation priority of test page to "Required"
5. Started translation via ATE
6. And here I get "Required" term in ATE.
Here is where the problem is coming from. Check the screenshots.
And here I have one more Translation priority term in the dropdown.
This is a critical issue, I can not proceed with site translation until this is fixed.
1) The behavior of taxonomy terms appearing in mixed languages at WPML -> Translation Management is expected. This occurs because when terms are created, they persist on the website and display in the main language even if the translation for "Taxonomy Priorities" is turned off. (You can manually delete any unnecessary terms.)
2) I attempted to reproduce the issue on the sandbox by following your steps but couldn't recreate it exactly. Here's what I did:
- Deleted the previously created term "Requiredqweqwe".
- Created a new test page and set its priority to "Required".
- Translated it to German (no priority term appeared on ATE for translation).
- The term "Requiredqweqwe" was created only once, despite multiple attempts to reproduce this issue.
- I subsequently deleted the term "Requiredqweqwe".
3) Then, I disabled the TaxoPress plugin to see if the issue persisted without it. I couldn't reproduce the issue without the plugin. Even after reactivating the plugin, the issue did not reappear.
Can you provide details on how you use the TaxoPress plugin on your website? Or there is a step I might have missed when trying to reproduce the issue?
It's possible that this issue is related to the TaxoPress plugin, and to address or escalate the problem properly, I'll need a better understanding of your use of the plugin.
I appreciate your patience, and I look forward to your response.
Marsel
I could not reproduce the problem anymore. But I posted the screenshot where "Required" taxonomy term is in the ATE. Why is it there? It is not supposed to be there.
Could you reset this sandbox, so that I will make all the actions on the fresh setup and record a video with the problem.
Second, you are asking about Taxopress, why I use it. Exactly for the reason in the first item of your answer: I clean trash after WPML.
Mixed English and non-English terms in one dropdown must never be in one dropdown. After I disable translation WPML must delete all unnecessary terms automatically, not me manually with Taxopress.
I've set up a new fresh sandbox, please try to reproduce the issue without installing the TaxoPress plugin first, in order to better understand if the issue is created from the WPML or it is happening from the TaxoPress plugin.
Sandbox link: hidden link
* As I explained before, mixed terms being displaying the in the dropdown after having disabled the translation is normal behavior of WPML (is the same as when you disable WPML plugins completely, your translations will show mixed up on posts/pages).
You would need to delete the terms manually after disabling the translation for taxonomies.
That can be done without using any plugin on the wp-admin page: "/your-website/wp-admin/edit-tags.php?taxonomy=translation_priority"
Thank you, I'll record a video of reproducing the problem and come back.
As for WPML behavior. I understand what you say: it is WPML standard behavior. But I don't think it is correct. I think WPML must never mix translated and untranslated items in the dropdown. It make no sense. Instead of this, WMPL should delete all unnecessary terms and not make users do the monkey job.
The topic ‘[Closed] Translation priority taxonomy translated despite settings’ is closed to new replies.
