Product attributs changing maste language by themselves

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.

Tagged: Documentation request

This topic contains 32 replies, has 0 voices.

Last updated by Andreas W. 1 month, 1 week ago.

Assisted by: Andreas W..

Author	Posts
May 6, 2026 at 1:11 pm #18017680
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Vintage was not appearing inside WPML > Taxonomy Translation, as it was set to "Not translatable. WPML > Settings > Taxonomies Translation > Product Vintage (pa_vintage). You need to set it to "Translatable only show translated items". I adjusted this now. The same counted for "Product Volume (pa_volume)". Result: The attribute terms are no longer appearing duplicated at Products > Attributes. Guide: https://wpml.org/documentation/getting-started-guide/translating-post-categories-and-custom-taxonomies/
May 7, 2026 at 3:08 pm #18020990
henrikt-5	It was me when doing the sync and reading that I can also make attributes "untranslatable" doing those setting changes. There is no reason for having vintage, volume etc... translated in different laguages... 2018 is 2018. 75 cl is 75 cl in all languages. I thought this would simplify, not complicate. The outcome has been that -sv -fr-en have been created. I really don't see an end to this mess and will in any case return the values you changed to non translatable, if I remember how to do that... Is your guide complete meaning, if I follow it from step A, will I then have correct setting of the attributes without WPML doing changes by its own ?
May 8, 2026 at 2:14 am #18021544
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Hello Henrik, Thank you for your patience. Following the guide step-by-step should help you set the attributes correctly without WPML making unwanted changes. However, it's important to ensure that you fully understand the settings to avoid any further issues. The attributes need to be translated. If you set them to "Not translatable", the already translated attributes will show up in site's default language. This is expected behavior. Best regards Andreas
May 11, 2026 at 5:14 pm #18028396
henrikt-5	Well, I will check the guide, but this is so complicated that even professional webmasters do errors apparently. I paid a pro to do the initial setup. Furtheron, when reading your message, I would rather expect when making a previously translatable attribute non translatable, that the attribute becomes a single value for all languages. Not to have the translated ones included in to the master language... Best regards, Henrik
May 12, 2026 at 5:49 pm #18031276
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Indeed, I totally understand your expectation, but in fact, if you set a post type to "Not translatable" or disable WPML, it assigns all translations to the site's default language. WPML has a cleanup tool that becomes visible at WPML > Languages if you disable an active language, but this dialog will remove all translations for a given language. If you want to keep a global product attribute to "Not translateable", you will need to delete the translated terms manually at Products > Attributes.
May 20, 2026 at 9:14 am #18047895
henrikt-5	Well, I don't know what to say. I : -I've done the syncs as discussed and deleted the automatically created attributed => they are now back again, WPML created them alone -I created non translatable attributes for simplification i.e. "vintage". WPML now gives me 3 options to select the same vintage, probaly one in each language ex. 2008 three times proposed on the product page I'm sorry, but this is not a well working plugin with customer friendly envinironment. I don't know where to start and all I do make the situation worse...
May 20, 2026 at 11:11 am #18048306
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Please provide me with admin access again, so that I can take a closer look at this issue. The private reply form is enabled.
May 26, 2026 at 10:35 pm #18062025
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	There is a fatal error on the login page that disappears once I disable WPML by renaming its plugin's folder using the FPT connection. Next, if I now go to the Plugins list, I can still see a fatal error that seems to be caused by WCML. Disabling the plugin by FTP solves the issue. To identify the cause of these errors, I will need to take a local copy of the site, but before doing this, I need to ask you to try the following: 1) Disable the plugin "String Locator" - you do not need this plugin when using WPML and its String Translation plugin. 2) Update all plugins. Leave me a comment once you have finished those tasks.
May 27, 2026 at 3:29 pm #18064315
henrikt-5	Andreas, What have you done??? The country selector is gone and there is USD proposed, it's a pure messup ! The whole night the site has had critical errors. Please correct the site immediately. I just sent a newsletter and this will definetaly create a mess !!!
May 27, 2026 at 3:42 pm #18064364
henrikt-5	First time in 13 years I experience a plugin support team member breaking a functioning customer website. Who told you to remove the language selector and install new currencies ? This is NOT normal.
May 27, 2026 at 3:55 pm #18064423
henrikt-5	What did you do Andreas ? We restored the data base back to last night and the switchers are still a mess ?
May 27, 2026 at 7:13 pm #18064765
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	If you could please read this comment again: https://wpml.org/forums/topic/product-attributs-changing-maste-language-by-themselves/?paged=2#post-18062025 1) I was not able to access the login form unless I disabled WPML 2) I was not able to access plugins in the backend, as long as I disabled WCML This is why you did not see a language switcher or a currency switcher, as both plugins are currently causing fatal errors on your site. If you would like me to investgiate this issue further, provide us access to a staging site on which we can work without affecting the business of your site.
May 27, 2026 at 7:53 pm #18064791
henrikt-5	Hold on, please don't put the things in the opposite direction. First you can ask for those accesses, then intervene. Now you've created bugs on a live website and I' rather prefer you put it back to what it was in a first step. I don't have a staging site and can not set it up in 5 minutes. Please put things back to what they were and don't disconnect plugins and test around live if it's not secure. I would appreciate a immediate action on this.
May 27, 2026 at 8:15 pm #18064811
henrikt-5	If you can tell me what to restore (avoid complete restoration losing orders) it would be fine. What has been touched and what to be restored ?
May 28, 2026 at 4:27 am #18065178
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Only deactivated the plugins "WPML Multilingual CMS" and "WooCommerce Multilingual". I already activated them again earlier today. If you can not provide access to a staging site, I can offer to use the plugin "All In One WP Migration" to take a copy of the site for debugging purposes. Would you agree on that?