Skip to content Skip to sidebar

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client discovered that all strings translated from English to Bulgarian were deleted and replaced by their translations, causing elements on English pages to appear in Bulgarian. The issue was also present on the staging site, ruling out a cache problem. Additionally, there was a concern about taxonomy translation where a sub-category was missing its parent category.

Solution:
1. We resolved the synchronization issue indicated by the warning at the top of the backend.
2. We navigated to WPML -> String Translation, searched for, and deleted the entries for 'grad'.
3. We went to WPML -> Settings -> Taxonomy translation, selected 'City', and added 'city' as a translation for the 'grad' slug, then saved the changes.
4. In the 'Real State' section under 'City', we fixed a sub-category that was missing its parent category in English.
5. We advised the client to follow these steps on the production site.
6. We also highlighted the importance of saving theme options in the correct backend language, as saving them in a secondary language might have caused the default language for strings to change.

Please note that this solution might not be relevant to your case, as it could be outdated or not applicable. If you're experiencing similar issues, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket with us.

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.

This topic contains 40 replies, has 2 voices.

Last updated by Carlos Rojas 1 year, 7 months ago.

Assisted by: Carlos Rojas.

Author Posts
March 15, 2024 at 12:55 pm #15414504

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

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

Hi,

Step 3 is in WPML -> Settings -> Taxonomy translation -> City -> Added 'city' as a translation for the 'grad' slug -> Save the changes

March 15, 2024 at 12:58 pm #15414524

damienC-18

I don't think we understand each other, have you seen in the last screenshot that the slug for city is "grad"? It shouldn't be the case, it should be "city" in English. How can I change it please?

March 15, 2024 at 1:04 pm #15414547

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

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

I do understand you, but you haven't done step 3.

Go to hidden link -> Taxonomy translation -> City -> The slug is not translated. Translate that slug.

March 15, 2024 at 1:13 pm #15414579

damienC-18

Now what? I still can't edit the English's slug (screenshot).

slug.png
March 15, 2024 at 1:18 pm #15414600

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

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

Please watch this video: hidden link

March 15, 2024 at 1:34 pm #15414646

damienC-18

OK my bad sorry I didn't get that there were TWO "Taxonomy translation" pages, one under "Settings", hence my confusion.

The slug for city is "grad" in the first "Taxonomy translation" but anyhow frontend indeed the slug is correct when we switch language, that's confusing but eh, you made it work, thanks.

I've set the village back once more under Kostenets and now there's no error showing up anymore.

The theory from your coworker is that I might have translated some things under the BG tab, yet it doesn't make any sense, I made all translations a few weeks ago and there was no mistake at all on front-end.

If I ever notice a plugin triggering such issue again I'll report it.

Thank you for your assistance, you can close this ticket.

March 15, 2024 at 1:56 pm #15414691

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

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

Hi,

No worries, WPML sometimes could be tricky 🙂

Please don't hesitate to contact us if you need our help in the future with WPML. We will be more than happy to help.

Have an excellent day!

March 15, 2024 at 3:56 pm #15415276

damienC-18

Hi, for some reason the problem happened again with Ochusha village.
Credentials are the same.
Can you check please?

March 18, 2024 at 10:37 am #15420325

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

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

Hi,

Please run the sync steps in the warning messages that appear in the backend -see attached image-

FireShot Capture 237 - Dashboard ‹ BulgarIMOT.bg — WordPress - bulgarimot.bg.png
March 18, 2024 at 10:43 am #15420391

damienC-18

Hi, I've deleted and recreated Kostenets and put Ochusha both from Bulgarian and English under. So far no new error message, I hope it'll stays like this.

For the "type" error message it's a mistake from my team they'll fix it themselves in due time I told them.

March 18, 2024 at 12:19 pm #15420764

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

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

Excellent! Is there anything else I can help you with?

March 18, 2024 at 12:26 pm #15420784

damienC-18

So far so good, thank you for your support Carlos. Have a good day!