Skip Navigation

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

Problem:
"An error of type E_ERROR was caused in line 3937"
There was a conflict between WPML and the latest version of Google Site Kit (1.106)

Solution:
On the moment, the workaround was to downgrade to Google Site Kit 1.105, but a few days after we released WPML 4.6.5 which solved the issue. Please update WPML.

Relevant Documentation:
https://wpml.org/errata/site-kit-by-google-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in/

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.

No supporters are available to work today on this forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Tagged: 

This topic contains 8 replies, has 3 voices.

Last updated by Nicolas V. 1 year, 3 months ago.

Assisted by: Nicolas V..

Author Posts
August 3, 2023 at 10:21 am #14148073

colourI

Hi

We updated have WPML Multilingual CMS version 4.6.4 on this website hidden link and we got a critical error on backoffice. See prints bellow.

We had to inactivate the plugin so that the website shows so I can't sent you the debug info.

critical_error_frontend.JPG
critical_error_email.JPG
August 3, 2023 at 10:45 am #14148621

Mihai Apetrei
Supporter

Languages: English (English )

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

Hi there.

Before your ticket is assigned to one of my colleagues, can you please enable the WordPress debug log?

This will allow us to see if any PHP errors are being produced.

More Info: https://codex.wordpress.org/Debugging_in_WordPress

In order to do that, edit the wp-config.php file inside your WordPress directory and insert the following lines:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Now please reproduce the issue once again.

Locate the debug log in: /wp-content/debug.log

Paste the content (if any) on a site like pastebin.com and then share the link here with us (only you and us will see the URL you are sharing).

We will be waiting for your response.

Kind regards,
Mihai Apetrei

August 3, 2023 at 11:28 am #14148977

colourI

Hi

Done. Also I was able to have the plugin enabled with PHP 7.4 and so we could get the debug info

*hidden by supporter*

August 3, 2023 at 11:33 am #14149027

colourI

Sorry wrong debug info. The correct one is this

*hidden by supporter*

August 3, 2023 at 11:38 am #14149067

Mihai Apetrei
Supporter

Languages: English (English )

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

Hi there.

That's the WPML debug information, what I recommended is that you go through the steps in the URL I shared to activate the WordPress debug mode and get the full extra errors that are not shown by default on the screen.

For the WPML debug information, there's a special field that I am enabling below now in case you want to share that again, too.

But we don't share that private information publicly, only in the private field I am enabling below.

Mihai

August 3, 2023 at 12:17 pm #14149423

Nicolas V.
Supporter

Languages: English (English ) French (Français )

Timezone: America/Lima (GMT-05:00)

Hello,

Let me jump here because I think that you have Google Site Kit installed on your site. Looking at the source code I can see <meta name="generator" content="Site Kit by Google 1.106.0" />.

Please note that there is a conflict between WPML and the latest version of Google Site Kit (1,106) as mentioned here: https://wpml.org/errata/site-kit-by-google-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in/

We already fixed it and the patch will be implemented in the next WPML release (4.6.5) which is scheduled for beginning of next week. In the meantime, please downgrade to the previous version of Google Site Kit: hidden link

August 4, 2023 at 10:17 am #14154231

colourI

Ok but if we delete the plugin we have now and upload the file you sent we'll have to to the integration with analytics again, right?

August 4, 2023 at 3:00 pm #14155607

Nicolas V.
Supporter

Languages: English (English ) French (Français )

Timezone: America/Lima (GMT-05:00)

Hello,

In your dashboard ("Plugins > Add new") you can upload the zip file and overwrite the plugin you already have.
Ref: https://wordpress.org/support/topic/conflict-between-wpml-4-6-4-and-site-kit-1-106-0/

If you don't have to wait the new WPML release next week, you can also patch the code yourself (please make a backup first).
- Edit the file wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/wpml-url-filters.class.php and replace:

if ( ! $this->is_display_as_translated_mode( $post_element ) && $post_element->is_translatable() ) {

- with:

if ( ! is_wp_error( $post_element->get_wp_element_type() ) && ! $this->is_display_as_translated_mode( $post_element ) && $post_element->is_translatable() ) {
August 10, 2023 at 7:41 pm #14184887

Nicolas V.
Supporter

Languages: English (English ) French (Français )

Timezone: America/Lima (GMT-05:00)

Hello,

Just a quick message to let you know that WPML 4.6.5 has been released already.