XF 2.4 XenForo 2.4 status and what's new under the hood?

Where are we?​

XenForo Community PSD Edit (1).webp
TL;DR: We're working hard to release XenForo 2.4 ASAP, but it's taking longer than expected due to scope changes and strategic decisions to wait for certain upstream developments that will benefit the long-term roadmap. Here's an analogy to explain why:

Software development is like planning a cross-country expedition with multiple destinations.

When you set out for version 2.4, you're not just driving to the next town over. You're charting a course through unknown territory with several strategic stops planned along the way - each representing a major milestone or feature release.

But the challenge is the landscape keeps changing along the journey.
  • New roads open up (better technologies emerge)
  • Bridges get washed out (dependencies break or become obsolete)
  • You discover scenic routes that would benefit all future travellers (opportunities for architectural improvements)
  • Weather conditions shift (market demands or user needs evolve)
  • Your vehicle needs unexpected maintenance (technical debt must be addressed)
You can't just focus on reaching the immediate next stop. You must consider how each decision affects the entire journey ahead. Taking a shortcut to reach 2.4 faster might leave you stranded when trying to reach 3.0, 4.0 or even 5.0.

This is why scope changes occur: experienced developers are constantly recalibrating the route based on new information, ensuring the expedition can successfully reach not just the next destination, but all the strategic waypoints that follow.

The delays aren't detours, rather they're course corrections that keep the long-term journey viable.

To be slightly less cryptic, these are some of the specific challenges we have faced along the way:

A new Tiptap version is coming​

When we announced that Tiptap is coming to XenForo 2.4 it was 95% complete, and we then took a bit of a pause to work on other projects, which we have talked about since and will be discussing in this thread. Since then, Tiptap have announced Tiptap V3 which is currently in beta. Given how core the editor is to the forum experience, it makes a lot of sense to ship XenForo 2.4 with Tiptap V3 rather than Tiptap V2 as originally planned. While the changes involved are not too extensive, we also don't want to ship 2.4 with a dependency that is still in beta and subject to change. While we are not planning to wait for Tiptap V3 to be stable, necessarily, we do at least want to give it a little bit more time so we have a higher degree of confidence that we're shipping a stable editing experience.

We started talking about a rewrite (again)​

While this is not currently the direction we've decided to go in, it's responsible for us to at least consider all routes available to us to help us reach our destination.

1749736697928.webp


After nearly 8 years since the release of XenForo 2.0, many of the technologies we use are showing their age, many of the decisions we made have started to slow us down more than we would like, and as a framework, XenForo becomes a less productive framework to work with. The solution to this problem can be to start from scratch, but we have ultimately decided that this is not something we need to do at this stage.

Instead, over the next few versions, including 2.4, we will be attempting to make iterative architectural changes to the framework so that we all have greater tools at our disposal to improve both the developer and user experience, particularly focusing on the implementation of developer tools and features that have become commonplace in other frameworks, such as Laravel.

Some of our best features are simply not finished​

There are one or two features that we see requested consistently from customers in our community forums and feedback channels, and we're excited to confirm they are coming in 2.4! However, it serves no one well if we release such highly-anticipated features before they are ready and before they have the usual level of quality, polish, and extensibility you would expect from a XenForo release. We'd rather take the extra time to get them right than rush them out and disappoint users with a subpar implementation that requires immediate patches or lacks the flexibility for customisation. We'll be sharing exciting details about what these features are and how they work in the coming weeks, so stay tuned!

We can't keep up!​

