Gogo JILI casino login registration Philippines.REGISTER NOW GET FREE 888 PESOS REWARDS!

Resolved

(@laminedj)

Hi,

After upgrading Google site kit to Version 1.106.0

I get a conflict with WPML plugin (Translation plugin). Please advise :

Error Details

=============

An error of type E_ERROR was caused in line 3937 of the file /srv/htdocs/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php. Error message: Uncaught TypeError: Illegal offset type in isset or empty in /srv/htdocs/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php:3937

Stack trace:

#0 /srv/htdocs/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 /srv/htdocs/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/wpml-url-filters.class.php(445): WPML_Post_Element->is_display_as_translated()

#2 /srv/htdocs/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 /wordpress/core/6.2.2/wp-includes/class-wp-hook.php(310): WPML_URL_Filters->permalink_filter('https://XXX...', Object(WP_Post))

#4 /wordpress/core/6.2.2/wp-includes/plugin.php(205): WP_Hook->apply_filters('https://XXX...', Array)

#5 /wordpress/core/6.2.2/wp-includes/link-template.php(371): apply_filters('post_type_link', 'https://XXX...', Object(WP_Post), false, false)

#6 /wordpress/core/6.2.2/wp-includes/link-template.php(201): get_post_permalink(Object(WP_Post), false, false)

#7 /srv/htdocs/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1099): get_permalink(Object(WP_Post))

#8 /srv/htdocs/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(728): Google\Site_Kit\Core\Assets\Assets->get_product_base_paths()

#9 /srv/htdocs/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 /srv/htdocs/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 /srv/htdocs/wp-content/plugins/google-site-kit/includes/Core/Assets/Asset.php(129): call_user_func(Object(Closure), 'googlesitekit-b...')

#14 /srv/htdocs/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1017): Google\Site_Kit\Core\Assets\Asset->before_print()

#15 /srv/htdocs/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 /srv/htdocs/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 /srv/htdocs/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 /srv/htdocs/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 /wordpress/core/6.2.2/wp-includes/class-wp-hook.php(308): Google\Site_Kit\Core\Assets\Assets->Google\Site_Kit\Core\Assets\{closure}('')

#20 /wordpress/core/6.2.2/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)

#21 /wordpress/core/6.2.2/wp-includes/plugin.php(517): WP_Hook->do_action(Array)

#22 /wordpress/core/6.2.2/wp-admin/admin-header.php(146): do_action('admin_print_scr...')

#23 /wordpress/core/6.2.2/wp-admin/index.php(137): require_once('/wordpress/core...')

#24 {main}

  thrown

Viewing 12 replies - 16 through 27 (of 27 total)

← 1 2

robertstaddon
(@robertstaddon)

1 year, 4 months ago

I’m going to chime in here as another WPML user who just upgraded to Site Kit 1.106.0 and started experiencing this same fatal error as everyone else. I rolled back to 1.105.0 for now.

Plugin Support James Osborne
(@jamesosborne)

1 year, 4 months ago

Just to keep you updated on this @laminedj, there is an issue filed with WPML on this. You’ll find more on this below:
https://wpml.org/errata/site-kit-by-google-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in/

We are still testing this on our side and I’ll provide you with an update as soon as I have one.

@robertstaddon @scarpinoc @miguelgilmartinez Thanks for chiming in. As we’re still investigating this it would be great if you could open individual support topics. After doing so you can share your Site Health information using this form – referencing your own support topic.
Arno Peck
(@arnopeck)

1 year, 4 months ago
Same problem here, any solution?
Until solution will be available I am going to disable the plugin,
Thx
- This reply was modified 1 year, 4 months ago by Arno Peck. Reason: added 2 lines
- This reply was modified 1 year, 4 months ago by Arno Peck. Reason: correct typo
Plugin Support James Osborne
(@jamesosborne)

1 year, 4 months ago

@arnopeck Please follow updates on this from below:
https://wpml.org/errata/site-kit-by-google-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in/

We’re also investigating this from our end.

Plugin Support James Osborne
(@jamesosborne)

1 year, 4 months ago

Thanks for your patience on this @laminedj, and all those who shared additional insights. Thanks to these insights we were able to learn more on how this can occur and we’ve created the following GitHub issue:
https://github.com/google/site-kit-wp/issues/7389

Please subscribe to this issue for update. We’ll also share any resolution within this support topic. In the meantime, while this is being worked on, you may wish to downgrade to Site Kit 1.105.0 if this is impacting your wp-admin dashboard, WPML or Site Kit functionality.

Plugin Support James Osborne
(@jamesosborne)

1 year, 3 months ago

Just to let you know that we released Site Kit 1.107.0, which has a fix out for this @laminedj. Please upgrade to this latest version, at which point you should no longer encounter the same error reported previously with WPML and the same version of PHP.

robertstaddon
(@robertstaddon)

1 year, 3 months ago

I can confirm that upgrading to Site Kit 1.107.0 resolved the issue for me. Thank you!

Plugin Support James Osborne
(@jamesosborne)

1 year, 3 months ago

Glad to hear it @robertstaddon. Appreciate the update.

Miguel
(@miguelgilmartinez)

1 year, 3 months ago

I can confirm too. Great job.

Plugin Support James Osborne
(@jamesosborne)

1 year, 3 months ago

Thank you @miguelgilmartinez, much appreciated.

Thread Starter laminedj
(@laminedj)

1 year, 3 months ago

Fixed. Thanks @jamesosborne

Plugin Support James Osborne
(@jamesosborne)

1 year, 3 months ago

Thanks for the update @laminedj, good to hear it! Be sure to reach out if you run into any further PHP warnings or errors, or with any Site Kit related query. Best of luck.