After upgrade issue with WPML

Thanks for reaching out @laminedj. So we can determine more on this please share the following:

1. Your Site Health information. You can use this form to share privately if preferred.??
2. Do you encounter any loss of functionality within Site Kit or with your WPML plugin, either via the translations or on any WPML wp-admin pages?
3. Have you reached out to the WPML support team on this? The error you’re facing is similar to one reported with their plugin support team.

Let me know if you have any questions with the above.

Same situation. It looks it is trying to get a value from a non-existing array key/position.

Only happens when you are a logged in admin.

• This reply was modified 1 year, 4 months ago by Miguel.

Thanks for the input @miguelgilmartinez. I’ll check this with the team. There is also more details on this from another impacted user in this support topic, with an update from their query with WPML.

If you’d like to open an individual support topic I can also share details on this when discussing with the team.

Hi @jamesosborne

Thanks for your quick answer.

1/ Form sent

2/ When Google site kit is activated I can’t access wordpress admin panel

3/ Yes. They told me is plugin conflict after I have updated GSK

Regards

Thanks, @jamesosborne . It happens with Site Kit by Google 1.106.0 and WPML Multilingual CMS 4.6.4.

I had Site Kit by Google 1.105.0 and WPML Multilingual CMS 4.6.4 and everything worked fine.
JFYK.

Appreciate the update @laminedj. In that case please allow me some time to check this. I’ll report back to you today with an update. What you can do in the meantime is downgrade to Site Kit 1.105.0 if you wish. You’ll find this version below:
https://downloads.www.ads-software.com/plugin/google-site-kit.1.105.0.zip

Note also that what you’re experiencing may be a multi party plugin conflict. You can determine any such multi plugin conflict by following the steps in this guide. We’ll keep you updated on this through this support topic.

@miguelgilmartinez Appreciate the update. If you can open a support topic and then share your Site Health information referencing this support topic I can compare your WordPress environment. which may be useful while we do some troubleshooting on our side. Thank you.

@laminedj @miguelgilmartinez Just a quick update on this based on another support topic. Can you please navigate to “WPML > Settings > Post Types” and then set the post type Products to “Translatable – only show translated items“. After doing so please save this update and share whether the same occurs with Site Kit 1.106.0 active and the latest version of WPML.

Note also that I encountered database related errors after activating the same version of WPML (4.6.4) and Site Kit (1.106.0), and on my test site these were since resolved when saving post updates as above.

Still the same. It did not fix the issue. I set the product option to “Translatable – only show translated items“ then activated Google plugin and boom… site went down. Sorry and thanks, @jamesosborne

• This reply was modified 1 year, 4 months ago by Miguel.

@jamesosborne

Applying this fixed mi issue, thx :

navigate to “WPML > Settings > Post Types” and then set the post type Products to “Translatable – only show translated items“.?

Thanks for the update both.

@laminedj As you’re not longer encountering this issue I’ll close this support topic.

@miguelgilmartinez I’d be happy to investigate your case further from an individual support topic if you wish. I have a site set up for testing with the same versions as yourself. You can share your Site Health information with any accompanying information such as error logs, your Stack Trace or a recording of your experience. Thank you!

@jamesosborne

I am sorry but after 1h the issue came back. I have to reopen the suppor ttopic.

Please advise.

Not a problem @laminedj. I’ll do some more testing on this, in particular after installing your other WPML related plugins.

While I’m doing so, can you share whether you encounter the same error while using the Health Check & Troubleshooting plugin, via following the steps below.

1. Login to your live site from a Chrome browser incognito window.
2. Install and activate the Health Check & Troubleshooting plugin.
3. Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
4. From the same screen click on the “Available Plugins” tab at the top right and then click on the “Enable” option next to “Site Kit by Google“ and also WPML.
5. Update Site Kit and check does the same occur once more. If not, please enable your other plugins one by one, while in troubleshooting mode, checking for the same error each time. This will help indicate a multi party plugin conflict if any.

Note that you may need to downgrade Site Kit to 1.105.0 before performing the above. I’ll work on the same test site used for this topic previously while you perform the above.

Stack trace:
#0 /opt/bitnami/wordpress/wp-content/plugins/sitepress-multilingual-cms/classes/translations/class-wpml-post-element.php(54): SitePress->is_display_as_translated_post_type()
#1 /opt/bitnami/wordpress/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/wpml-url-filters.class.php(445): WPML_Post_Element->is_display_as_translated()
#2 /opt/bitnami/wordpress/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/wpml-url-filters.class.php(238): WPML_URL_Filters->is_display_as_translated_mode()
#3 /opt/bitnami/wordpress/wp-includes/class-wp-hook.php(310): WPML_URL_Filters->permalink_filter()
#4 /opt/bitnami/wordpress/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#5 /opt/bitnami/wordpress/wp-includes/link-template.php(371): apply_filters()
#6 /opt/bitnami/wordpress/wp-includes/link-template.php(201): get_post_permalink()
#7 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1099): get_permalink()
#8 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(728): Google\Site_Kit\Core\Assets\Assets->get_product_base_paths()
#9 /opt/bitnami/wordpress/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}()
#11 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Script_Data.php(51): call_user_func()
#12 [internal function]: Google\Site_Kit\Core\Assets\Script_Data->Google\Site_Kit\Core\Assets\{closure}()
#13 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Asset.php(129): call_user_func()
#14 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1017): Google\Site_Kit\Core\Assets\Asset->before_print()
#15 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks()
#16 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks()
#17 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks()
#18 /opt/bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(156): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks()
#19 /opt/bitnami/wordpress/wp-includes/class-wp-hook.php(308): Google\Site_Kit\Core\Assets\Assets->Google\Site_Kit\Core\Assets\{closure}()
#20 /opt/bitnami/wordpress/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#21 /opt/bitnami/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action()
#22 /opt/bitnami/wordpress/wp-admin/admin-header.php(146): do_action()
#23 /opt/bitnami/wordpress/wp-admin/index.php(137): require_once('...')
#24 {main}
 thrown in /opt/bitnami/wordpress/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 3937

Same exact problem here

https://www.francesc0legrenzi.c0m.

No error with Site Kit 1.105.0.

Is WPML or your Site Kit the problem? =)

In the meaintime, I will stay with Site Kit 1.105.0

• This reply was modified 1 year, 4 months ago by scarpinoc.