XF 2.4 general discussion, feedback, complaints, random off topic posts, etc.

In any case, it's about trust and brand respect.
I would like more communication from Kier - it's nice that the others step in, but it would be more re-assuring to hear from the top brass.

Just a monthly update to say what is going on, even if nothing much changed - just nice to know everything is ticking along.
 
I'm currently debating whether to upgrade my forum from version 2.2 to version 2.3 or wait for version 2.4. I understand that I won't have to wait four years, but even two years is not a long time :)

Can you give me a recommendation? I just don't want to go through the whole tedious process of re-adjusting plugins again in a short amount of time. Do you think most
plugins will require another adjustment to 2.4?

Thanks for your valuable work.
I'm no expert, but I found upgrading to 2.3 very smooth with the only issue being with email - which was resolved when I switched email to SMTP. Some existing addons needed updating as addon producers made new versions for 2.3 - but it wasn't many to upgrade. That gave me a feeling of satisfaction of being up to date. And if, as mentioned above, there won't be a lot of change from that to 2.4, it might be easier to get addons etc up to date first.
 
They need to add the multilink function to XFRM in 2.4. :(
What exactly do you mean with "the multilink function"? This?


While I would highly appreciate and praise if this would be implemented (the more, as it would solve limitations in other areas of XF as well) I do have my doubts. XFRM and XFMG are both embarrassingly outdated, completely neglected and literally many years (rather decades) behind any modern standards (to say it politely). Both need a really massive, complete overhaul - in their current state probably no one would use it if there was any alternative. But there is none. So really time so start working on them - absolutely agreed.

But XF2.4 was supposed to deliver mainly the new editor and it is already massively delayed. So realistically I do not see this feature in 2.4. Why exactly would "they need" to add it to exactly 2.4? The price for that would no doubt be another monthlong delay.
 
What exactly do you mean with "the multilink function"? This?


While I would highly appreciate and praise if this would be implemented (the more, as it would solve limitations in other areas of XF as well) I do have my doubts. XFRM and XFMG are both embarrassingly outdated, completely neglected and literally many years (rather decades) behind any modern standards (to say it politely). Both need a really massive, complete overhaul - in their current state probably no one would use it if there was any alternative. But there is none. So really time so start working on them - absolutely agreed.

But XF2.4 was supposed to deliver mainly the new editor and it is already massively delayed. So realistically I do not see this feature in 2.4. Why exactly would "they need" to add it to exactly 2.4? The price for that would no doubt be another monthlong delay.
This

The suggestion is great and it's from 2018... 2018 and we're in 2025! 😭😭😭😭😭😭😭
 
The suggestion is great and it's from 2018... 2018 and we're in 2025! 😭😭😭😭😭😭😭
In all fairness: Stop whining. The one I mentioned dates back to 2013 plus it has way more votes. ;) Fact is: Neither of the two will make it to 2.4 by any chance. The one you want seems no doubt helpful, but only for a tiny fraction of people. Most either won't need it or one of the many alternative ways of providing more than one link per resource does the job for them in a way that is good enough.
 
sometimes I wonder why we even have a suggestion forum, lol.
Maybe somebody suggested it back then. :p And that's only the one for XFRM. The one for XF itself counts 64 pages and 1.275 open suggestions, the oldest one dates back to 2010.

We also have a bug forum that more or less works in the same way. It currently counts 37 pages of open bugs - 733 in total, the oldest one dates back to Dec. 1st 2018. Of those 733 open bugs 31 are confirmed, 14 are waiting for feedback from the reporter, 6 are tagged as "cannot reproduce", 8 as "third party" and 0 with "future fix", "Browser issue" or "Design issue". Which leaves 733-31-14-6-8= 674 bugs w/o classification, fix or reaction, many of them for years. 110 of the bugs received just one single response over time (from anyone, sometimes from the reporter himself), 338 did not even receive a single response. They are just reported, listed, stay open and collect dust.

Probably a bit of housekeeping would be a good idea.
 
Back
Top Bottom