Passer la navigation

Accueil › Assistance › Assistance en français › [Fermé] My website crash when WPML is activated

[Fermé] My website crash when WPML is activated

Il s'agit du forum d'assistance technique de WPML, le plug-in multilingue pour WordPress.

Il est accessible à tous, toutefois seuls les clients de WPML peuvent y publier leurs messages. L'équipe du WPML répond sur le forum 6 jours par semaine, 22 heures par jour.

Sun Mon Tue Wed Thu Fri Sat
- 6:00 – 12:00 8:00 – 12:00 6:00 – 12:00 8:00 – 12:00 6:00 – 12:00 -
- 13:00 – 15:00 13:00 – 17:00 13:00 – 15:00 13:00 – 17:00 13:00 – 15:00 -

Fuseau horaire du support : America/Lima (GMT-05:00)

Ce sujet contient 8 réponses, a 2 voix.

Dernière mise à jour par Nicolas V. Il y a 1 année et 10 mois.

Assisté par: Nicolas V..

Auteur Messages
juillet 31, 2023 à 7:07 pm #14129261

lamineD

Hi,

My site is hosted on WordPress.com.

Since today, when WPML is activated my site crashed. I had to disable it.0

Below is the error message. Please advise :
*******************
Howdy!

WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, WPML Multilingual CMS.

First, visit your website (lien caché) and check for any visible issues. Next, visit the page where the error was caught (lien caché) and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.

lien caché

To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.2.2
Active theme: Hello Elementor (version 2.8.1) Current plugin: WPML Multilingual CMS (version 4.6.4) PHP version 8.0.29

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('lien caché...', Object(WP_Post))
#4 /wordpress/core/6.2.2/wp-includes/plugin.php(205): WP_Hook->apply_filters('lien caché...', Array)
#5 /wordpress/core/6.2.2/wp-includes/link-template.php(371): apply_filters('post_type_link', 'lien caché...', 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
juillet 31, 2023 à 10:59 pm #14129821

Nicolas V.
Supporter

Les langues: Anglais (English ) Français (Français )

Fuseau horaire: America/Lima (GMT-05:00)

Bonjour,

Bienvenue sur le support de WPML. Il peut s'agir d'un problème de compatibilité entre plugins. Pourriez vous essayer WPML avec un environnement minimum sur votre site ou mieux encore sur une copie staging?
- Désactivez tous les plugins qui ne sont pas liés à WPML et changez de thème pour un thème WordPress comme 2020.
- Si l'erreur disparaît commencez à réactiver les plugins un par un ou en petit groupe. De cette manière il vous sera possible d'identifier quel plugin crée un conflit.

Activez également WP_DEBUG pour avoir le détail des erreurs PHP.
- Accédez à votre serveur via FTP et ouvrez wp-config.php (à la racine de votre installation WordPress).
- Insérez ces lignes just avant /* That's all, stop editing! Happy blogging. */

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

Reproduisez le problème, puis accédez au fichier debug.log ici: /wp-content/debug.log et copiez/collez l'information dans votre prochaine réponse.
Plus d'info: https://wordpress.org/support/article/debugging-in-wordpress/

août 1, 2023 à 6:38 am #14130531

lamineD

Hi,

If you read the error log, you can see that the issue is with the official Google Site Kit plugin but I need it to track my data.

Start at #7

So please, propose a solution.

Regards
août 1, 2023 à 11:26 am #14133205

Nicolas V.
Supporter

Les langues: Anglais (English ) Français (Français )

Fuseau horaire: America/Lima (GMT-05:00)

Hello,

Two other supporters are also working on tickets with the same issue. Can you please deactivate the plugin Google Site Kit (or downgrade to an older version) for now. We tried to replicate the issue on our servers to be able to escalate but with no luck.

Do you think you can provide us with a copy of your site?
For this, you need to temporarily install a plugin called “Duplicator” on your site. This will allow you to create a copy of your site and your content.
I have activated a private field for you where you can share those files (package + installer).
- You can exclude /wp-uploads from the copy to reduce the size
- Once the package is ready, if the files are too large to upload them to the private field, you can share a link to Google Drive, Dropbox, WeTransfer or any other similar service.

Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
https://wpml.org/faq/provide-supporters-copy-site/

août 1, 2023 à 1:00 pm #14134425

lamineD

Hi,

I fixed my issue by applying this recommendation from Google plugin support :

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

The thread is here: https://wordpress.org/support/topic/after-upgrade-issue-with-wpml/

Regards
août 1, 2023 à 1:01 pm #14134429

lamineD

I fixed my issue by applying this recommendation from Google plugin support :

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

The thread is here: https://wordpress.org/support/topic/after-upgrade-issue-with-wpml/
août 1, 2023 à 1:19 pm #14134595

Nicolas V.
Supporter

Les langues: Anglais (English ) Français (Français )

Fuseau horaire: America/Lima (GMT-05:00)

Thanks for sharing that workaround!

I forwarded your answer to the compatibility team. We're still investigating to find what change in the new version created this issue.

If you could provide clear step by step instructions on how to reproduce it that would be great!
août 1, 2023 à 3:24 pm #14135703

lamineD

I am sorry, but after 1h the issue came back. I have to reopen the ticket.

Please advise.
août 1, 2023 à 4:29 pm #14136175

Nicolas V.
Supporter

Les langues: Anglais (English ) Français (Français )

Fuseau horaire: America/Lima (GMT-05:00)

Hi,

We're still investigating but in the meantime we recommend to downgrade to a previous version of Google Site Kit.

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

Link to v1.105: lien caché

Le sujet « [Fermé] My website crash when WPML is activated » est fermé aux nouvelles réponses.