There has been a critical error on this website.

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

Problem:
I'm trying to edit a product but I get a critical error. I received the following error by email:

An error of type E_ERROR was caused in line 3937 of the file ..../wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php. Error message: Uncaught TypeError: Illegal offset type in isset or empty in ..../wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php:3937
Stack trace:
#0 ...../wp-content/plugins/sitepress-multilingual-cms/classes/translations/class-wpml-post-element.php(54): SitePress->is_display_as_translated_post_type(Object(WP_Error))
#1 ...../wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/wpml-url-filters.class.php(445): WPML_Post_Element->is_display_as_translated()
#2 ..../wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/wpml-url-filters.class.php(238): WPML_URL_Filters->is_display_as_translated_mode(Object(WPML_Post_Element))
#3 ...../wp-includes/class-wp-hook.php(310): WPML_URL_Filters->permalink_filter('https://coveint...', Object(WP_Post))
#4 ...../wp-includes/plugin.php(205): WP_Hook->apply_filters('https://coveint...', Array)
#5 ...../wp-includes/link-template.php(371): apply_filters('post_type_link', 'https://coveint...', Object(WP_Post), false, false)
#6 ...../wp-includes/link-template.php(201): get_post_permalink(Object(WP_Post), false, false)
#7 ...../wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1099): get_permalink(Object(WP_Post))
#8 ...../wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(728): Google\Site_Kit\Core\Assets\Assets->get_product_base_paths()
#9 ...../wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(357): Google\Site_Kit\Core\Assets\Assets->get_inline_base_data()

Solution:
This error happens due to a conflict issue between WPML and the latest version of the "Site Kit by Google" plugin.

Please check here for more details: https://wpml.org/errata/site-kit-by-google-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in/

The "Site Kit" plugin's authors are also investigating the issue (https://wordpress.org/support/topic/conflict-between-wpml-4-6-4-and-site-kit-1-106-0/)

In the meantime, please consider downgrading to the previous Site Kit version (1.105).

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: Known issue

This topic contains 9 replies, has 2 voices.

Last updated by issam 1 year, 5 months ago.

Assisted by: Mohamed Sayed.

