|
Hello,
We are currently experiencing an issue with taxonomy translation on our website:
We have a custom post type called Franchise with a custom taxonomy franchise_category.
**Description of the Issue**
We noticed inconsistent behaviour when working with taxonomy translations:
**1️⃣ Translation Creation Behaviour**
When we create the taxonomy directly as a translation (from the translation interface), it works correctly.
However, when we:
Create the taxonomy separately in EN-US,
Then try to map or assign it to the FR translation,
👉 It does not work properly.
It seems that the taxonomy must be created strictly through the WPML translation workflow, otherwise it fails.
2️⃣** Slug Conflict Problem (Important)
**
The issue appears specifically when the slug of franchise_category is identical across languages.
When the slug is the same:
The taxonomy seems broken.
The category does not update properly.
Saving behaves inconsistently.
However, this should NOT happen because:
Translation is explicitly activated for this custom taxonomy in WPML settings.
The taxonomy is set as translatable.
Please clearly note:
It is when the slug is the same that the issue appears.
It seems broken only in that situation.
This behaviour suggests a conflict in how WPML handles identical slugs for translated custom taxonomies.
**3️⃣ Saving Fails After Unassigning**
Another critical issue:
If we unassign the taxonomy from a post,
We are unable to save the post properly afterward.
The taxonomy cannot be saved again.
Category changes are not updating.
This creates a blocking workflow issue.
**4️⃣ Existing Categories Not Updating**
We also tested:
Using existing categories not currently assigned
Editing and reassigning them
But:
They do not update properly.
Changes are not reflected after saving.
**5️⃣ Conflict Testing**
To rule out conflicts:
We deactivated all unnecessary plugins.
The issue still persists.
We activated a default theme (Twenty Twenty-Four / Twenty Twenty-Five) for testing.
The problem remains even outside the Bricks child theme.
Video Demonstration (Very Important)
Please watch this video carefully to understand the issue clearly:
hidden link
In the video, you will clearly see:
1. The different behaviours between creating as translation vs separate creation
2. The saving issue after unassigning
3. This video demonstrates the issue much more clearly than text explanation.
Our Questions
1. Why must the taxonomy be created only as a translation to function correctly?
2. Why does saving fail after unassigning the taxonomy?
3. Why are category updates not reflected?
4. Why does the issue specifically occur when the slug is identical across languages?
5. Should identical slugs be supported when translation is enabled for that custom taxonomy?
This issue is blocking our workflow, and we would appreciate your guidance.
Looking forward to your assistance.
Thank you.
|
