Flarum Update Log

JoshStrobl

This post is used to provide a change log to inform our community of recent or upcoming changes to our Flarum installation. Comms Only posts are solely able to be replied to by Core Team, Mods, and Global Maintainers to facilitate a focused discussion topic and reduce noise.

JoshStrobl

Incoming Change: Re-enabling the FoF Prevent Necrobumping extension.
Occurring On: 2019-03-08T20:06:28+02:00

Previously when this extension was enabled, it was preventing users from posting entirely. This issue has since been fixed in 0.1.2 and the extension will now be re-enabled. This extension will warn a user about necrobumping a post that has not seen discussion in over a specific time, in our case I have it set to 30 days.

JoshStrobl

Change: Fixed is:unread search
Occurred On: 2019-03-26T22:59:30+01:00

Backported a fix from git to resolve is:unread search. Thanks @Justin for letting me know about the availability of the fix.

JoshStrobl

Change: To combat some recent issues with spam, I've patched out the support for signing up using an email, username, and password. New users will be required to sign up with Phabricator or GitHub (which I'd prefer at this point). Existing users can still log in with the traditional method if that is what was used. This was done after adding existing support for ReCAPTCHA (v2 + hardest security level), Stop Forum Spam integration, and Akismet integration. Ref: Current Flarum/Core issue

Occurred On: 2019-08-10T10:37:00+03:00

JoshStrobl

Change: Apparently Flarum is using the same sign-up form (instead of log-in form) components and inputs even when you're logging in with a new account over OAuth2. So I've had to disable our previous hiding of that support, so unfortunately that may mean that spam may return. 🙁 We'll just have to do our best to combat it and I'll look into writing a Flarum extension that adds a custom "security" question that only actual Linux users would know!

Occurred On: 2019-08-14T00:32:00+03:00

Thanks @abyssalmaven for bringing this to my attention

JoshStrobl

The forum has been updated to Flarum v0.1.0-beta13. Originally I was intending on updating Flarum v0.1.0-beta14 however there is too many extensions which are incompatible with it, so I opted to downgrade it to keep things as stable as possible, though beta13 is still a considerable upgrade compared to our previous version. I also kept our older version of the fof/nightmode extension to ensure our dark theme adjustments continue to work as expected. I'm sure some of you will be happy to know however that I have disabled the Prevent Necromancy extension. Most people seemed to not respect it anyways 😃

This update was done in response to some random sudden issues reported by our users, such as email change issues as well as some issues related to double posting.

Occurred On. 2020-11-02T23:47:00+02:00

P.S: Turns out the mail issues was just SendGrid having degraded services. An upgrade never would've been technically necessary. But hey, nice to have anyways.

JoshStrobl

So uhhh.

It's up-to-date now.

JoshStrobl

Removed custom styling so we can get an understanding of how things have progressed with Flarum since the last update. Updated some tag colors to hurt your eyes less.

JoshStrobl

I added new reactions emojis.

It's the little things, or the smelly things 💩

JoshStrobl

Upgraded hardware associated with forum.

ReillyBrogan

Some performance tweaks were applied to the instance running Flarum and it was also moved to being proxied through Cloudflare. The net result of this is that loading the forum should be faster most of the time and everything should just be a bit more consistently responsive.

JoshStrobl

Added a new Sync Updates tag that will be used going forward, ensuring that we have dedicated posts for updates for our intended weekly syncs, any defers, etc. These posts will not be "announce only", meaning you should be able to comment and react to your heart's desire.

JoshStrobl

Flarum has been updated to the latest 1.8.1. Apologies for the downtime, there was a short moment where Cloudflare had cached an invalid PHP error page while composer was clearing its vendor cache. Not realizing it was doing a cache hit, I went down a rabbit hole of evidently pointless debugging.

I went ahead and disabled the cache for a bit. I'll purge that cache soon and re-enable it, but for just a moment I'd like to celebrate a functioning forum again lol.

JoshStrobl

Fixed video previews. May you now endlessly consume content on the Song of the day thread again.

EbonJaeger

We now have the Best Answer plugin. You can now select the best answer in your own thread, which will highlight the post and mark the thread as Solved. This is enabled for topics with the Support tag, and Off-Topic->How Do I... tag.

ReillyBrogan

Updated the Flarum server to the latest PHP and OS bits and bytes. While I was at it I upped the size of the PHP opcache and enabled the new-ish PHP JIT compiler, so hopefully that results in the forum feeling a bit snappier.

EbonJaeger

Added two plugins:

Diff: Allows viewing a post's edit history by clicking the Edited text at the top of the post
Moderator Warnings: Allows moderators to warn users with notes, allowing for greater organization and accountability

EbonJaeger

Because we have added a plugin to view edit history, users can now edit their posts whenever they want.

ReillyBrogan

Did a quick restart a while ago for system updates.