madalin.ungureanu

If that works (setting ‘show_in_menu’ to true) , we will add a filter or find one that you can use in the future

Hello, We are truly sorry for the issues created. I suggest rolling back to version 2.8.3 and the paid version 1.4.1 or 1.2.8 that should be available in your account. We will release an update to fix the issues next week.

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!

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!

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!

Hello,

Did you try running the database update from the admin notice when visiting Settings->TranslatePress again?

If you are not currently using the SEO Pack addon, you can ignore the upgrade database message, it will be removed in a future update.

Hello,
Do you have the SEO-Pack addon activated ? If you are not using it you can ignore the database optimization for now, it is only intended for the SEO Pack addon.

If you have the SEO Pack addon activated can you please open a support ticket here Open Ticket – TranslatePress and write in the title your nickname so I can identify you. We will probably need more information on your part that is more suited to our support platform.

Thank you and we apologize for the inconvenience!

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.

Ok, so now the database updater runs without any errors but no slugs are migrated to the new tables ?

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.

Hello,

The plugin has been temporarily closed due to an email bounce issue. One of the email accounts associated with the plugin bounced, and it seems this is a guideline violation. We are in contact with the plugins team to get it back up as soon as possible. We apologize for the inconvenience!

Hello,

The plugin has been temporarily closed due to an email bounce issue. One of the email accounts associated with the plugin bounced, and it seems this is a guideline violation. We are in contact with the plugins team to get it back up as soon as possible. We apologize for the inconvenience!

Hello,

Yes @kzeni is right, it should have been fixed by now and I apologize for the delay. I will start working on it today.

Best Regards,
Madalin

Hello @kzeni

You are right and we apologize for this!
The explanation ( not excuse, because it should have been don by now ), is that we had some compatibility issues with WordPress 5.5 that had a higher priority.
I am sorry for this, and I will be patching this today. If you need it earlier than our release cycle please write us at https://www.cozmoslabs.com/support/open-ticket/

It was marked as Resolved by our support team because they were told it would be fixed.

Best Regards,
Madalin

• This reply was modified 4 years, 7 months ago by madalin.ungureanu.