Update to 10.0 crashed our website
-
I updated StageShow to v10.0 yesterday evening and it immediately crashed our website. When I next tried to bring up a page on the site all I got was “There is a critical error”.
Fortunately our website host was able to restore StageShow v9.8.6 and we’re operational again. I don’t know if this is a general problem or something specific to our site. We’re running WordPress 6.7.2 and PHP 7.4
The two error messages that were repeated while the site was down were:
[20-Mar-2025 18:51:26 UTC] PHP Warning: require(/home/exeterst/public_html/wp-content/plugins/stageshow/lib/stripe-php/lib/Util/EventTypes.php): failed to open stream: No such file or directory in /home/exeterst/public_html/wp-content/plugins/stageshow/lib/stripe-php/init.php on line 16
[20-Mar-2025 18:51:26 UTC] PHP Fatal error: require(): Failed opening required ‘/home/exeterst/public_html/wp-content/plugins/stageshow/lib/stripe-php/lib/Util/EventTypes.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in /home/exeterst/public_html/wp-content/plugins/stageshow/lib/stripe-php/init.php on line 16
In normal 9.8.6 operation we get a warning message in our error_log file about once a minute. That warning is:
[20-Mar-2025 20:57:06 UTC] PHP Warning: session_start(): Cannot start session when headers already sent in /home/exeterst/public_html/wp-content/plugins/stageshow/include/stageshowlib_dbase_api.php on line 1679
Again, I don’t know if this is general or site-specific.
Sorry – I don’t have the knowledge to say exactly what these error messages mean (apart from seeing that the fatal error relates to the interaction between StageShow and our Stripe payment gateway), though I’m wondering about the syntax of the include_path in the fatal error line. But maybe others, including the StageShow author, can follow it up.
Graham
- You must be logged in to reply to this topic.