Try running php flarum info. It should also error but with more information. Use it with -vvv

    • [deleted]

    • Edited

    luceos no output, which is very odd

    [inoculrn@s011 discuss.guruwall.com]$ php flarum info -vvv
    [inoculrn@s011 discuss.guruwall.com]$

    No output from php flarum migrate either ??

    Try running composer dumpautoload

    • [deleted]

    • Edited
    [inoculrn@s011 discuss.guruwall.com]$ composer dumpautoload
    Generating autoload files

      [deleted] did that change the error? If not I recommend getting help on discord. I'm at the tennis court right now, it would be better if someone could take a look on your server or reproduce using the lock file.

        • [deleted]

        luceos No, it didn't. I think I'll recover from backup as it'll be quicker.

        • [deleted]

        Recovered from backup - didn't need to restore the DB.

        • [deleted]

        • Edited

        Created a DEV instance for further testing
        Tried the same process in DEV with the same results - error booting flarum.

          I had a similar issue where I was stuck on Beta 8.2, it was one of the 3rd party extensions I had installed but not enabled that was causing the issue. I'll try to reproduce and get back to you [deleted]

            • [deleted]

            Ralkage Thanks. I'm currently stripping out third party extensions in dev to see if I can get this working

              [deleted] sorry, I was referring to your upgrade haha. Do let us know if you get your instance up and running again and if you're still facing issues, I'll try my best to assist 🙂

              • [deleted]

              Right - I'm getting somewhere. If I remove the below from composer.json, I can complete the upgrade
              "jordanjay29/flarum-ext-summaries": "^0.3.1", "michaelbelgium/flarum-discussion-views": "v0.1.0-beta.8.2", "oe800/flarum-ext-bbcode-alerts": "^0.2.0", "nomiscz/flarum-ext-auth-linkedin": "v0.1.0-beta.8.0", "reflar/cookie-consent": "^0.2.0", "reflar/gamification": "^3.1", "reflar/nightmode": "^0.2.0", "reflar/polls": "^1.3", "reflar/pwned-passwords": "^0.2.0", "reflar/reactions": "1.0.0-beta.5.2", "reflar/twofactor": "^0.1.2" "saleksin/flarum-auth-google": "v0.1.0-beta.8.0.3", "symfony/process": "^4.3", "v17development/flarum-seo": "^1.0", "wiwatsrt/flarum-ext-best-answer": "^0.2.1"

              Going to install again one by one in DEV to see where it's breaking

              • [deleted]

              OK, my DEV instance has been successfully upgraded to Beta 9. Bit of a painful exercise, but these two extensions seem to be incompatible

              reflar/gamification
              reflar/reactions

              Anyone have any interest in making them so ? 🙂

              Thanks

                [deleted] not having any issues with Gamification, are or were you getting any errors while updating?

                Edit: Feel free to drop a line in each extension respective discussions for more assistance 🙂

                  • [deleted]

                  Ralkage Strange. If I install it, I get "error booting flarum"

                  [deleted] let's not spread ourselves thin. Stick to this thread please. Reflar, fof, flagrow are all reading or notifying each other.

                  Are you able to single out the actual extension? Then enable debug and check the latest flarum log file.

                    • [deleted]

                    • Edited

                    luceos As I mentioned before, it's both

                    reflar/gamification
                    reflar/reactions

                    If you install one without the other, they cause Flarum to crash independently.

                    In addition, enabling DEBUG makes no difference at all. No flarum.log file, and no log files in /storage/logs either.

                    • [deleted]

                    Anyone have any further thoughts around this ?
                    Thanks 😁

                      [deleted] Please be patient, it's only been 2 hours since your last post. Your issue will get addressed, you might just need to wait for people to do research, answer other support questions, and work on non-Flarum tasks.