We recently switched from the XTM plugin to the Memsource plugin. The XTM plugin did not work for us, so we searched for an alternative. Our initial tests on a dev site we good, but now that we're working with existing content, we're experiencing issues. The existing content/pages are coming back as new pages, not the expected behavior using WPML. When the content is pushed back from Memsource, it creates two new pages for the translated content (Spanish & Chinese), besides the English version. See the attached image.
The existing content/pages are coming back as new pages, not the expected behavior using WPML.
You mean you do this?
- Choose any existing page
- Send it through Translation management to Memsource (even if it was translated already)
- you translate it there and complete to 100%, meaning it should return to your site through our translation proxy
- it doesn't update the translation but creates a new page?
Are you able to create a short video about the whole process and where the bug is then to be seen?
I will then consult our 2nd tier about this, as I am unsure what could be happening here.
That is correct. Existing content translated by Memsource comes back as new pages for the languages (Chinese & Spanish). If we clone them before having Memsource translate them, they come back fine. I'll work on getting you a video.
Can you tell me it is possible to emulate this problem in sandbox setup if I prepare one for you?
What does it take to implement Memsource to your site, this plugin or you need to register for the service as well (I am not familiar with how it works)? hidden link
I'm wondering if performing a reset on WPML and starting over would be of any benefit. I understand we'd lose all existing translations, but up till now, we've been only testing specific pages and reuseable blocks. What would you recommend?
I would recommend either of these:
- see with their support if they can shed some light on this
- I can setup a sandbox site for you to see if this is reproducible there
- if you provide us with all the logins and correct steps to reproduce (I do see this is complicated procedure though), maybe our compatibility team can trace the error
Reset should be the last resort and only in specific cases and when nothing has been translated yet. There is also no guarantee that this is not a bug in Memsource so resetting would not fix anything.
This is Ahmed Mamdouh from the translation proxy team.
I've checked the issue and as far as I understand (correct me if I'm wrong) that the issue mainly is you are facing an undesired behavior in some pages (not all of the pages) while trying to translate them using memsource, and when you contacted them, they advised to check some options in WPML (the used editor for the new content option) are set, and you did but you still have the same issue.
If the issue summary I mentioned in the above paragraph is right, I think it might be a compatibility issue with memsource, to make sure of that please deactivate all WPML Plugins and try to replicate the same issue, if it replicated, that's mean that the issue mainly from memsource and WPML is not part of this issue.
if it's not replicated, that means that there is a compatibility issue between memsource and WPML, in this case, you need to report this issue to memsource and let us know if they required anything from our side.
There is another possibility that memsource is having a bug or issue with original/older legacy pages in your website and in this case unfortunately we couldn't help as we are not experts in how memsource working.
