Andreas W.
WPML Supporter since 12/2018
Languages:
English (English )
German (Deutsch )
Timezone:
America/Lima (GMT-05:00)
|
Anyhow, I would appreciate it if you could simply duplicate the affected page, make some edits to the original content, and let me know if you can still replicate the issue.
In case not, it would be better to close the ticket and open a new ticket once the issue occurs again.
Each supporter handles a very high number of up to 200 tickets each month. It is unlikely that someone will review each ticket. I will simply show in my stats that I took three tickets yet to solve this ticket, and this is not good for my performance rating.
|
Andreas W.
Supporter
|
Ok, keeping it open and assigned to my queue.
If you do agree, I can offer to run some tests on your site to see if I can recreate the issue. In case of translation loss, I can offer to add necessary credits for automatic translation.
Let me know if this would be possible, and I will run some tests on your site, trying to recreate the issue.
|
|
|
Thanks. This is a live site of an important customer, so no tests on it please. I should have a new smaller site this week. Or if you want, you can take a clone of this site.
|
Andreas W.
Supporter
|
Do you still wish me to take a copy of the site? If so, please use the private reply form and provide access again, as I can no longer log in.
|
|
|
Yes please. I am sorry, the customer from the new site is taking more time to send the content than we agreed before.
The login I shared on April 15, 2026 at 12:50 pm #17971433 should work again.
Can you please let me know when you have the copy, so I can remove the credentials again?
Thank you
JP
|
Andreas W.
Supporter
|
Hello JP,
I took a local copy and have it running on localhost.
You can remove the access credentials now. I will reach out again after I run some tests.
Thank you for your patience!
Best regards
Andreas
|
|
|
Hi Andreas,,
Thanks for the update.
My customer called today that only the home page of their website worked and all other pages returned a 404 error. I couldn't figure out what caused it, so I reinstated a backup. Everything works again.
Is there anything you did that could have caused this?
Thanks
JP
|
Andreas W.
Supporter
|
Hi,
I can not imagine that taking a backup with "All In One WP Migration" would have caused this. I did not take any further changes on the site.
|
Andreas W.
Supporter
|
On a local copy, I can confirm the issue currently for most of the pages.
This is an ongoing issue that is being investigated by our developers, and the only solution for now would be to unmark the orange markers and update the translations.
We are sorry for the inconvenience, and as compensation, we can offer to create the necessary credits for updating the translation.
Note that I also ran further tests, and it seems that after fixing the issue on the current affected translation, the issue does not occur again. If this will not be the case on your site, please let us know, so that we can investigate further.
|
|
|
Thanks for the updates.
About the 404 pages, I didn't mean to blame and just want to find out what happened so I know what to look for when something weird happens in future. After migration, did you (manually?) delete the AIOW plugin and backup files?
It's unlikely I am going yo see 'marked for later' again on this site. It's all handed over to the client, so I usually won't check translations anymore.
There is still this new site coming up so I'll report back when I see it happen there.
Thanks
|
Andreas W.
Supporter
|
Hi JP,
I tested on a local copy of your site, without making any further changes.
If you run into this issue again, please report it here so that we can investgiate further.
Workflow for now:
1) If you see orange markers on the translation editor, please unmark them and update the translation to 100%.
2) Now make a small edit on the original content, save the page or post, and then open the translation editor.
3) If you again see orange markers or segments have been deleted that have not been edited on the original content, then please report it to us by chat or inside the forum.
Best regards
Andreas
|
|
|
Hi Andreas,
I know you tested on a local copy. I was referring to the life site. You installed the AIOW plugin to clone the site. Then what? Did you (manually?) delete the AIOW plugin and backup files? I just want to understand what happened, nothing else.
As for the 'marked for later', I am a bit confused by the workflow for now. We already know the problem can be 'fixed' when you unmark and translate them. The whole point of my ticket was that segments are 'marked for later' on first translation and the question was why that is? What is that status for anyway?
Thanks
JP
|
Andreas W.
Supporter
|
As far as I remember, I removed the package and the plugin "All in One WP Migration". In case I missed it, please feel free to remove them.
About the workflow:
I am mentioning this, because it can be that the issue still shows up on old job but might not be replicable on a new translation job.
|
|
|
OK thanks.
But the question remains why segments are marked for later when you translate a brand new website.
|
