Taxonomy translations do not seem to get saved in the database.

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
-	-	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00
-	-	-	-	-	-	-

Supporter timezone: America/Lima (GMT-05:00)

Tagged: Bug, Compatibility, Exception

This topic contains 25 replies, has 1 voice.

Last updated by Andreas W. 10 months, 4 weeks ago.

Assisted by: Andreas W..

Author	Posts
June 4, 2025 at 7:59 am #17104981
kaurM	We have been using the Ultra version of their theme from the very beginning. Initially, we also imported the demo placeholder content to get started.
June 4, 2025 at 5:04 pm #17107689
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	I can not confirm the issue on my test site. I will now try to take a local copy of your website to investigate further and take a closer look at the database.
June 5, 2025 at 4:09 am #17108415
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	I am still trying to figure out what is causing these unexpected issues but wanted to give you a quick heads-up. Please see the screenshot attached which is from WPML's translations table. I first created a new "Feature" which has the source language "NULL" and language code "en". This entry is expected. Then I went to WPML > Taxonomy Translation and translated this new Feautre to Russian and German which registers on the table with the source language "es" instead of the expected code "en". Finally, I went to Esay Real Estate > Property Feature, edited one of the Features, and added a translation from the edit screen. This time the database entry is correct. This time also I see the translation showing up at WPML > Taxonomy Translation. I suggest you use the last workflow as a workaround. Why this unexpected issue occurs when using WPML > Taxonomy Translation is still unclear to me and I need more time for the investigation.
June 5, 2025 at 7:16 am #17108738
kaurM	I’ve noticed that new taxonomies in languages like German are being marked as Spanish. I suspect this could be happening because all secondary languages, except Spanish, are currently hidden on the front end. Could this be related to the database issue?
June 5, 2025 at 8:37 am #17109065
kaurM	I today installed the Media Translation plugin to manually translate images containing text. After completing the initial setup, I noticed that all current images are marked with Spanish as the original language, even though the page's default language is set to English (and has always been).
June 5, 2025 at 4:03 pm #17111287
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Hi, I discovered a site issue, that does not solve the problem on this ticket but is something that should be handled: WPML uses a term called "Translation preference" which on your site currently was set to "Not translatable". Further, there are more than 170 terms declared in the site's default language, which is unexpected. There should only be 3 terms per language: - Required - Optional - Not needed I am not sure why this issue occurred, but I would suggest deleting all the duplicated terms. Make sure to not delete all terms, as this will lead to an error. You can find them at: /wp-admin/edit-tags.php?taxonomy=translation_priority If you agree, I can take a look into this on the live site. --- I am investigating now the database of your site to find out what is causing the unexpected language assignment in Spanish. If I do not find the cause today, I will be escalating the issue to the Second Tier Support Team.
June 5, 2025 at 4:54 pm #17111535
kaurM	The live site has the pre WPML install setup. Please feel free to take a look if you think it might help resolve the issue. I would appreciate it if we could address this on the development site, as we need to update the live page once the problem is fixed. We cannot update the properties info until this is resolved, so I just wanted to make you aware of our situation. Thank you for your help!
June 5, 2025 at 8:21 pm #17112298
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	This issue has been escalated to the Second Tier Support for further revision. IMPORTANT: Please allow us further access to the Staging site. Once I have feedback from the team I will contact you again.
June 6, 2025 at 7:07 am #17112959
kaurM	Please go ahead. Do you need anything additional from my end?
June 6, 2025 at 4:33 pm #17114638
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Could you please allow me once more access to the site, so that I can create a smaller site package for the second tier support? The current package has 19GB. I might be able to create a smaller package without media. The private reply form is enabled again.
June 7, 2025 at 2:31 am #17115177
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Thank you very much! I was able to create a smaller package (2GB) and forward it to the second tier support team.