Skip Navigation

[Resolved] error http 500 after activating framework installer

This support ticket is created 6 years ago. 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
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 5 replies, has 3 voices.

Last updated by erikS-5 6 years ago.

Assisted by: Christian Cox.

Author
Posts
#1182514

I am trying to: install reference site

when trying to activate the framework installer 3.1.1 on a clean site, no plugins except for toolset types, default theme twenty seventeen. With PHP 7,1 , 7,2 and 7,3 all the same issue -> error http 500. As soon as I remove the framework installer from plugins, site works again. It's a wordpress 5.0.3

[Sat Jan 12 00:14:42.930450 2019] [error] [pid 10734] mod_proxy_fcgi.c(848): [client 109.70.147.90:49946] AH01071: Got error 'PHP message: PHP Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in .../wp-content/plugins/types/vendor/toolset/types/embedded/includes/wpml.php on line 650PHP message: PHP Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in .../wp-content/plugins/types/vendor/toolset/types/embedded/includes/wpml.php on line 667'

#1182779

https://toolset.com/errata/php-7-3-shows-warnings-about-continue-statement-in-types/

This should be solved soon, I also pushed the Developers to include a patch on the erratum above, please follow it to see when it's solved.

#1182792

I have seen this but I also have it on php 7.2 and php 7.1 ?

#1183125

Hi, I haven't seen this specific error in PHP < 7.3, so may I log into your site using FTP to reproduce the problem? This way if the Framework Installer plugin causes a 500 error, I can quickly revert by changing the plugin directory name.

#1183142
#1183683

On this PHP 7.1.25 site, I don't get the same error. In fact, I don't get any error at all, just a blank screen. I'm not able to see any errors reported despite having logging turned on, and the server responds with a 200 instead of a 500. It's a silent failure for some reason I cannot understand.

I also created a clone of this site and installed it locally on my own machine running PHP 7.1.22, and I don't have any problems with the Framework Installer plugin. So something else server-related is going on here. Are any additional logs available for this server, like an Apache log or a separate PHP FPM log?

Is it possible to wipe this server and start over with a fresh installation of WordPress? I can see at least one non-standard file in the root directory, and I'm curious about what other customizations are in place.

#1188784

My issue is resolved now. Thank you!