• A patch update broke the whole WordPress Instance from running with a fatal error.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Roll back to 7.5.0 and directly upgrade to 7.5.3. Skip the 7.5.1 update, it indeed has crash error

    Lots of customers don’t have the tech knowledge to roll back… their websites are simply showing the white screen of death! Can you not stop your release of version 7.5.1? Or force the update to 7.5.3? Because I’ve had to spend hours this week fixing this issue.

    @modred33 It works fine for me and others if you update directly to 7.5.3

    The updates keep breaking my sites. Some are fine while others crash. I have to find a viable backup and step back. Getting really frustrated.

    Here is a sample error from the error logs:

    15847#0: *265490 FastCGI sent in stderr: “PHP message: PHP Warning: require_once(/var/www/vhosts/xxxxxxx.org/httpdocs/wordpress/wp-content/plugins/shortcodes-ultimate/freemius/start.php): Failed to open stream: No such file or directory in /var/www/vhosts/xxxxxxx.org/httpdocs/wordpress/wp-content/plugins/shortcodes-ultimate/shortcodes-ultimate.php on line 31; PHP message: PHP Fatal error: Uncaught Error: Failed opening required ‘/var/www/vhosts/xxxxxxx.org/httpdocs/wordpress/wp-content/plugins/shortcodes-ultimate/freemius/start.php’ (include_path=’.:/opt/plesk/php/8.3/share/pear’) in /var/www/vhosts/xxxxxxx.org/httpdocs/wordpress/wp-content/plugins/shortcodes-ultimate/shortcodes-ultimate.php:31
    Stack trace: 0 /var/www/vhosts/xxxxxxx.org/httpdocs/wordpress/wp-content/plugins/shortcodes-ultimate/shortcodes-ultimate.php(61): su_fs() 1 /var/www/vhosts/xxxxxxx.org/httpdocs/wordpress/wp-settings.php(589): include_once(‘…’) 2 /var/www/vhosts/xxxxxxx.org/httpdocs/wordpress/wp-config.php(102): require_once(‘…’) 3 /var/www/vhosts/xxxxxxx.org/httpdocs/wordpress/wp-load.php(50): require_once(‘…’) 4 /var/www/vhosts/xxxxxxx.org/httpdocs/wordpress/wp-blog-header.php(13): require_once(‘…’) 5 /var/www/vhosts/xxxxxxx.org/httpdocs/index.php(17): require(‘…’) 6 {main}

    thrown in /va” while reading response header from upstream

    @nekojonez yes, the latest version works fine thanks! The only problem is that for quite a few customers, they downloaded the corrupt version – and their website is stuck in the white screen of death. WordPress is totally frozen so it doesn’t automatically update to the newer version., So, for over 20 customers I had to go in manually and delete Shortcodes Ultimate.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.