I have translated a product attribute (manufacturer) to 2 languages (german and english) Also the slug is translated, but the description of the attribute, will be in the original language even though the attribute value is translated and the description as well
Thank you for contacting WPML support, I'd be happy to help you with this issue.
I've tried to create a new attribute and translate it, the translation description displays properly in the frontend. Here is the attribute page URL hidden link
So I think it could be a server caching issue. Can you please try to clear the server cache or contact your hosting support and ask them to clear the cache and check this issue again?
Page Cache is disabled, I cleared the object cache via ssh, restarted the redis service. Also how can the half page be in English and the other half in German if it is a caching issue? I didn't translate the taxonomies shortly I copied the db weeks ago from the live site and just pushed the plugin / core updates there.
It seems, that as soon as I change the slug of the translated category to something different then the original one, it seems to work normally again, but that would screw up my whole link structure.
hidden link hidden link -> doesn't work, shows the german description and meta tags and so on, hidden link -> shows the english content immediatly. So there is some mixup with the permalinks I assume?
I see that issue after changing the slug of the test attribute to "wpml-test-de" as you said. But I do not see it occurs on a clean installation of WordPress, you can check it here hidden link
I suggest you contact your hosting support and ask them to check the server configuration file if there is an issue there. Or use a different attribute slug in the English language to fix this issue.
i checked logs and found out, that that issue is there since the migration from polylang a month ago. So it seems to have to do with a incorrect logic in the migration tool or something else. Before the migration (on polylang) everything was fine and the content was displayed correctly.
Also, it seems, that if I switch on the option auto_adjust_ids it does work, but the db queries explode from about 200 to 600 on archive pages and way more on product pages. As that issue is then woocommerce related and not theme related (I do not overwrite the archive woocommerce template functions) i assume that's a malfunction?
Using the feature auto adjust ID would help to fix this issue but the downside for using it is slightly increased processing time and DB access, as WPML will hook to many functions and check that the output is correct for the active language.
Actually I am shocked :O That issue that you are linking had an open ticket at the WP Core Team which was especially fixed to solve the linked issue.. That ticket was solved and implemented 5 YEARS ago. That is horrible for such an regularly occurring issue and has nothing to do with my current issue.
As all parts of the page are translated without auto-ids and just the description and SEO information not I assume thats an mistake in the woocommerce integration, because you can't really prepare a theme to conquer that issue (I know you could overwrite all woocommerce functions but that wouldn't be sane for a theme dev).
Also I already have a major performance decrease after migrating from polylang and don't want to decrease the performance any further.
Could you please check if that will be fixed soon? It certainly does.
I ran into another issue now with using the auto-ids. Because of that the cache cleaning functions won't work anymore except for the default language, because they get the slug by querying get_post which then returns always the default language post.
As already said, I assume that that has to be fixed in the WMPL Woocommerce Plugin, because the description of the taxonomies of blogs e.g. like "category" works like expected without the auto IDs.
Please get a response from the 2nd level asap. Can't understand how that issue is not affecting more people.
I'm waiting for more feedback from our development team in this case. Meanwhile, they also suggest turning on the option auto adjust ID (by default) for the term and its translation which have the same slug.
I will update you here as soon as I have something to share.
As the translated slug is identical to the original slug, WordPress fails to fetch the proper (translated) term. We have a mechanism that replaces it with the translated ID, but this is disabled when "Auto adjust IDs" is disabled. It also can save a lot of headaches and make other themes compatible with WPML to display translation content. So our development team recommends enabling this option to fix the issue.
Or please use a unique slug for each term as a workaround. Thank you.
The topic ‘[Closed] Description of the attribute, will be in the original language’ is closed to new replies.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
