[Resolved] How to ReTranslate Media for Previously Translated Language Pages

Your provided function crashed my server & created 14 pages, of pages, with (no title). Yes, I implemented correctly (we are a corporate level dev team). I rewrote your script to include batch processing, logging, percentage tracking, propert updating, and designation to a custom url vs. running for any admin who might hit this page. A full list of improvements can be found below:

- Custom URL Trigger: Custom URL [/save-posts/] to trigger script.
- Batch Processing: Declarative to change batchcount
- Progress Tracking: _last_processed meta key & last_processed_post_id meta keys
- Logging: Detailed Logging [wp-content/save_posts_log.txt] Each log entry includes the post type, ID, title, and percentage complete.
- Percentage: Calculated percentage complete on current post ID and maximum post ID.
- Completion: CONGRATULATIONS: All posts/products/pages on completion

That code can be found here:

// Register custom URL endpoint
add_action('init', 'custom_endpoint');
function custom_endpoint() {
add_rewrite_rule('^save-posts/?$', 'index.php?save_posts=1', 'top');
add_rewrite_tag('%save_posts%', '([^&]+)');
}

// Add query variable to catch the custom URL
add_filter('query_vars', 'custom_query_vars');
function custom_query_vars($vars) {
$vars[] = 'save_posts';
return $vars;
}

// Hook the function to template_redirect
add_action('template_redirect', 'save_posts_on_custom_url');
function save_posts_on_custom_url() {
global $wp_query;

// Check if custom URL is accessed
if (isset($wp_query->query_vars['save_posts']) && $wp_query->query_vars['save_posts'] == 1) {
save_all_posts_on_custom_trigger();
exit;
}
}

// Function to save posts
function save_all_posts_on_custom_trigger() {
global $wpdb;

// Get the last processed post ID from options table
$last_processed_id = get_option('last_processed_post_id', 0);

// Get the maximum post ID to calculate percentage complete
$max_post_id = $wpdb->get_var("SELECT MAX(ID) FROM $wpdb->posts WHERE post_type IN ('page', 'post', 'product')");

// Get the next set of posts to process
$args = array(
'post_type' => array('page', 'post', 'product'), // Process pages, posts, and products
'posts_per_page' => 300, // Limit to 300 posts per refresh
'orderby' => 'ID',
'order' => 'ASC',
'post_status' => 'any',
'post__not_in' => array($last_processed_id),
'meta_query' => array(
array(
'key' => '_last_processed',
'compare' => 'NOT EXISTS'
)
)
);
$all_posts = get_posts($args);

// Open the log file in append mode
$log_file = fopen(WP_CONTENT_DIR . '/save_posts_log.txt', 'a');
if (!$log_file) {
echo 'Could not open log file.';
return;
}

// Check if there are posts to update
if (!empty($all_posts)) {
foreach ($all_posts as $single_post) {
wp_update_post($single_post);
update_post_meta($single_post->ID, '_last_processed', time()); // Mark the post as processed
update_option('last_processed_post_id', $single_post->ID); // Save the last processed post ID

// Determine the type of post
$post_type = ucfirst(get_post_type($single_post));

// Calculate the percentage complete
$percentage_complete = ($single_post->ID / $max_post_id) * 100;
fwrite($log_file, "{$post_type} ID: {$single_post->ID} - Title: {$single_post->post_title} - Percentage Complete: " . round($percentage_complete, 2) . "%" . PHP_EOL);
}
fwrite($log_file, 'Processed ' . count($all_posts) . ' items.' . PHP_EOL);
echo 'Processed ' . count($all_posts) . ' items.';
} else {
// If no posts are found, reset the last processed post ID and log the completion message
delete_option('last_processed_post_id');
fwrite($log_file, 'No posts found for updating or all posts have been processed.' . PHP_EOL);
fwrite($log_file, 'CONGRATULATIONS: All posts/products/pages have been updated.' . PHP_EOL);
echo 'CONGRATULATIONS: All posts/products/pages have been updated.';
}

// Close the log file
fclose($log_file);
exit;
}

ACTION LOG:
1.) I ran the updated version (as it is the only script that works correctly) until completion.

The complete log can be found here (note logging implementations changed up top until I decided percentage based was the best manner): hidden link.

Completion is identified by this message when accessing [/save-posts]: CONGRATULATIONS: All posts/products/pages have been updated.

2.) I ran some tests by:

a.) Changing Admin Panel Default Language to es-us while inside of the edit admin of several products (I cannot change language on the frontend because of the another issue being experienced in an additional ticket that is getting nowhere if you want to take a look at that. It is my only other issue):

hidden link
hidden link
hidden link

So the links changed to:

hidden link
hidden link
hidden link

I then opened those pages in a new window: I GET 404 PAGE NOT FOUND FOR THESE PRODUCTS. SO LIKELY RELATIVE TO THE OTHER TICKET.

b.) Testing a different manner. I started by accessing es.ellasbubbles.com. I tested the products and pages that do seem to not be affected by the issue in another ticket:

- All of the links in the footer take me outside of es.ellasbubbles.com (so can't test this either. not sure if this is relative to the other ticket, dropping a comment there as well). What a mess

- Most pages seem to have "some" restored, with exception to a few [Note their page ID's are listed in the update log]:

hidden link
hidden link
hidden link
hidden link
hidden link

Please do conduct a thorough evaluation on your end. Awaiting your comments, resolutions, and if FTP is needed enable the secure form

Hi Lucas, diving right in:

1.) I can confirm that this NO CONTENT was created in the french Canadian language individually, and all originated from .com. This sounds like it may be another issue in itself (I originally had a ticket to retranslate the site from scratch and start over due to all of this misconfiguration and evident issues with previous versions of your plugin). Anyway, we expect all of these product and all of these pages to be properly identified as translated versions of their original .com page. I am 110% confident (as the CMO of Ella's Bubbles) that no individualized content was drafted for French Canada, and 110% of the content is a direct translation of .com

2.) From which page am I clicking "Update Needed"? The Translation Editor Accesible via pages? Are you intending that I take this action for over 600 pages? Please be more elaborate in your suggestions and replies for actions that are needed to be taken. You mention "We've already completed all pending translations for the original US-en products." What about Pages as well? Please feel free to proceed with resolutions instead; we are simply looking for resolutions to issues that are incurred from your plugin; and do not care to learn troubleshooting for issues that should not have otherwise occured. A query to "bulk complete updating" is preferred. No Credits Should be spent in this process

3.) There is no update from Itamar at this time. Right now we have the issues of:

a.] Itamar Ticket
b.] Images Issue [Identified Here]
c.] Improper synchronization of translated pages (French Canada) <-

Shall I open a third and in depth ticket regarding c? As it seems that we are going to be inside of a downward spiral of discovering more and more problems and inevitably take 10-20+ hours of support time (likely more, feel free to look at our number of tickets) until this issue is resolved. As mentioned, we are more than willing to "wipe out WPML" and restart at no expense to us. Or, if you prefer to continue to try to fix (and identifying more problems like the French Canada) along the way, I will continuously spiral into unlimited ticket creation that reaches your Second-Tier support and press this matter as absolutely hard as we need to for immediate resolutions.

As you can tell, we are tired of the issues imposed by your plugin, as well as the "open ended support in the past"; and have assigned a designated representative from our company who will be taking as many hours as absolutely possible until this plugin is 110% prestine on our website.

The ball is back in your court,

And to properly answer your question (in an effort to demonstrate how that can be done); no; we are not interested to restoring to a backup from 8 months ago