Release 1.4.0

Release 1.4.0

I'm pleased to announce our newest version: 1.4.0. I've bumped this version up a bit because there are some pretty major changes under the hood.We’ve moved from Laravel 10 to 12 and Livewire 2 to 3.7. These updates give us a much more stable and future-proof base to build on, while we wait for newer...

Read the full article →

If you're interested in blogs, but haven't quite made up your mind it's worth the subscription for you, send me a DM and we'll give you a trial for a week. 🙂

Looks great! :)

Alright folks - new reactions update is live! Tweaked and improved…

I’m off on holiday until Monday, so now would be a great time for nothing to break.

If it does, any bugs will be emotionally supported upon my return. 🫣

I'm in awe of how quickly you update Spark!

All of it is really nice, but conversations & aliases really stood out to me especially.

The conversations topic is a really good point, I'm looking forward to using the new messaging system in the future. c:

What you did with aliases is really nice, too. I like that I can assign member groups to them! I'll give them a proper lookover.

Thank you for all your hard work, Cedric. 🙌😁

I love that you added a Blog feature to Premium! I don't think there's any other free forum host that offers this. You've done so much in such little time it's astonishing! Keep up the awesome work Cedric!

Thanks guys. We have sooo much more coming. 😊 Just wait until you see what @Mace has been working on for ForumSpark 2.0. 💪

All my notifications go to the home page, not the topics/comments/reactions.

I haven't been signed out at all, which confirms that is fully resolved now. Good progress is being made.

On Apr 7, 2026, fmchris10 said:

All my notifications go to the home page, not the topics/comments/reactions.

I haven't been signed out at all, which confirms that is fully resolved now. Good progress is being made.

Thanks Chris.

I would recommend to clear cache though. That would explain the notifications being brought to home. That was fixed earlier in 1.3.6 or 1.3.7 - don’t remember exactly.