4.7.3 upgrade not working on multisite - Site crashed

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

Problem:
I am trying to upgrade to version 4.7.3 of WPML on our multisite as advised. After the upgrade, the site crashed. We attempted to downgrade to version 4.7.2, but the site still does not work.

Solution:
We could fix the issue by deactivating and deleting WPML 4.72 as well as string translations. Then we uploaded version 4.7.3 newly from the WPML site. Only after we then activated WPML 4.7.3 we then downloaded string translations from the commercial tab in the multisite network and activated it on the sub site.

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: Exception

This topic contains 0 replies, has 0 voices.

Last updated by svenH-12 1 week, 4 days ago.

Assisted by: Lauren.

Author	Posts
April 3, 2025 at 1:34 pm #16892596
svenH-12	Background of the issue: I am trying to upgrade to version 4.7.3 of WPML on our multisite as advised. After the upgrade, the site crashed. We attempted to downgrade to version 4.7.2, but the site still does not work. Symptoms: I received a 500 internal server error when the WPML core plugin is active. Questions: What can we do to resolve the site crash after upgrading to 4.7.3? How can we fix the 500 internal server error with the WPML core plugin?
April 3, 2025 at 3:35 pm #16893576
Lauren WPML Supporter since 10/2015 Languages: English (English ) Timezone: America/New_York (GMT-04:00)	Please test minimal settings in your staging environment and let me know if you are able to reproduce the issue.
April 4, 2025 at 4:20 pm #16898505
svenH-12	For anyone else running into this same problem: We could fix the issue by deactivating and deleting WPML 4.72 as well as string translations. Then we uploaded version 4.7.3 newly from the WPML site. Only after we then activated WPML 4.7.3 we then downloaded string translations from the commercial tab in the multisite network and activated it on the sub site. Hope this helps anyone who might run into a similar problem. IT took us quite some investigating to find the culprit.