Background of the issue:
Once a week, the WPML String Translation plugin causes a critical error that crashes the entire website. This can only be fixed as follows, all other options fail:
1. rename the plugin folder and thus deactivate all plugins.
2. reactivate all plugins.
IMPORTANT: The bad thing is that it is NOT possible to leave WPML String Translation deactivated. The website will work again, but then a critical error will occur on the CHECKOUT page.
Link to a page where the issue occurs: hidden link
Symptoms:
Either I leave WPML String Translation disabled, then the checkout has a critical error and doesn't work.
If I leave the plugin activated, a critical error occurs once a week (yes, really, i'm not crazy, once a week every sunday or saturday)
and the page is offline again until I fix it manually. The critical error, which occurs about once a week, has the following reason:
An error of type E_ERROR was caused in line 60 of the file /home/bm7bxku/public_html/wp-content/plugins/wpml-string-translation/classes/slug-translation/wpml-st-slug-translation-strings-sync.php. Error message: Uncaught Error: Call to a member function get_original_value() on bool in /home/bm7bxku/public_html/wp-content/plugins/wpml-string-translation/classes/slug-translation/wpml-st-slug-translation-strings-sync.php:60 Stack trace: #0 /home/bm7bxku/public_html/wp-content/plugins/wpml-string-translation/classes/slug-translation/wpml-st-slug-translation-strings-sync.php(31): WPML_ST_Slug_Translation_Strings_Sync->sync_element_slug() #1 /home/bm7bxku/public_html/wp-includes/class-wp-hook.php(324): WPML_ST_Slug_Translation_Strings_Sync->run_taxonomy_sync() #2 /home/bm7bxku/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #3 /home/bm7bxku/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #4 /home/bm7bxku/public_html/wp-includes/taxonomy.php(570): do_action() #5 /home/bm7bxku/public_html/wp-content/plugins/woocommerce/includes/class-wc-post-types.php(94): register_taxonomy() #6 /home/bm7bxku/public_html/wp-includes/class-wp-hook.php(324): WC_Post_Types::register_taxonomies() #7 /home/bm7bxku/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #8 /home/bm7bxku/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #9 /home/bm7bxku/public_html/wp-settings.php(700): do_action() #10 /home/bm7bxku/public_html/wp-config.php(105): require_once('/home/bm7bxku/p...') #11 /home/bm7bxku/public_html/wp-load.php(50): require_once('/home/bm7bxku/p...') #12 /home/bm7bxku/public_html/wp-admin/admin.php(34): require_once('/home/bm7bxku/p...') #13 {main} thrown
Questions:
How can I disable the WPML String Translation plugin without causing a critical error on the checkout page?
Why does the WPML String Translation plugin cause a critical error once a week?
have you seen that in the main folder there is an error_log file which is regularly updated? it contains no wpml errors from 5th of august, but from before.
When the debug log is enabled, the site’s front-end displays the error message instead of "Es gab einen kritischen Fehler auf deiner Website." This is the default behavior of WordPress.
To resolve the issue, we will need the most recent logs. Unfortunately, logs from July 26 will not be relevant now, so please check where the new logs are being stored.
Additionally, could you create a test site for us? This would allow us to disable everything and determine if the problem is due to a conflict.
the problem is, the logs are enabled and new entries from today are added frequently. but not from the WPML issue. this is the problem. you can check that by downloading error_log file (4MB).
Nevertheless, i created a staging site. Please see the private message from our chatlogs from before, i have edited this private message and added the credentials for the staging site.
as a hint, the problem does not occur when deactivating checkoutwc plugin before deactivating wpml string plugin.
but i need checkoutwc, so this is not the solution.
I can see the issue on the staging site here: hidden link
The problem of error not being shown still exists, nothing on log, nothing shown on the front-end so with this situation it will be impossible for me to solve the issue.
As mentioned earlier, we will need host help here and they need to allow to show errors on the front-end, if not, the only suggestion I can provide you is to disable checkoutWC.
Please ask them to enable error to be displayed on the front-end so we can debug this issue further.
i am still in contact with the hosting. i will let you know once there are any updates.
besides that. as you know, the only reason i want to deactivate string translation plugin is because it regularly causes a critical error once a week. i know there is no entry in debug log, but can't you find the error from the emails i get when the critical error occurs?
pls see the attached error email content:
5. August - critical error on whole website.
Typ E_ERROR wurde in der Zeile 60 der Datei /home/bm7bxku/public_html/wp-content/plugins/wpml-string-translation/classes/slug-translation/wpml-st-slug-translation-strings-sync.php verursacht. Fehlermeldung: Uncaught Error: Call to a member function get_original_value() on bool in /home/bm7bxku/public_html/wp-content/plugins/wpml-string-translation/classes/slug-translation/wpml-st-slug-translation-strings-sync.php:60 Stack trace: #0 /home/bm7bxku/public_html/wp-content/plugins/wpml-string-translation/classes/slug-translation/wpml-st-slug-translation-strings-sync.php(31): WPML_ST_Slug_Translation_Strings_Sync->sync_element_slug() #1 /home/bm7bxku/public_html/wp-includes/class-wp-hook.php(324): WPML_ST_Slug_Translation_Strings_Sync->run_taxonomy_sync() #2 /home/bm7bxku/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #3 /home/bm7bxku/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #4 /home/bm7bxku/public_html/wp-includes/taxonomy.php(570): do_action() #5 /home/bm7bxku/public_html/wp-content/plugins/woocommerce/includes/class-wc-post-types.php(94): register_taxonomy() #6 /home/bm7bxku/public_html/wp-includes/class-wp-hook.php(324): WC_Post_Types::register_taxonomies() #7 /home/bm7bxku/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #8 /home/bm7bxku/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #9 /home/bm7bxku/public_html/wp-settings.php(700): do_action() #10 /home/bm7bxku/public_html/wp-config.php(105): require_once('/home/bm7bxku/p...') #11 /home/bm7bxku/public_html/wp-load.php(50): require_once('/home/bm7bxku/p...') #12 /home/bm7bxku/public_html/wp-admin/admin.php(34): require_once('/home/bm7bxku/p...') #13 {main} thrown
----
31. july - critical error on whole website.
yp E_ERROR wurde in der Zeile 60 der Datei /home/bm7bxku/public_html/wp-content/plugins/vvwpml-string-translation/classes/slug-translation/wpml-st-slug-translation-strings-sync.php verursacht. Fehlermeldung: Uncaught Error: Call to a member function get_original_value() on bool in /home/bm7bxku/public_html/wp-content/plugins/vvwpml-string-translation/classes/slug-translation/wpml-st-slug-translation-strings-sync.php:60 Stack trace: #0 /home/bm7bxku/public_html/wp-content/plugins/vvwpml-string-translation/classes/slug-translation/wpml-st-slug-translation-strings-sync.php(31): WPML_ST_Slug_Translation_Strings_Sync->sync_element_slug() #1 /home/bm7bxku/public_html/wp-includes/class-wp-hook.php(324): WPML_ST_Slug_Translation_Strings_Sync->run_taxonomy_sync() #2 /home/bm7bxku/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #3 /home/bm7bxku/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #4 /home/bm7bxku/public_html/wp-includes/taxonomy.php(570): do_action() #5 /home/bm7bxku/public_html/wp-content/plugins/woocommerce/includes/class-wc-post-types.php(93): register_taxonomy() #6 /home/bm7bxku/public_html/wp-includes/class-wp-hook.php(324): WC_Post_Types::register_taxonomies() #7 /home/bm7bxku/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #8 /home/bm7bxku/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #9 /home/bm7bxku/public_html/wp-settings.php(700): do_action() #10 /home/bm7bxku/public_html/wp-config.php(105): require_once('/home/bm7bxku/p...') #11 /home/bm7bxku/public_html/wp-load.php(50): require_once('/home/bm7bxku/p...') #12 /home/bm7bxku/public_html/wp-admin/admin-post.php(19):
new:
when trying to access WPML -> theme and plugin localization, page cannot be opened and also critical error, but only on the page that i try to open.
please check the first two errors from 31. july and 5. august . i received this via email when the critical error occured, it's the same information as it would be in the debug log. so you can check the error by this.
hosting (wp-rocket.net, very good hoster) told me that the wp-config is configured correctly and it has nothing to do with their server that there are no errors logged in wp-debug and that this must have to do someting with your plugin.
to summmarize:
1. i have the errors from the emails and copied them here.
2. if you have no solution, you must ask someone from a different level from support to help me.
the fact is the following: since weeks, wpml string translation causes random errors about once a week and makes my site go offline for several hours (until i notice it).
i lost about 10.000$ of sales in total because if this.
i already opened a ticket regarding this problem before. the support didn't help me. nothing.
now you can't help me as well, even if i provide the email error logs.
AND you can't help me how to deactivate wp string translation.
forcing me to get this error again and again and lose thousands of dollars in sales over and over.
as you can undertand, this is not acceptable.
wp-rocket.net is a high performance hoster, i have premium support with them and pay 1200$ a month. they clearly told me: all server settings are correct. that the error is not logged is a problem from the wpml plugin.
you cannot tell me that your plugin causes a fatal error on my side and then blame the hosting company for the fact that the error is not logged.
I am not blaming that the hosting is creating the issue, I would need help as it's unusual for error to happen without any logs.
Anyway, I think the best way to debug this further will be to move your site to my local setup, I tried to create a backup using wp staging but was unable to, so can you provide me wp-content and database backups, you can send the backups using some file sharing platforms.
Look forward to your reply.
Thanks
The topic ‘[Closed] critical error with String Translation’ is closed to new replies.
