I also have similar issues. Went back to the earlier version. Hope that a newer version will update without SQL errors.
Same problem here…
1
last_error_insert_original_slugs Table 'appPigeon_1642682813.pigeon_trp_slug_original' doesn't exist
message Error inserting original slugs.
disable_automatic_translations Yes
last_query INSERT IGNORE INTO pigeon_trp_slug_original (original, type) VALUES ('product-category', 'taxonomy'), ('product-tag', 'taxonomy'), ('product', 'post-type-base'), ('uncategorized', 'term')
date_time 2024-08-22 15:32:22
timestamp 1724340742
Not a very wise idea to release such a major update of the plugin on thursday, when their support is closed on Friday, Saturday and Sunday.
Hello,
I am writing to let you know that we fixed the bug. Update TranslatePress – Business/Personal/Developer to the latest version 1.3.0/1.4.3.
After updating, please Run the database update from the admin notice when visiting Settings->TranslatePress. You will have to re-activate Automatic Translation from Settings->TranslatePress->Automatic Translation, in case it self-deactivated due to the previously encountered errors.
We apologize for the inconvenience this issue has caused. At TranslatePress we strive to make our product as reliable as possible, but some issues can still go unnoticed before launching updates. We are learning from this incident and we hope you keep your trust in our product.
Please let me know if the new update works for you.
This partial fix is not resolving the tables being empty. It doesnt import all existing and translated slugs from wp_postmeta. This is a huge issue for someone that translated slugs manually. Actually the big issue is still there, all slugs are being completely translated – again! Existing and already existing slug translations are fully ignored.
-
This reply was modified 1 year, 8 months ago by
morphiaz.
Ok, so now the database updater runs without any errors but no slugs are migrated to the new tables ?
Can you open a support ticket here Open Ticket – TranslatePress so we can continue the conversation on our support platform as it is a paid version issue, and I will probably need some more sensitive details on your part. Write your user-name in the title please so I can identify you quickly.
I encourage anyone who still has issues after updating to 1.3.0/1.4.3 to open a support ticket.
@madalinungureanu done. Pls check your support tickets.
Thank for the fix… I know it’s not solved everyone’s issues as yet, but in my case the sql error alert is now gone, and the automatic translations option is able to be activated.
We momentarily rolled back to version 2.8.3 so no more users that have the paid versions get affected until we release a more robust update. People who updated to 2.8.4 and had no issues, don’t need to do anything. People who experienced problems (it should only have happened to paid users) please open support tickets. Thank You!
Just got the same with update to 2.9.3 and business 1.5.1
My translated slugs are not woking anymore…: get this error:
Actually Table: PfJ018_trp_slug_originals has disappeared
These are the most recent 5 errors logged by TranslatePress:1last_error_insert_original_slugsTable ‘lgen_pp22byTagadart.PfJ018_trp_slug_originals’ doesn’t existmessageError inserting original slugs.disable_automatic_translationsOuilast_queryINSERT IGNORE INTO PfJ018_trp_slug_originals (original, type) VALUES (‘nouveaux-projets’, ‘post’)date_time2025-01-16 02:02:41timestamp1736992961
Plugin Support
Alex
(@alexcozmoslabs)
@greenative
If you have the pro version of TranslatePress, you should open a ticket directly on our website, https://translatepress.com/support/open-ticket/. WordPress guidelines rules prohibit discussions about pro features on the free forum.
Kind Regards,
