There's also 8.0.14 available on my hosting, maybe I shouldn't use 8.1.1 for it being too recent?

Just updated 2 servers - test bench and community forum. Easy and smooth update in both cases.
Well done and thanks to whole team!

OK, I changed the PHP on my shared hosting to 8.0.14 this time (not 8.1.1) and executed the three commands, now the forum works.

However there's something strange: if I execute php flarum info I still see PHP version: 7.4.27 and if I execute php -v it's 7.4.27, however if I open the dashboard in the administration panel, I see PHP 8.0.14.

    CyberGene Right, that's because the command line version of PHP, and the version used by php-fpm to serve your website, are independent.

        askvortsov, thanks, so does it mean my Flarum installation is fully utilizing PHP 8.0.14 now (and the supposed speed increase)?

        As a side note, it seems that Flarum doesn't work with 8.1.1, at least on my hosting, but works with 8.0.14.

            🚀

            Smooth and crispy, as usual, congrats!! I can't wait to get more time to finish my theme 🙂

            askvortsov here are the errors I've seen with 8.1.1:

            [20-Jan-2022 19:34:32 UTC] PHP Deprecated:  Return type of Flarum\Foundation\Config::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/customer/www/mydomain.com/public_html/forum/vendor/flarum/core/src/Foundation/Config.php on line 61
[20-Jan-2022 19:34:32 UTC] PHP Deprecated:  Return type of Flarum\Foundation\Config::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/customer/www/mydomain.com/public_html/forum/vendor/flarum/core/src/Foundation/Config.php on line 56
[20-Jan-2022 19:34:32 UTC] PHP Deprecated:  Return type of Flarum\Foundation\Config::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/customer/www/mydomain.com/public_html/forum/vendor/flarum/core/src/Foundation/Config.php on line 66
[20-Jan-2022 19:34:32 UTC] PHP Deprecated:  Return type of Flarum\Foundation\Config::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/customer/www/mydomain.com/public_html/forum/vendor/flarum/core/src/Foundation/Config.php on line 71
[20-Jan-2022 19:34:32 UTC] PHP Deprecated:  Return type of Tobscure\JsonApi\Document::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/customer/www/mydomain.com/public_html/forum/vendor/tobscure/json-api/src/Document.php on line 222
[20-Jan-2022 19:34:32 UTC] PHP Deprecated:  mb_strwidth(): Passing null to parameter #1 ($string) of type string is deprecated in /home/customer/www/mydomain.com/public_html/forum/vendor/illuminate/support/Str.php on line 350
[20-Jan-2022 19:34:32 UTC] PHP Deprecated:  strtolower(): Passing null to parameter #1 ($string) of type string is deprecated in /home/customer/www/mydomain.com/public_html/forum/vendor/illuminate/database/Query/Builder.php on line 836
[20-Jan-2022 19:34:32 UTC] PHP Fatal error:  Uncaught Laminas\HttpHandlerRunner\Exception\EmitterException: Unable to emit response; headers already sent in /home/customer/www/mydomain.com/public_html/forum/vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php:19
Stack trace:
#0 /home/customer/www/mydomain.com/public_html/forum/vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitterTrait.php(36): Laminas\HttpHandlerRunner\Exception\EmitterException::forHeadersSent()
#1 /home/customer/www/mydomain.com/public_html/forum/vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitter.php(27): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->assertNoPreviousOutput()
#2 /home/customer/www/mydomain.com/public_html/forum/vendor/laminas/laminas-httphandlerrunner/src/RequestHandlerRunner.php(98): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->emit(Object(Laminas\Diactoros\Response\HtmlResponse))
#3 /home/customer/www/mydomain.com/public_html/forum/vendor/flarum/core/src/Http/Server.php(44): Laminas\HttpHandlerRunner\RequestHandlerRunner->run()
#4 /home/customer/www/mydomain.com/public_html/forum/index.php(26): Flarum\Http\Server->listen()
#5 {main}
  thrown in /home/customer/www/mydomain.com/public_html/forum/vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php on line 19

                luceos how is that done? Sorry, I’m not a PHP developer. I don’t see such a file. I’m on a shared hosting (Siteground). Should I create this file somewhere with some content in it?

                In the tools panel I see many PHP parameters I can set though. The closest to what you say are these:

                pgsql.ignore_notice 0
                pgsql.log_notice 0

                    luceos thanks, I will do it. However please note that Flarum didn't work with 8.1.1 at all, it wasn't just warnings. See the last line of the error I pasted above, it's a fatal error with a stack trace. Will it be ignored when I disable display_errors?

                        CyberGene the last two deprecated warnings are more of an issue actually, but this can also be caused by running composer with an older php binary from terminal. The fatal error is caused because errors were thrown before Laminas could generate the output to the browser client.

                            luceos Thanks, I will do some tests, it doesn't hurt.

                            luceos but this can also be caused by running composer with an older php binary from terminal

                            Indeed, I posted earlier that even though the Flarum forum works under PHP 8, the terminal still uses PHP 7 and I'm wondering how I can change that too but I guess that's more a question for Siteground.

                                luceos I found that there are multiple php executables supported by the terminal, for instance there's php81 that runs under the proper PHP runtime, however I can't update the symlink of the php to use it because that's a shared hosting. Is there any way to somehow instruct the composer that is invoked for various Flarum stuff to use php81 and not php?

                                    CyberGene yes:

                                    php81 composer update --prefer-dist --no-dev -a

                                    😉

                                        luceos After a lot of struggle I managed doing it. For someone else on Siteground wondering how to use it, here are the commands:

                                        php81 -d memory_limit=4096M /usr/local/bin/composer.phar update --prefer-dist --no-plugins --no-dev -a --with-all-dependencies
php81 flarum migrate
php81 flarum cache:clear

                                        BTW, all of the commands display a lot of depreciation notices in the console. But other than that things seems to work.

                                          luceos OK, all is good now, but I notice that the php_errorlog in my forum folder gets constantly filled in with warnings. I have disabled the notices as you have suggested but I think I should also disable that logging since it will quickly fill up disk space. Do you know how I can do that?

                                          Should I downgrade to 8.0.14 instead? Things seemed to be working without warning and notices, maybe it will be the safer choice after all?

                                          P.S. Downgraded to 8.0.14 with the commands as the above but using php80 and there are no warnings. I prefer being on the safe side.

                                              CyberGene if you can't disable those warnings in your logs then a downgrade makes sense.

                                              We will look at these depreciations in the coming period too, 8.1 is soon to be the recommended version (from a php maintainer perspective) anyway.