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

Problem: Secondary language pages not loading Solution: Upgrade WooCommerce Multilingual to WCML Relevant Documentation:

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.

This topic contains 3 replies, has 2 voices.

Last updated by phetM 1 year, 1 month ago.

Assigned support staff: Bruno Kos.

Author Posts
April 24, 2019 at 3:23 pm


After updating to all recent WPML plugins version, secondary language (english) pages are not loading. Sometime WooCommerce pages sometime loads, but it is very slow to load...

I'm also getting "Internal Server Error" when trying to finalise the installation of WPML Media.

April 24, 2019 at 9:06 pm #3676953


I manage to completely activate WPML Media. I had to deactivate every other non WPML plugins to do so.

But still, that did not resolve the issue. After deactivating/reactivating every plugins, WooCommerce Multilingual seems to be the culprit...

Currently, I have WooCommerce Multilingual deactivated and the site is running. But, that means I can't translate any new products...

April 25, 2019 at 5:05 am #3678863

Bruno Kos

Languages: English (English )

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


Thank you for contacting WPML support!

Can you please check this errata and try what has been suggested there?

If this works for you, let me know. This patch will end up officially in WCML 4.6.2.

Another thing - could you make sure your server conforms to our minimum requirements?

Based on provided debug information, I can see the following - WP Memory Limit: 40M.

Specifically, could you set WP Memory limit to at least 256MB?

If unsure on how to set this, you can consult your host/server admin to do this. After you increase this value, you can confirm it by checking on WPML -> Support by finding the “Memory limit” value.

Bruno Kos

April 25, 2019 at 6:13 pm #3684959


Hey Bruno, just tackled all of your suggestions and it worked fine.

FYI, wp_memory_limit was actually configured in wp-config.php. But it was a the wrong place in the file. It had to be inserted right after this line : define( 'WP_DEBUG_LOG', true );

Thanks for the help again!