Skip Navigation

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.

Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 -
- 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 -

Supporter timezone: Europe/Zagreb (GMT+01:00)

This topic contains 2 replies, has 0 voices.

Last updated by patrykP-6 2 hours, 55 minutes ago.

Assisted by: Dražen.

Author Posts
January 8, 2025 at 12:01 am #16571618

patrykP-6

Background of the issue:
Hello WPML Support Team,

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?

January 8, 2025 at 7:23 am #16572175

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

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.

Regards,
Drazen

January 13, 2025 at 1:47 pm #16588792

patrykP-6

Hi, unfortunately, this didn’t help us.

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."