January patch release - 1.8.12

KBExit

Silvestrus looks like you're almost there now!

Silvestrus when I visit your site, it's asking for database password.

Edit...
Flarum encountered a boot error. Details have been logged to the Flarum log file.

Edit 2: looks like your site is online again!

Silvestrus

KBExit yes! Got it working. Well, it seems that Link Preview extension was causing trouble as well but I like that one. I will try to install it now and see if it works again.

Thanks everyone for the assistance! I appreciate.

KBExit

Silvestrus I know it's a paid extension, but Rich Embeds is extremely well polished.

Silvestrus

KBExit I know it's a paid extension, but Rich Embeds is extremely well polished.

I know it's little bit offtopic but I get error when I click on purchase.

KBExit

Silvestrus I wonder if it's because the Flarum homepage is managed by the other Flarum Entity that is splitting :/

GreXXL

Wlork I hope there will be volunteers to update if the original developer can't. But I'm waiting for the green light from @GreXXL before making any requests 🙂

The Flarum Foundation will be launching a bounty program (announcement will follow soon when I return from holday next week) to update FoF extensions and also some other important ones. Maybe its best to wait for that and then we can see whats happening.

Manoj from ONEMCO

Love it!

Mayhem

Is this the correct way to update?

composer update --prefer-dist --no-plugins --no-dev -a --with-all-dependencies
php flarum migrate
php flarum cache:clear

It worked just fine, but I remember seeing somewhere that the latest update was also supposed to do a database update.

I'm assuming this method doesn't cover that?

KBExit

Mayhem looks good to me. I think the Database Migration is only prompted for updates via Extension Manager.
https://docs.flarum.org/update

m4v3rick

I get

flarum.ERROR: TypeError: FoF\Terms\Extenders\UserPoliciesRelationship::__invoke(): Argument #1 ($serializer) must be of type Flarum\Api\Serializer\UserSerializer, Flarum\Api\Serializer\BasicUserSerializer given, called >
Stack trace:

after updating.
Reverted to 1.8.11 with a snapshot.

Edit: Did update again and disabled fof/terms (1.5.0) and forum seems to work besides only showing 1.8.11 version in the admin backend (php flarum info shows 1.8.12).

To update I used:

composer update --prefer-dist --no-plugins --no-dev -a --with-all-dependencies
php flarum migrate
php flarum cache:clear

Mayhem

KBExit Database migration is only for extensions? or do I need to enable Extension Manager and do an additional stop to complete the forum upgrade?

GreXXL

Mayhem the command php flarum migrate does do all necessary database migrations via the commandline. Hence you will not see any database password prompt in the webview. If you would use Extension Manager to update (either an extensions of flarum/core) that needs database migrations then you would see the database password page as you have not run migrations via commandline.

m4v3rick this sounds odly suspicious. If the cli php flarum info says you are running 1.8.12 you certainly are. You might want to clear any cache that you have implemented or clear the Flarum cache either via cli or in the admin panel to see if it then shows the correct version.

huseyinfiliz

m4v3rick You don't run SSH commands as root, do you? You might already be aware of this, but running SSH commands with the root user can cause issues such as the inability to clear the cache.

Capybara

huseyinfiliz As far as I know, clearing the cache as root has always worked fine, even if the entire site is owned by another user. Composer just shows a warning before running commands as root, since it’s not considered very safe

KBExit

Capybara perhaps it's an issue to clear cache as root and it changes ownership of files? Making the user useless afterwards? I haven't tried. But I could see it as such.

huseyinfiliz

Capybara KBExit The reason for this is that your root SSH session caused permission issues, preventing Flarum from writing to files like cache and logs. After you deleted those files using root privileges, Flarum recreated them with www-data permissions, effectively allowing Flarum to fix the initial error you made.

Mayhem

GreXXL Thank you.

m4v3rick

GreXXL this sounds odly suspicious. If the cli php flarum info says you are running 1.8.12 you certainly are. You might want to clear any cache that you have implemented or clear the Flarum cache either via cli or in the admin panel to see if it then shows the correct version.

Did both.
Admin panel and via "php flarum cache:clear"

huseyinfiliz
Nope, I ran the "php flarum cache:clear" as a different user.

I reverted back to 1.8.11 but will give it another try the next days.

Bavarian

Thanks so much for the steady, reliable work, everyone!

« Previous Page