Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. WordPress (Managed)
  3. Website breaks after update to v3.0

Website breaks after update to v3.0

Scheduled Pinned Locked Moved WordPress (Managed)
7 Posts 6 Posters 1.1k Views 6 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    stormgrass
    wrote on last edited by
    #1

    I tried updating two of my Wordpress installs to the latest package (v3.0.0), and it results in a critical, not very verbose, error message.

    "There has been a critical error on this website.
    
    Learn more about troubleshooting WordPress."
    

    I tried renaming the entire plugins folder while in recovery mode, in order to find out whether it's a specific plugin, but the result is the same.

    Any ideas what might be going on here?

    M jdaviescoatesJ P 3 Replies Last reply
    0
    • S stormgrass

      I tried updating two of my Wordpress installs to the latest package (v3.0.0), and it results in a critical, not very verbose, error message.

      "There has been a critical error on this website.
      
      Learn more about troubleshooting WordPress."
      

      I tried renaming the entire plugins folder while in recovery mode, in order to find out whether it's a specific plugin, but the result is the same.

      Any ideas what might be going on here?

      M Offline
      M Offline
      msbt
      App Dev
      wrote on last edited by
      #2

      @stormgrass PHP got upgraded to 8.1, make sure your plugins and themes are ready for that before updating.

      1 Reply Last reply
      0
      • S stormgrass

        I tried updating two of my Wordpress installs to the latest package (v3.0.0), and it results in a critical, not very verbose, error message.

        "There has been a critical error on this website.
        
        Learn more about troubleshooting WordPress."
        

        I tried renaming the entire plugins folder while in recovery mode, in order to find out whether it's a specific plugin, but the result is the same.

        Any ideas what might be going on here?

        jdaviescoatesJ Offline
        jdaviescoatesJ Offline
        jdaviescoates
        wrote on last edited by
        #3

        @stormgrass said in Website breaks after update to v3.0:

        I tried renaming the entire plugins folder while in recovery mode, in order to find out whether it's a specific plugin, but the result is the same.

        Sounds like it's probably a theme then.

        I use Cloudron with Gandi & Hetzner

        S 1 Reply Last reply
        0
        • jdaviescoatesJ jdaviescoates

          @stormgrass said in Website breaks after update to v3.0:

          I tried renaming the entire plugins folder while in recovery mode, in order to find out whether it's a specific plugin, but the result is the same.

          Sounds like it's probably a theme then.

          S Offline
          S Offline
          stormgrass
          wrote on last edited by
          #4

          @jdaviescoates Thank you! Apparently it was one of my plugins, but they needed to be deactivated manually, simply renaming the folder didn't work. I guess I'm gonna do that with my other installs now and see which one it is there that breaks the site.

          robiR 1 Reply Last reply
          1
          • S stormgrass

            @jdaviescoates Thank you! Apparently it was one of my plugins, but they needed to be deactivated manually, simply renaming the folder didn't work. I guess I'm gonna do that with my other installs now and see which one it is there that breaks the site.

            robiR Offline
            robiR Offline
            robi
            wrote on last edited by
            #5

            @stormgrass which plugin?

            Conscious tech

            1 Reply Last reply
            1
            • scookeS Offline
              scookeS Offline
              scooke
              wrote on last edited by
              #6

              I've had this happen to me. The quickest for me was to just restore from the most recent working backup. You are backing up, right? And yes, as @jdaviescoates says, it's definitely a plugin or theme not ready for 8.1. I suggest restoring to one of your backups, and work from within the functioning WP to deactivate the problematic plugin/theme, then upgrade.

              A life lived in fear is a life half-lived

              1 Reply Last reply
              1
              • S stormgrass

                I tried updating two of my Wordpress installs to the latest package (v3.0.0), and it results in a critical, not very verbose, error message.

                "There has been a critical error on this website.
                
                Learn more about troubleshooting WordPress."
                

                I tried renaming the entire plugins folder while in recovery mode, in order to find out whether it's a specific plugin, but the result is the same.

                Any ideas what might be going on here?

                P Offline
                P Offline
                p44
                translator
                wrote on last edited by
                #7

                @stormgrass You have to go to wp-config.php and enable DEBUG mode to understand if plugin or theme is blocking.

                Insinde wp-confing.php you will find:

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

                change to

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

                And you will see on the screen what is blocking your Wordpress instance.

                1 Reply Last reply
                2
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Bookmarks
                • Search