Dieses Thema ist gelöst. Hier finden Sie eine Beschreibung des Problems und der Lösung.
Problem: The client was unable to save the translation for a "Header" template using WPML's advanced editor. Automatic translation would remain in 'pending' status, and manual translation through the advanced or classic editor would result in an endless loading upon saving.
Solution: The client discovered a workaround: 1. Navigate to WPML translation management and select the untranslated template. 2. Assign it to a translator. 3. Add it to the translation basket and assign to any translator. 4. Go to translations, take and translate the template, then edit and complete the translation. 5. Finally, go to templates, select the template, edit and publish.
We suggested closing the issue for now, as the problem might be a residue from a previous issue. We also mentioned that creating a new header could solve the problem since it would have a new ID. If the client encounters this issue again in the future, we advised them to contact us.
Please note that this solution might be outdated or not applicable to your case. If you're still experiencing 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.
Dies ist das technische Support-Forum für WPML – das mehrsprachige WordPress-Plugin.
Mitlesen können alle, doch nur WPML-Kunden können hier Fragen veröffentlichen. Das WPML-Team antwortet im Forum an 6 Tagen pro Woche, 22 Stunden am Tag.
Thanks, everything worked fine except with translation and the WPML advanced editor is working for all pages I have tested it with. There is only one tiny issue: The template "Header" translation cannot be saved. If I automatically translate it with WPML it will stay in pending forever. If I try to manually translate via advanced or classic editor, pressing "save" will load forever and nothing happens. Do you have any idea about the cause? I wouldnt mind to translate it manually. In fact, the translation is already done, i just cannot publish it...
Please try the following steps and let me know how it goes:
1- Go to WPML-> Translation Management-> Jobs tab
2- Search for the stuck job and cancel it
3- Edit the template in the default language
4- Make a minor edit by adding "V2" to the title and updating the template
5- Delete "V2" and update the template
6- Translate the template
I followed your steps several times. Neither automatic translation nor manual translations is working because whenever I press "save" it always freezes there and nothing happens anymore. If I use WPML automatic translation, it always stays in the queue. By now, I would be happy with doing it manually since just this one template "Header V2" is not working. Can you have a look and see if you can get it done? Could be just an English copy, I just want to be able to manipulate it. But I see this "Call to a member function get_main_id() on null /bitnami/wordpress/wp-content/plugins/elementor-pro/core/utils.php:80 " in the error logs. It is so strange that it just happens for this single template. Thanks
I checked your website, tried some debugging strategies, but it didn't work. I'd have to escalate the issue again.
Before doing that, since this is a specific error that might be residual from the last problem we solved, I ask you to create another header, copy the content from this one and try translating it. If that works, the issue will be solved. This way, we would create another translation ID, what might solve the issue. You can then delete the original header.
thanks so far. I just found something out what works:
WPML translation management -> select untranslated template -> assign to a translator
translation basket -> assign to any translator
go to translations -> take and translate the template, edit and complete translation
go to templates, select the template, edit and publish was possible
I fear we may get problemswith the header in the future but if we can do the translation like this, it would be fine for us now. Do you want to investigate further or should I close the issue?
Let's close the issue for now. As I said, it's probable the issue is a residue from the last problem. I think that creating a new header would solve it, since it would have a new ID.
If you ever encounter this issue in the future, please let us know.
I forgot to mention: I created a new header and it had the same issue. Another idea would be that some item within the header may cause the problem but I am only a wordpress novice so I cannot tell. Anyhow, we can move forward like this. Thanks!
