[Closed] I am experiencing an unexpected change in the status of ALL my translations

Hello,

Thank you for reaching out and providing such detailed information.

The issue seems to be related to this errata:
https://wpml.org/errata/advanced-translation-editor-ate-removes-ampersand-from-urls/

Workaround:
In the right-upper corner of the WPML Translation Editor click the settings icon and use the option to revert the UI to the legacy layout (ATE Gen2).

Let us know if further assistance will be needed.

Best regards
Andreas

Hello,

Please go to WPML > Settings > Translation Mode and choose "Translate what you choose".

If you open now one of the translations that are "In progress" can you confirm that the status of this content is in fact at 100%?

Best regards
Andreas

Hello,

This still could be related to the known issues I mentioned earlier.
https://wpml.org/errata/advanced-translation-editor-ate-removes-ampersand-from-urls/

I would like to offer to have a closer look at the problem and request temporary access (wp-admin and FTP) to the website to investigate this issue further.

You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.

IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.

The private response form looks like this:
hidden link

Next time you reply, click "I still need assistance."

Video:
hidden link

Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.

Best regards
Andreas

Maybe, we could use a snippet to call save_post() on all your contents, which should solve the translation status issue, but it will not update the translated content, in case an update is indeed expected.

Bulk save all posts and pages of your site, by adding this snippet to the end of the functions.php of your theme and then going to wp-admin/edit.php screen (all posts list):

// Add a function to the admin_init hook
add_action( 'admin_init', 'save_all_posts_on_refresh' );
 
// Define the function to save all posts on refresh
function save_all_posts_on_refresh() {
  // Check if the current page is the posts page
  global $pagenow;
  if ( $pagenow == 'edit.php' ) {
    // Get all the posts
    $args = array(
      'post_type' => array('page', 'post'),
      'numberposts' => -1
    );
    $all_posts = get_posts( $args );
    // Loop through all the posts and update them
    foreach ( $all_posts as $single_post ) {
      wp_update_post( $single_post );
    }
  }
}

Then remove the snippet again.

Honestly, at the moment I do not know what triggered the status update on your translations.

It is expected, that once the original content changes, as status update is triggered. This does not need to be a text change.

Even a setting or design change con trigger a status update. Also adding new plugins, like for example a plugin that adds new fields to all posts could trigger such behavior. Or adding new taxonomies to posts could also trigger a status update.

Do you maybe recall that such changes were made?

I am asking, as I review a few posts and on most of those it looked like more than one segment was edited on the original content.

About the markers:
As those markers handle HTML they will need to be connected on the translated content, as otherwise it would break the HTML markup.

If you set a marker on various words of text it might be that those words will be structured differently or even be mixed up between words that are not part of the original marker, once the automatic translation engine will create the translation.

The engine will likely pick what sounds more natural and correct when it comes to grammar in different languages.

This is what happened on your example content.

If you use DeepL as translation engine you could try to intervene into such behavior by using the Glossary feature of the Advanced Translation Editor:

https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/how-to-create-and-manage-glossary-entries/

Surely, our developers are always looking into ways to optimize such behavior but for now such issues are expected and can only be adjusted manually.