Author	Posts
August 2, 2023 at 6:59 am #14139219
issam	I am trying to: edit the product Link to a page where the issue can be seen:hidden link try to edit any product you will get the same error I expected to see: the product details Instead, I got: There has been a critical error on this website. Please check your site admin email inbox for instructions
August 2, 2023 at 7:47 am #14139679
issam	if you need any access please let me know
August 2, 2023 at 1:54 pm #14143049
Mohamed Sayed	Hi there, Thanks for contacting WPML support. Please provide us with the WordPress debug.log, this will allow us to see if any PHP errors are being produced. More Info: https://wordpress.org/support/article/debugging-in-wordpress/ To enable it, open your wp-config.php file and look for: define('WP_DEBUG', false); And change it to: define('WP_DEBUG', true); // Enable Debug logging to the /wp-content/debug.log file define('WP_DEBUG_LOG', true); // Disable display of errors and warnings which is recommended on a live site. define('WP_DEBUG_DISPLAY', false); @ini_set('display_errors',0); Then try to reproduce the issue by editing a product and check if any errors were saved to the debug.log log file inside the /wp-content/ directory. If you can paste your debug.log to https://pastebin.com/ and provide me that link, it would be great! Kind regards, Mohamed
August 2, 2023 at 2:07 pm #14143243
issam	hi mohamed thanks for the advice but I rather provide you with login details, as my website currently is running and I do not want to do anything by mistake which would lead the website to be down please
August 2, 2023 at 2:20 pm #14143285
Mohamed Sayed	Hi, Please provide us with temporary access (WP-Admin and FTP) so I can investigate this issue further. – preferably to a test site where the problem has been replicated if possible – Your next answer will be private, which means only you and I have access to it. ❌ Please backup your database and website before providing us with access details ❌ ✙ I would also need your permission to take a local copy of your site to debug the issue locally if needed without affecting your live site. If you don't see the form below, please don't add your credentials as they will be publicly exposed: hidden link Privacy and Security when Providing Debug Information for Support: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ Thanks for your cooperation
August 2, 2023 at 5:18 pm #14144019
Mohamed Sayed	Thanks for providing the access details. I imported a local copy of your site but I can't see the issue there. I tried to edit the same product while WPML is activated but it doesn't show any errors and the product is updated. Please check here: hidden link Could you please tell me the exact steps to replicate this issue on the local copy?
August 3, 2023 at 6:10 am #14145705
issam	hi I made a video about it, as the page dashboard doesn't open even if I try to edit the product as per the attached. hidden link
August 3, 2023 at 8:35 am #14147135
issam	am getting this by mail Error Details ============= An error of type E_ERROR was caused in line 3937 of the file /home/coveinte/public_html/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php. Error message: Uncaught TypeError: Illegal offset type in isset or empty in /home/coveinte/public_html/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php:3937 Stack trace: #0 /home/coveinte/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/translations/class-wpml-post-element.php(54): SitePress->is_display_as_translated_post_type(Object(WP_Error)) #1 /home/coveinte/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/wpml-url-filters.class.php(445): WPML_Post_Element->is_display_as_translated() #2 /home/coveinte/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/wpml-url-filters.class.php(238): WPML_URL_Filters->is_display_as_translated_mode(Object(WPML_Post_Element)) #3 /home/coveinte/public_html/wp-includes/class-wp-hook.php(310): WPML_URL_Filters->permalink_filter('hidden link...', Object(WP_Post)) #4 /home/coveinte/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters('hidden link...', Array) #5 /home/coveinte/public_html/wp-includes/link-template.php(371): apply_filters('post_type_link', 'hidden link...', Object(WP_Post), false, false) #6 /home/coveinte/public_html/wp-includes/link-template.php(201): get_post_permalink(Object(WP_Post), false, false) #7 /home/coveinte/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1099): get_permalink(Object(WP_Post)) #8 /home/coveinte/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(728): Google\Site_Kit\Core\Assets\Assets->get_product_base_paths() #9 /home/coveinte/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(357): Google\Site_Kit\Core\Assets\Assets->get_inline_base_data() #10 [internal function]: Google\Site_Kit\Core\Assets\Assets->Google\Site_Kit\Core\Assets\{closure}('googlesitekit-b...') #11 /home/coveinte/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Script_Data.php(51): call_user_func(Object(Closure), 'googlesitekit-b...') #12 [internal function]: Google\Site_Kit\Core\Assets\Script_Data->Google\Site_Kit\Core\Assets\{closure}('googlesitekit-b...') #13 /home/coveinte/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Asset.php(129): call_user_func(Object(Closure), 'googlesitekit-b...') #14 /home/coveinte/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1017): Google\Site_Kit\Core\Assets\Asset->before_print() #15 /home/coveinte/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks(Object(WP_Scripts), Array) #16 /home/coveinte/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks(Object(WP_Scripts), Array) #17 /home/coveinte/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks(Object(WP_Scripts), Array) #18 /home/coveinte/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(156): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks(Object(WP_Scripts), Array) #19 /home/coveinte/public_html/wp-includes/class-wp-hook.php(308): Google\Site_Kit\Core\Assets\Assets->Google\Site_Kit\Core\Assets\{closure}('') #20 /home/coveinte/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) #21 /home/coveinte/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #22 /home/coveinte/public_html/wp-admin/admin-header.php(146): do_action('admin_print_scr...') #23 /home/coveinte/public_html/wp-admin/edit-form-advanced.php(425): require_once('/home/coveinte/...') #24 /home/coveinte/public_html/wp-admin/post.php(206): require('/home/coveinte/...') #25 {main} thrown
August 3, 2023 at 9:48 am #14147819
Mohamed Sayed	Thanks for sharing the error. This error happens due to a conflict issue between WPML and the latest version of the "Site Kit by Google" plugin. Please check here for more details: https://wpml.org/errata/site-kit-by-google-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in/ The "Site Kit" plugin's authors are also investigating the issue (https://wordpress.org/support/topic/conflict-between-wpml-4-6-4-and-site-kit-1-106-0/) In the meantime, please consider downgrading to the previous Site Kit version (1.105). Let me know please how that goes.
August 3, 2023 at 10:12 am #14148017
issam	wow, thank you for informing me to downgrade Site Kit to version (1.105) it fixed the issue.
August 3, 2023 at 10:15 am #14148049
issam	thank you for your help