I've tried accessing the second link. I get the screenshot attached. If i select 'I understand - continue editing', I don't see any translatable content, just the regular WP post editor.
And when I visit hidden link, there's still raw html-shortcode at the bottom of the page, and the text at the top is still not translated.
To be clear: I may be able to fix the not translated items myself, my main concern is all the raw html-shotcodes that are being outputted on several pages. I really need a fix for that!
Btw, can you please edit the links i've posted to hidden links as well? I don't see an option to do that.
thanks for the screencast, that defiantly helps. I see now you're using a totally different route then I did; I'm using the automatic translation function, not the old way like you did.
I've translated some of the strings in the Dutch language, using the same method as you did, on the same page. The verbose HTML output is still there on the bottom of the page: hidden link
Regarding the Dutch translation, once it's completely translated, the shortcodes at the bottom of the page should be removed, as demonstrated here: hidden link
It is indeed great news to see the shortcodes are disappearing as soon as translation is complete. I'm still wondering how this could have happend; I like to know the source of an issue, so I can prevent the issue from appearing again.
On the page with the hidden-link you shared, the content at the top of the page is still not translated. It has been translated for years. How can we fix that?
And also for that issue: what might be causing this?
Could you also please share the raw custom XML? It seems like the staging env is somehow broken, and I can't take it from there. It would like to place the custom XML on the Live site, and then overwrite the staging env, so we can start working from there.
When a translation is incomplete, it typically displays the existing content from your manual translations. In this case, the layout and options were already broken. Upon completing the translation, the Classic Translation Editor copies the layout and options from the primary language page, which resolves the issue.
Regarding your mention of "hidden-link," could you please clarify what this refers to? It would be helpful to see some screenshots for better understanding.
Here is the custom XML configuration. After inserting it, please make minor changes to the primary language page to ensure the contents are resynchronized.
Thanks for the custom XML. I've copied that to the live-server.
Your explanation of what happens when a translation is incomplete, sounds understandable, although I don't really get why this wasn't the way things worked for the previous years. We never had raw shortcodes on pages before, even if a translation wasn't complete.
I think I'm seeing the real cause here: we've switched from manual translation to the new default. And now a lot of pages that previously were 100% translated, aren't anymore. And pages that weren't 100% translated, just didn't show untranslated content before, but now show raw shortcodes.
We've spend hundreds of dollars on translating content. Some of that is now gone, migrating to the new default mode. And when pages are not fully translated, shortcodes show up.
How did we lost all those manual translations, when we switched to the new default translating modus, and how do we get it back without spending even more money?
To manage this, I recommend changing the translation method for one page at a time. Then, use the Advanced Translation Editor to translate the content. Once translated, it will be saved in the translation memory, explained ttps://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/
If you need to revert to manual translation, you can switch it back, and the translations should return to their previous state.
Thanks for clarifying this.
Switching back to classic translation, still meant a lot of translations were lost. Translations we've spend a few hundred dollars on.
I'm now activating the pay-as-you-go automatic translation to get all content translated again, because we do need to get this website back online asap. I do hope the credits needed will be compensated: there's no warning or explanation stating that switching from classic to advanced means translations are lost, and that reverting back to classic won't bring them back. Yes, there's an article about it, as you pointed out, but we just simply changed the setting in the plugin, without getting any warning at all. So I do hope you will start the process that will be refunding the credits used for updating translations now.
When all translations are done using Automatic Translations, I hope we can start looking into the remaining issues, where some content is not translatable at all.
Thank you for your feedback. Regarding the translation fees you've incurred externally, please note that we do not refund credits used for updating translations because manual translations using the Classic Translation Editor are not recorded in our system. Moving forward, we will enhance our communication regarding system limitations. You can find more information on how translation memory works in our system https://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/
Could you please specify any other translation issues you are experiencing? Additionally, could you confirm if you are currently working on the production or staging site?
We appreciate your patience as we work diligently to resolve these issues promptly.
The topic ‘[Closed] Translation editor no longer working’ is closed to new replies.
