Problem: The client has a custom taxonomy set as not translatable, yet translations are being added to the terms. The taxonomy consists of country codes as slugs, and the client is concerned that making the taxonomy translatable will alter the slugs (e.g., 'GR' becoming 'GR-DE'), which could affect the site's geolocation functionality. Solution: We advised that while WordPress does not allow duplicate slugs for taxonomy terms by default, WPML can manage this issue. When translating a taxonomy term, the client can edit the term to remove the language prefix, thus keeping the original slug intact (e.g., changing 'GR-DE' back to 'GR'). Additionally, if the client wants the terms to be synced across translations with the English post as the source, this functionality should already be in place.
If this solution does not resolve the issue or seems outdated, or if it does not apply to your specific case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.
