Skip Navigation

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

Problem:
The client is experiencing an Error 500 on the German language page of their WooCommerce site when WPML String is activated. Deactivating WPML String resolves the checkout issue but not the Error 500.

Solution:
1. Enable WordPress debug mode by following the guide at Debugging in WordPress.
2. Reproduce the error by visiting the problematic page.
3. Check the debug.log for errors. The logs indicated a fatal error caused by the WooCommerce plugin, specifically a missing format specifier in 'class-wc-post-types.php' on line 237.
4. Temporarily deactivate WooCommerce to confirm if the site loads without errors.

If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, please check for related known issues at WPML Known Issues and ensure all themes and plugins are up to date. If problems persist, we recommend opening a new support ticket for further assistance.

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 5 replies, has 2 voices.

Last updated by Carlos Rojas 1 week ago.

Assisted by: Carlos Rojas.

Author Posts
November 22, 2024 at 1:37 pm #16434104

philippeC-3

Background of the issue:
I am trying to have German, French, and English languages on my WooCommerce site. The issue can be seen on this page: hidden link

I have deactivated all plugins and found WPML String to be the cause. All min requirements are met and plugins at latest version.

Symptoms:
I am experiencing an Error 500 on the German language page. The English and French pages still work - if I deactivate WPML String then checkout no longer works for all languages

Questions:
Why does the German page cause an Error 500?

November 22, 2024 at 1:44 pm #16434136

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Hello,
Thank you for contacting us

I kindly ask you to follow these steps to get more information about the error:
- Activate the WordPress debug mode by following the steps described in this guide: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/
- Reproduce the error by visiting hidden link
- Share the latest fatal error registered in the debug.log file located within the wp-content folder

Looking forward to your message.
Regards,
Carlos

November 22, 2024 at 2:05 pm #16434171

philippeC-3

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the myworks-sync-for-xero domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-paypal-payments domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Weitere Informationen: Debugging in WordPress (engl.) (Diese Meldung wurde in Version 6.7.0 hinzugefügt.) in /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the mametwint domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Weitere Informationen: Debugging in WordPress (engl.) (Diese Meldung wurde in Version 6.7.0 hinzugefügt.) in /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-includes/functions.php on line 6114

Fatal error: Uncaught ValueError: Missing format specifier at end of string in /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-content/plugins/woocommerce/includes/class-wc-post-types.php:237 Stack trace: #0 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-content/plugins/woocommerce/includes/class-wc-post-types.php(237): sprintf('Alle %', 'Brand') #1 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-includes/class-wp-hook.php(324): WC_Post_Types::register_taxonomies('') #2 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #3 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #4 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-settings.php(704): do_action('init') #5 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-config.php(96): require_once('/home/bouncybo/...') #6 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-load.php(50): require_once('/home/bouncybo/...') #7 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-blog-header.php(13): require_once('/home/bouncybo/...') #8 /home/bouncybo/www/nginx/maplestore.eu/index.php(17): require('/home/bouncybo/...') #9 {main} thrown in /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-content/plugins/woocommerce/includes/class-wc-post-types.php on line 237
Es gab einen kritischen Fehler auf deiner Website.

Erfahre mehr über die Problembehandlung in WordPress.

November 22, 2024 at 2:09 pm #16434179

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Thank you for sharing the error messages.

As you can see in the Fatal Error, the cause of the problem is the Woocommerce plugin. If you deactivate Woocommerce (for testing) the German version of the site should appear again.

November 22, 2024 at 2:16 pm #16434193

philippeC-3

Strange because when I disable WPML String (with all other plugins running) then the error does not appear. Does the error log show it is woocommerce the culprit?

November 22, 2024 at 5:05 pm #16434826

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Yes, you can read in the Fatal Error message that the problem comes from Woocommerce:

Fatal error: Uncaught ValueError: Missing format specifier at end of string in /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-content/plugins/woocommerce/includes/class-wc-post-types.php:237 Stack trace: #0 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-content/plugins/woocommerce/includes/class-wc-post-types.php(237): sprintf('Alle %', 'Brand') #1 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-includes/class-wp-hook.php(324): WC_Post_Types::register_taxonomies('') #2 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #3 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #4 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-settings.php(704): do_action('init') #5 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-config.php(96): require_once('/home/bouncybo/...') #6 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-load.php(50): require_once('/home/bouncybo/...') #7 /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-blog-header.php(13): require_once('/home/bouncybo/...') #8 /home/bouncybo/www/nginx/maplestore.eu/index.php(17): require('/home/bouncybo/...') #9 {main} thrown in /home/bouncybo/www/nginx/maplestore.eu/wordpress/wp-content/plugins/woocommerce/includes/class-wc-post-types.php on line 237