Skip to content Skip to sidebar

This thread is resolved. Here is a description of the problem and solution.

Problem:
If you're experiencing issues with Translation Management not loading after updating to WPML version 4.7.0, it might be due to a bug related to having many languages active, which affects the database and causes the module to fail.
Solution:
1. Ensure you have a backup or access to a staging site.
2. Disable all other plugins except for WPML plugins.
3. Switch to the WordPress default theme.
4. Check if the issue persists.
5. If the problem continues, revert to the previous version of WPML (4.6.15) manually by downloading it from here.
6. If none of these steps resolve the issue, please provide admin and FTP access to a staging site for further debugging.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, do not hesitate to open a new support ticket at WPML support forum.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 1 replies, has 0 voices.

Last updated by Dražen 6 days, 15 hours ago.

Assisted by: Dražen.

Author Posts
February 12, 2025 at 8:11 am #16694386

akakiT

Background of the issue:
I am trying to use Translation Management, but it does not load after updating to version 4.7.0.

Symptoms:
Translation Management does not load after the update.

Questions:
Why does Translation Management not load after the update?
Is there a compatibility issue with version 4.7.0?

February 12, 2025 at 8:44 am #16694656

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

thanks for contacting us, it should work fine.

1) Can you please try next:

- Make sure you have a backup or staging site
- Disable all other plugins and leave active only WPML plugins
- Switch to WP default theme
- Check if the issue still happens.

2) If issue still happens, please share admin and FTP access to the staging site so we can have a look and check what is wrong.

Regards,
Drazen

February 12, 2025 at 10:10 am #16695443

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

thanks, I can see the issue, but I can not check or debug it further on a production website.

It would be best if you could provide a staging site where I can debug, if not please provide a duplicator copy or let me know if it is okay and I can create a copy and check further.

Regards,
Drazen

February 12, 2025 at 10:14 am #16695499

akakiT

Duplicator will not work, as the website if many 10s of GBs. We tried many times. So, you have my approval to proceed with production AND treat it like staging.

There are thousands of visits on the website every hour, but it is ok to have some downtime. So please proceed. Thanks.

February 12, 2025 at 10:27 am #16695608

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

I am afraid that would not be possible since the package is also needed to further debug the issue and escalation.

Anyway, I think I figured out the issue and reproduced it on the new test site. It seems to be a bug when there are many languages active and causes issues with DB so Transaltion Management fails to load.

I have escalated it as a bug to our 2nd tier, we will check and try to provide a workaround soon, in the meantime if you need it to work you can revert to previous versions 4.6.15, manually: https://wpml.org/download/wpml-multilingual-cms/?section=changelog

Regards,
Drazen

September 9, 2025 at 1:39 pm #17387315

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

this should be fixed with latest WPML versions.

I will be closing the ticket now.

Regards,
Drazen