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 |
---|---|---|---|---|---|---|
- | 8:00 – 15:00 | 8:00 – 15:00 | 8:00 – 15:00 | 8:00 – 15:00 | 8:00 – 15:00 | - |
- | 16:00 – 17:00 | 16:00 – 17:00 | 16:00 – 17:00 | 16:00 – 17:00 | 16:00 – 17:00 | - |
Supporter timezone: Europe/Rome (GMT+01:00)
Tagged: ATE
This topic contains 7 replies, has 1 voice.
Last updated by Alejandro 2 days, 19 hours ago.
Assisted by: Alejandro.
Author | Posts |
---|---|
January 20, 2025 at 3:26 pm #16614305 | |
brigitteW |
Background of the issue: Symptoms: Questions: |
January 20, 2025 at 4:40 pm #16614834 | |
brigitteW |
And I have another item that stays stuck, this time at 96%. |
January 22, 2025 at 7:28 am #16621297 | |
Waqas Bin Hasan Supporter
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Hi, Thank you for contacting the support. Meanwhile this ticket is attended by one of my colleagues, please try the following: - Go to your user profile and make sure that first and last name fields are filled properly, if not, please fill in and save the profile. Please let us know and we'll try our best to help you further if issue continues to appear. Regards. |
January 22, 2025 at 1:21 pm #16623179 | |
brigitteW |
Hi Waqas, So instead I went to tasks in my Translation Management and removed the task there and followed the rest of the steps you mentioned. Another issue is now, since today, that as soon as I open the Advanced translater and I click in a field, my screen goes blank. So I cannot copy already translated content, I cannot edit content - I cannot do anything. So: Hope there is a solution? |
January 22, 2025 at 1:24 pm #16623182 | |
brigitteW |
Update on my side: So to the WPML team: it seems to be an issue with the advanced translater. |
January 22, 2025 at 2:10 pm #16623608 | |
Alejandro Supporter
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00) |
Hello, We are in the process of fixing all the issues we found about the advanced translation editor and we should have an update more or less in the first week of February with a big improvement and many bug fixes. About the white screen issue, do you remember the page you were trying to translate that had this issue? because I'd like to check on that situation and see if we have that among our bug fixes. In the meantime, you can keep using the "old" version of the translation editor which will probably have less issues since it's more mature. Thanks in advance. |
January 24, 2025 at 12:32 pm #16631322 | |
brigitteW |
Hi Alejandro, The issue with the white screen happened with all pages, where I openend and tried the translator. The weird thing is, that untill January 22nd I did not have the white screen issue. It started when I followed the steps of Waqas, to get my translation un-stuck, and after that the white screen happened. First with the Privacy statement page, and then my FAQ page (that was translated for 100% but I had some edits in the source language). I can provide the URLs but the site is in maintenance as the store is not open yet. That'll be in about 4 weeks. So if there is anything I can download or make a screenshot for you to investigate? I'm happy to help. |
January 27, 2025 at 9:36 am #16636671 | |
Alejandro Supporter
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00) |
I see, ok white screens are errors happening and it could mean 2 things most of the time: - Something that was supposed to load on the browser failed to load - You are trying to edit a page that came from a different domain. In most cases the issue should be resolved by going to WPML > Translation Management and resending the page again for translation. Did you ever try that? If so, if the problem happens again, please let me know the URL of the page where that happened and also if possible open the JS console of your browser (by pressing f12 or right click + inspect) and check under "console" that you do not have any error since extensions could make certain elements to fail as well. Regards, |