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:
Wasn't over my head, the joke was absolutely fine. The non-delivery of the punchline caused the friction, and then caused some to object to the joke itself and communication in general.
 
Last edited:
Wasn't over my head, the joke was absolutely fine. The non-delivery of the punchline caused the friction, and then caused some to object to the joke itself and communication in general.
My last response to the matter before turning into a 20-page off-topic discussion on how XenForo public relations should be: My post went over your head. It's not about the joke; it's about delivering a joke on what should be a professional software development forum in the first place.
Wasn't over my head, the joke was absolutely fine. The non-delivery of the punchline caused the friction, and then caused some to object to the joke itself and communication in general.
You believe it's fine for staff to joke about releases, etc., and I do not. Joke aside, at the core of it, that's the difference of opinion that we have.

While I recognize that in the past, "when it's released" (or something to that extent) was a running joke, it no longer becomes a joke when it's overused over a full year or two/release cycles, and it should be retired. It's obviously irritating paying customers, if you can't tell by now, and is still frequently used as a scapegoat for delivering, be it a release or news about a release.

They seemingly have enough time to joke now, but it used to be nearly strictly development talk and community support. Notice the lack of responses lately in the XenForo support forums compared to when you and I joined in about 2018. Perhaps instead of joking around, they could spend some of that effort in that, now, barren wasteland instead?
 
No more humour. Got it.
The time it took you to catch up and comprehend my complaint, you could have spent answering this question.

Could you provide me with support forums from software companies that have humor? Perhaps I have tunnel vision.
 
The time it took you to catch up and comprehend my complaint, you could have spent answering this question.

Could you provide me with support forums from software companies that have humor? Perhaps I have tunnel vision.

This forum is primarily for customers to support each other. If staff replied to every single support request here, we’d have no time for anything else. But reply we do, regardless, on a best effort basis.

You could have replied to many support threads in the time it took you to write the substantial amount of text you’ve written complaining about a very simple joke which only fell flat due to an unfortunate last minute change of plan.

Any customer with active support is able to submit a ticket if they require a response from a member of staff.
 
And if a ticket response is not forthcoming for any reason, you're more than welcome to submit another ticket or contact one of us directly.
 
And if a ticket response is not forthcoming for any reason, you're more than welcome to submit another ticket or contact one of us directly.
So, submit a second ticket because you missed the first one due to laying out your next comedy sketch?

I'll remember that one next time.

Thanks!
 
I thought we agreed there would be no more humour? If we're not allowed, neither are you!
(This was also humour)
This forum is primarily for customers to support each other. If staff replied to every single support request here, we’d have no time for anything else. But reply we do, regardless, on a best effort basis.
Seems like humour (humor) is higher on the priority list at XenForo than replying to as many customer-to-customer support forums to build a public knowledgebase (as well as strengthen customer relations), which would undoubtedly, over the years, reduce the number of tickets you'd need to handle, as a lot of the questions asked may have already been publicly answered over the past 2 decades. But, what do I know? Perhaps you have an internal system for support staff to use that spits out the answer quicker, as it's been answered before (public or private).

Back to the thread I randomly picked... 30 minutes later, and can't get a simple response along the lines of, "No, there wouldn't be any performance issues". I would only respond if I knew for certain, or at least with 80% certainty, that I'm right, but am leaning towards minimal performance issues (as well as permission errors) by using files over uploading as there are likely queries done to retrieve the file, so I abstained from giving my answer there.
 
I'm lucky that I have over 400,000 users for over a decade who don't give a **** about the internal workings of internet forum software and actually get mad when you start messing with their hug box by adding features they don't care about. I had to switch featured threads widget off they didn't want it on the forum index, more scrolling = mad at the internet :LOL:

Somethingawful still exists on a vBulletin version that died a long long time ago and remains popular to this day because the community keeps your forum alive not themes, JavaScript versions or new editors. That's just cosmetic. Don't blame the software, blame yourself for not being engaging enough to build something good enough that no one cares about a page taking 1.5 seconds to load.
 
Last edited:
Back
Top Bottom