Sauter la navigation

[Résolu] HTTP 500 Error. The whole site breaks if updating Views Plugin to the latest ver

This support ticket is created Il y a 6 années et 3 mois. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

Marqué : 

Ce sujet contient 6 réponses, a 3 voix.

Dernière mise à jour par ThorstenS967 Il y a 6 années et 3 mois.

Assisté par: Nigel.

Auteur
Publications
#1116275

Hi Nigel,
I just updated some Plugin in the WordPress Backend. After the update, the whole site (including the backend) is not reachable. The HTTP Error 500 occurs. After asking Google, I renamed the plugins folder to "xplugins" and i could reach the website again. The I renamed the plugins folder to "plugins" again and activated the plugins in the backend to see, which plugin causes the crash. It is the Toolset views plugin. Please look into this, as it seems to be a high priority problem.
You can have access to the backend. I now activated all plugins again except the views plugin.
Did you also took a look into the otehr thread (https://toolset.com/forums/topic/split-automatically-calculate-age-from-date-field/page/2/)? But I think, you are busy.

#1116314

Just a quick update. I had to restore a backup from UpdraftPlus because some things were also broken on the Home-Site and the menu didn't display correct. Now I updated all plugins except the views plugin as I assume, that this will crash my site again.

#1116356

Nigel
Supporter

Les langues: Anglais (English ) Espagnol (Español )

Fuseau horaire: Europe/London (GMT+00:00)

Can you see in the PHP logs what the error actually was?

(A 500 error means a fatal PHP error, which will be shown in your debug.log if you have debugging turned on.)

I tried to access your site to get a copy, but the password you provided doesn't work.

Let me mark your next reply as private again so that you can update it.

#1116544
#1117074

I had the same error on one of my websites.
The error was as follows: "[28-Sep-2018 09:44:56 UTC] PHP Parse error: syntax error, unexpected '::' (T_PAAMAYIM_NEKUDOTAYIM) in /www/htdocs/***/wordpress/wp-content/plugins/wp-views/application/controllers/compatibility/elementor.php on line 109"

I just removed the "::" and everything worked again.

#1117110

Nigel
Supporter

Les langues: Anglais (English ) Espagnol (Español )

Fuseau horaire: Europe/London (GMT+00:00)

Hi Thorsten

We have had some other reports of the same error.

It comes from our use of the Elementor API, which it seems only works in PHP 7+.

If your server is using PHP 5.x for the time being you should avoid upgrading.

We are investigating (it's not clear whether the issue is with how we call the Elementor API or with the API itself) and I should have an update for you soon.

#1118132

Nigel
Supporter

Les langues: Anglais (English ) Espagnol (Español )

Fuseau horaire: Europe/London (GMT+00:00)

Hi Thorsten

A hotfix for this was published Friday (2.6.4.2). Please go ahead and update, and let me know if you see more errors.

#1118573

My issue is resolved now. Thank you!