I just counted and there are about 15 features that have been merged or are pending to be merged into XF 2.4 that we haven't announced yet. Some of these are smaller and aren't worthy of a dedicated HYS of their own (so they'll probably be rolled into a "miscellaneous" HYS or two), and some of these are going to be mentioned below, but while we have been "cooking" (as the kids say these days) it has meant that things like code reviews, and writing HYS posts hasn't been easy to balance. There is also potentially more stuff coming from generous contributions from esteemed developers such as @Xon and @digitalpoint, assuming we have time to implement (otherwise they will wait for... a future version).


With all of that now being said, while 2.4 is taking longer than we wanted, we have been busy and we are very much nearing the end of development.

And, while disappointing (to all of us) it is important to maintain perspective. XenForo 2.2 was released in September 2020. XenForo 2.3 was released nearly four years later. XenForo 2.4 is not 3 more years away.

But, you clicked this to find out what's new, right? So let's go.
 
Last edited:
XenForo time is an industry term used jokingly with software releases from XenForo, used to acknowledge the difference between the "promised" date for released versions stated by Valve and to the "actual" release date; "XenForo Time" includes delays but also less communication than expected. XenForo has yet to acknowledge the term, including tracking known discrepancies between ideal and actual releases on their public forum and using it in announcements about such delays. XenForo ascribes delays to their mentality of team-driven initiatives over corporate deadlines
Ouch, that is why I have not updated but am on the correct security.
 
ALL THAT SAID THOUGH... I completely agree with @Wildcat Media . In the end, all this doesn't really matter because even if XF 2.4.0 comes out tomorrow absolutely perfect, that's not what's going to get new users to forums. If you want asses in seats then you need to deliver a good site. I see nothing wrong with XF 2.3.x that would hurt user traffic in any way. The life and death of forums do not depend on the cadence of XF releases.
👍👍

The content of a forum matters the most, followed by effective moderation. Those keep members returning. Not having the latest features. Fixing issues that annoy them, like a flaky editor? Yeah, they'll appreciate that. Yet they still want to contribute to the point where they will work around any issues they find.

Keeping the search function as useful as possible is also paramount. I've suggested adding the phonetic search plugin to ElasticSearch which would more effectively help users with poor spelling find the content they are looking for, but it gets ignored. The synonym plugin would be even more important than that, as each forum has its own unique terminology. Yet again...crickets. If it's one thing we get complaints about, it's the search system. (We do help them with the crude search tools we have, but there are numerous things that can be done with Elasticsearch that the XenForo system that are simply overlooked.)
 
Actually we went from phpbb to xenforo and our forum traffic stopped a long decline ( previous editor was code based ) and we started attracting users that normally used social media, because we had a wysiwyg editor now.

Xenforo search, no matter the tuning, was worse than phpbb's, consumes way too much resources on our large site, and we've conditionally replaced it with google. That brought back growth because previously, you had to go to google to find things on our site.

These kind of things are critical functionalities for users. If you do not provide convenient functionality, users will go to social media sites instead ( this is a big reason why forums are declining - software for forums keeps falling behind other, more polished systems )

TipTap 3.0 is very important. It is a much better editor. Froala is clunky no matter how you work around it.
 
Last edited:
Xenforo search, no matter the tuning, was worse than phpbb's, consumes way too much resources on our large site, and we've conditionally replaced it with google. That brought back growth because previously, you had to go to google to find things on our site.
You replaced the in built search with Google? I think that is what they did on phpbb.com and it’s nasty. Interesting though, as I don’t find the search to be that bad.
 
elastic/enhanced search is a must-have.

You can get that from your account. It's one of XF's official addons.
Given that @briansol is a member of this forum since 2010 I'd assume that he is well aware of that... He just pointed out that in his opinion this add on is a must have. Not that he desperately wished that elastic search was availble for XF, not knowing that it has been for ages already.
 
You replaced the in built search with Google? I think that is what they did on phpbb.com and it’s nasty. Interesting though, as I don’t find the search to be that bad.

Yes, i installed a plugin that allows you to chose between a google or xf search. We modified it so It defaults to google search whenever possible so the chance of high quality results is high.

Our info goes back to 2006. Some people have over 10000 posts, so we had to expand the search limit, otherwise we couldn't reliably pull up a list of user's posts. Even a search that should result in a direct hit in phpbb, would be some pages down in xenforo search. Not good.

We have elasticsearch. it doesn't do any better. It consumes 16gb of memory itself for making xenforo searches faster. Yes, we have elasticsearch well tuned. This minimum amount of memory keeps growing. Our hosting cost is up 4x. Phpbb didn't require elasticsearch, had better search, and was faster to return results.

We briefly considered rewriting the search engine from scratch but it was a lot less expensive to just use google!
 
Back
Top Bottom