The cursor jumps inside the advanced translator fields - That is super annoying!!! Why dont you fix ...

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

Problem:
You are experiencing an issue where the cursor jumps to the start of the string while typing in the advanced translator fields of WPML, which is very annoying.
Solution:
We have identified that this is a known issue and it has been added to our developer's queue for a fix. Unfortunately, we cannot provide a specific timeline for when this will be resolved. We have requested that this issue be prioritized, although it has not been widely reported by many clients yet. If you're experiencing this, we recommend checking if your issue matches the one discussed here: WPML ATE issue.

Please note that the solution provided might be irrelevant if it's outdated or not applicable to your 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 the problem persists, please open a new support ticket here.

0% of people find this useful.

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: ATE

This topic contains 9 replies, has 2 voices.

Last updated by Bruno Kos 12 months ago.

Assisted by: Bruno Kos.

Author	Posts
October 16, 2024 at 5:23 am #16293148
marcusB-32	Background of the issue: I am trying to edit text using the advanced translator fields in WPML, but the cursor jumps unexpectedly. Symptoms: The cursor jumps to the start of the string while typing, which is very annoying. Questions: Why does the cursor jump inside the advanced translator fields? Why hasn't this issue been fixed yet?
October 16, 2024 at 5:37 am #16293169
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	Can you tell me if this is what you are describing? https://wpml.org/forums/topic/wpml-ate/ I see that this issue is added to our developers queue, but I can't say when will it be fixed. I asked this to be checked with higher priority, even though not many clients reported this as of now.
October 16, 2024 at 7:38 am #16293607
marcusB-32	I will record a video next time it happens - it is rendering the whole solution quite useless or at least highly annoying to use.
October 16, 2024 at 9:37 am #16294478
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	I see, if not the same issue, please record a video using tool such as hidden link so I could check with our developers.
October 16, 2024 at 11:49 am #16295143
marcusB-32	I now have a video but I can not attach it here, but its obvious whats happening. The cursor jumps to the beginning of the string when the autosave kicks in. I am on MAC with the latest Chrome. I would also appreciate if you could help me with the following other issues: 1. In the advanced editor, I can only save once all translations are complete. That is problematic when work can not be finished in one session: 2. The progress indicator does not always update 3. Using AI/Autotranslate for translation only works globally for all untranslated strings (via the button top left). Translating just single strings is not possible. Note that I have turned off Google, DeepL and MS translation and only use your AI translation. Maybe thats the cause. Before I could translate individual strings. That is much better, as it allows to keep track of what is newly translated versus already present. Lastly. Please explain to me: If I change the Layout (using elementor) in the English Master Content. Do these layout changes get applied to the other languages? It seems so, but I do not understand how consistent it is. What can break the synchronization and can a broken synchronization be healed? Your help is greatly appreciated. Regards, Marcus Baur
October 16, 2024 at 11:51 am #16295146
marcusB-32	Find video here: hidden link
October 16, 2024 at 12:45 pm #16295555
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	Yes, the issue with cursor it the same as https://wpml.org/forums/topic/wpml-ate/, I can only wait until developers work on it and update here. As for not completing the translation, you save the translations you did into translation memory and then click to go back to WordPress (see my images). For the WPML AI translation engine thing, this being still in beta it is possible that it is not yet connected to our ATE as other engines, however I still raised the ticket for our development team. For the layout synchronization, the layout are synchronized as soon as you open the translation and mark it as completed ( this step is needed, unless you're using translate everything mode which does the whole process automatically). If this process somehow fails, which is quite rare, the cause can be just as with any other software - a sudden and random bug or a minor glitch that is hard to predict.
October 17, 2024 at 8:45 pm #16301994
marcusB-32	Very helpful reply! I finally understood how the content sync works. Very sad though that this does not get fixed: https://wpml.org/forums/topic/wpml-ate/ To me it pretty much makes WPML unusable. I hope it gets fixed soon. I also hope the AI translation becomes available for individual strings. Best M.
October 17, 2024 at 8:51 pm #16302066
marcusB-32	I think the jumping cursor issue only happens when AI translation is enabled. I disabled it for now.
October 21, 2024 at 6:01 am #16310152
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	I checked with our ATE team about this. Currently, the option for individual segment translation isn't available in WPML AI. The reason for this is that AI is optimized to handle entire pages more efficiently. Processing smaller sections individually would require more resources and is less efficient at the moment. We're always looking into ways to improve our tools, but this specific feature won't be changed at the moment.