I’m experiencing an issue with manually translated product attributes on my website (using the Kadence theme). My current setup appears correct according to Kadence Support, but it seems like manually translated attributes are adding an extra slug in the URL. This issue does not occur when using automatic translation.
The main focus here is using the Query Loop (Kadence) with WooCommerce. I have a product listing, and in Polish everything works correctly—the products are filtered as expected. When I added translations, the filters in other languages worked fine with automatic translation. However, I didn’t want to use up all my translation credits, so I manually translated the remaining attributes. Now the filters in those languages no longer work.
Kadence Support recommended reaching out to you to see if there’s a way to remove or prevent the additional slug that appears when attributes are manually translated. Could you please let me know if there is a known workaround or a specific WPML setting to address this?
Thank you for your help, and please let me know if you need any further details or access to troubleshoot.
Symptoms:
Manually translated attributes are adding an extra slug in the URL, causing filters in other languages to not work.
Questions:
Is there a way to remove or prevent the additional slug that appears when attributes are manually translated?
Is there a specific WPML setting to address this issue?
1. Navigate to WPML → Taxonomy Translation and select the taxonomy you wish to translate using the drop-down menu.
2. Click the plus icon to add or adjust the translations. Here, you can remove extra code from slug
If the above steps do not resolve the issue:
1. Go to Product / Posts → Categories / Attributes.
2. Choose the 2nd language and edit the category/ attribute to adjust the slug.
I’m sending you a message and a video from Kadence where the problem is explained in detail.
The issue is that some filters work with translated products, while others do not (as shown in the video).
For example, an attribute that works:
In Polish: Instalacja grzewcza/Wersja rozmiar/„50”
In English: Heating System/Version/„50”
However, an example of one that doesn’t work is shown in the video from Kadence (generally, there are many products where some filters work, and others don’t).
Here’s the message from Kadence:
"Hey Patryk,
Thanks for the update. I reviewed this once more with a developer, and we think this could be something from WPML and how it Queries. I made a video to explain this and I suggest providing this video to WPML for troubleshooting:
hidden link.
(You can also provide this ticket response to WPML as well)
I had a developer confirm the Query looks to be working as it should in this situation. What we think is happening is we think that WPML might be pulling in the Native Language Post IDS by default (Polish). Then, when we use a Filter in English, it uses the English Term ID. Since the Main Query seems to pull in the Native Language Posts, the English Filter finds no results. It looks like WPML pulls in the Polish Terms, then translates them to English on the Front End rather than using the English Posts.
There is also a chance that the Wersja/Versions Attribute isn't properly translated. I spent a bit of time checking this issue out and have confirmed with two developers the issue. WPML might know exactly what is going wrong in this case, as it could be something in this configuration causing this."
2) Please check if the issue still happens when only WPML plugins, Kadence and Wocommerce are enabled, and all other plugins are disabled.
3) If the issue still happens in step 2 please try to show us a simple example of an issue on this new website, that I created. Then I can quickly escalate this issue to our compatibility team.
4) Does not matter it should work, if not I will check with our team to try and get the key. As we need to reproduce this bug to be able to debug it on our side also and escalate to dev, to know what is wrong. This will speed things up in this process.
What I meant was that Query Loop (Adv) is a paid add-on for Kadence Blocks, and I’m not sure if I can add it to your site (in the sense of sharing the paid version of the plugin with other websites).
I understand but is for debugging purposes and to speed things up, so in most cases, it is understandable and falls under license. As you can see we collaborate with Kadence and they are our official partner:
Anyway, I have acquired a plugin from our compatibility team and installed it on the test site. Can you please try now and reproduce the issue. Please share the steps with me.
I’m currently trying to reproduce the issue and want to create a Spanish page, but there are no credits available for me to create a Spanish page. I looked through the settings but couldn’t find the option, and I don’t remember where to switch to manual translation instead of the automatic one that uses credits.
That said, as I mentioned, I used automatic translation for some of the product attributes, but I didn’t want to use it for everything, so I translated the rest manually. However, some additional credits would actually be helpful.
Okay, I managed to reproduce the issue. I created a new product, but it wasn’t necessary.
On this page, there is your product with the 50mm attribute in the English version:
hidden link
If you switch to Spanish in the footer, the Spanish version of the product appears, but when you select 50mm, you get a blank page – just like with mine.
Hi, I synchronized the attributes like you did, and I also received a message that the attributes are synchronized. However, unfortunately, the error still remains the same on my site 🙁 What can we do next?
I should add, because I'm not sure if I've mentioned it yet, that I've noticed when an attribute is a word and it differs in each language, it usually works. However, there are also strictly numerical attributes, such as "6x13", which don't work if the translation is the same and a slug like "-en" is added. On the other hand, there are cases like the "50" filter that works in every language. Nevertheless, here's what I've observed so far, as I have four languages (Polish - default), English, Romanian, and Ukrainian.
Example Filter - 50mm x 50m:
Polish - works
English - doesn't work
Romanian - doesn't work
Ukrainian - works
So overall, I'm shocked because I hadn't checked in other languages before.
