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.
Tagged: Exception
This topic contains 44 replies, has 2 voices.
Last updated by kovusA-2 1 year, 8 months ago.
Assisted by: Christopher Amirian.
Author | Posts |
---|---|
June 27, 2023 at 9:30 am #13900815 | |
Christopher Amirian Supporter
Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00) |
Hi there, That is ok, as when the issue happens on your installation all the options are changed and it will show in the front end. You can use the normal link you use for your website too. Here it is: hidden link Use the same login information of your website. Thanks. |
June 27, 2023 at 12:36 pm #13902513 | |
kovusA-2 |
I followed your link. |
June 27, 2023 at 1:32 pm #13903053 | |
Christopher Amirian Supporter
Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00) |
Hi there, I reported this to the second-tier support and I will inform you as soon as I have an update. Thanks. |
June 27, 2023 at 1:36 pm #13903069 | |
kovusA-2 |
I will wait for news from you. |
June 28, 2023 at 1:39 pm #13910519 | |
Christopher Amirian Supporter
Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00) |
I have an answer from the second tier support. The way WPML works is that if you do a change in the string translation, such as changing the translation of the "password" string, it will check the database and bring all the strings to the MO files inside the wp-content/languages/wpml folder. Now the problem is that the database content is wrong and it was because of the wrong collation of the database and there is no way to recover those with bad encoding. The strings before "2023-02-26" appear to be corrupted. The strings after "2023-04-09" appear to be okay. Now I assume that there was a migration in that period of time of the database or some other corruption. That is why the only thing is to translate all those strings which are about 835. As Russian is supported as an automatic translation, you can select the strings that are bad and send them for automatic translation and that should fix the issue for you: https://wpml.org/documentation/getting-started-guide/string-translation/#translating-strings That way all the string will be translated to Russian at once. When you select the strings set DO NOTHING for Turkman language and only use the translation for Russian language to send it for automatic translation. Thanks. |
June 28, 2023 at 7:14 pm #13913293 | |
kovusA-2 |
Thank you for considering my issue. As you can see, the error occurred again, and I had to restore my site and database again. |
June 29, 2023 at 7:50 am #13915507 | |
Christopher Amirian Supporter
Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00) |
Hi there, Here is the video to explain the situation: hidden link And here is the rest of the video: hidden link Thank you |
July 2, 2023 at 11:28 pm #13929965 | |
kovusA-2 |
Thanks for your videos. Please show specific examples, I want to see this translation on the page. I ask you for this translation in detail. |
July 3, 2023 at 3:39 am #13930151 | |
kovusA-2 |
I tried to translate myself, but as soon as I try to translate something on my own, the site immediately displays incorrect characters, see the screenshot |
July 3, 2023 at 12:49 pm #13932759 | |
Christopher Amirian Supporter
Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00) |
Hi there, I explained what to do for the wrong characters and I mentioned you will need to replace all with the correct translation because of the database corruption that you had on your website. There is no way to recover the wrong characters and you need to translate everything one by one: hidden link Thanks. |
July 3, 2023 at 12:50 pm #13932765 | |
Christopher Amirian Supporter
Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00) |
One last thing is that I mentioned, if you do not want to manually translate, as you have the Russian language, you can use the automatic translation to translate the Russian language and you will not have to do them manually. |
July 4, 2023 at 3:48 am #13936789 | |
kovusA-2 |
Yes, it's much clearer now, thanks. |
July 4, 2023 at 12:54 pm #13941313 | |
Christopher Amirian Supporter
Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00) |
Hi there, I checked the website, and no Credits are available for the Automatic Translation. You either need to add credits or subscribe for pay as you go model: https://wpml.org/documentation/automatic-translation/automatic-translation-pricing/ Here is how to assign credits to website: only then the automatic translation will be available and I can help you show how to do the automatic translation Thanks. |
July 4, 2023 at 10:31 pm #13945053 | |
kovusA-2 |
I did as you asked. I signed up for a pay-as-you-go model. hidden link |
July 5, 2023 at 9:55 am #13948691 | |
Christopher Amirian Supporter
Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00) |
Hi there, Thank you I used the minimum strings and it seems that it is working now. There are a few things left that I think you can handle manually. For example the dates in blog posts. The Turkmen language does not support Automatic translation. But I do not see wrong characters there so I think you are good to continue your work. Thanks. |