[Fechado] Translations don't work after update 4.6.1

Hello there,

Thanks for your contact, and welcome to the WPML support forum!

If you downgrade WPML to 4.6, does it work? Regardless, let's try some procedures and debugging actions. Please follow these steps:

- Just to be safe, make sure to have a website backup before proceeding
- Go to “WPML > Support“ in your admin dashboard “your-website/wp-admin.php”
- Click the “troubleshooting” link bellow the plugin versions list.
- Look for the “Clean up” section and hit these buttons:

# Clear the cache in WPML
# Remove ghost entries from the translation tables
# Fix element_type collation
# Synchronize local job ids with ATE jobs
# Synchronize translators and translation managers with ATE
# Set language information
# Fix post type assignment for translations

- Then, resend the jobs to translation

If still not working, we might be facing an interaction issue with a third-party functionality, in this case:

- Deactivate all the plugins that are not related to WPML
- Switch for a moment to a WordPress default theme like Twenty Twenty-one
- If the issue is gone, activate one by one to see with which one there is an interaction issue

Could you please tell me the results of this investigation? Also, can you enable the debug mode? Just add the following code in your wp-config.php file:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
  
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
  
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
  
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );

Please check the following links to read more about debugging with WordPress.
- https://codex.wordpress.org/Debugging_in_WordPress
- https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging

After adding the code above, try to reproduce the issue again and check if you'll find a debug.log file inside the wp-content folder. If you locate it there, kindly send us the last lines here in the ticket.

Regards,
Mateus.

Hello there,

Thanks for your reply.

That is expected, it is not possible to bulk auto translate from the second languages to any other language. The only way to get this content translated would be to:

- go to WPML -> Translation Management -> Dashboard
- change to the desired language that should be translated
- select the content you want to translate and send them to translation normally
- now go to WPML -> Translations (or to the Translation Basket, if you have more than one user in the website)
- here you'll need to open each translation job and translate them automatically in the ATE, using the 'Translate automatically' button

We had a report a couple of days ago for this. Please check the ticket history: https://wpml.org/forums/topic/stumbled-upon-an-issue-with-product-reviews/

For now it is the best solution we can offer. Our developers are still analyzing this issue and perhaps we'll have a fix in the next versions (but this is not guaranteed, please bear in mind).

Give these steps a try and let us know how they go. Thanks!

Hey there,

Thanks for your reply.

Here's our changelog, where you can check and download the previous versions: https://wpml.org/download/wpml-multilingual-cms/?section=changelog

Please let me know if it is solved now. Thank you!

Hello there,

Thanks for your reply.

About this:: "Did not work! because my account is set up for pay-as-you-go charges"

The pay-as-you-go shouldn't be related to this. I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue, is that possible?

You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.

Our Debugging Procedures

I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.

Privacy and Security Policy

We have strict policies regarding privacy and access to your information. Please see:
https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/

**IMPORTANT**

- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: link oculto

Please, let me know if you need any additional details. Have a nice day.