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

The title is a joke based on previous release discussion threads.
So a thread title should be taken as a joke? The previous discussion threads you are referring to are probably WordPress Drama, etc., which are off-topic.

This is posted in an official "Other XenForo discussions and feedback" forum.
Not everything in life should be taken literally.
Maybe next time you should rethink your titles and forum postings (i.e., move this to Off-Topic then) as they reflect poorly, in my off-topic feedback, on XenForo as a company, if you want a joke title but only replies that suit your in-house joke.
 
But I also can't imagine a scenario where it would be absolutely needed for categorization.
And that’s the problem. You can’t imagine it therefore it shouldn’t exist. It’s very trivial to imagine cases where multiple prefixes should exist for categorisation, even on this very site. Any topic that uses a prefix for an XF version could potentially want that. Take the questions and support board, it has primary XF version as a prefix. But some of the questions can apply to multiple versions. Ditto bugs.

Look... Let's say you're just an independent forum admin with full control over everything. Don't you think it's at least a little bit silly to completely crap on XF for not having a CMS when the forum itself already does such a damn good job?
Because it doesn’t, that’s the point. It does a great job at being a forum, but the requirements for a modern community, in many cases, go far beyond that.

You might be happy with the workarounds you’ve come up with. Your users might even be happy with it, I doubt everyone else is as easily pleased.

I’m also not “just an independent forum admin”, I’m a software developer and I’ve even been a forum software developer. I’m very aware of what is possible and what isn’t, and I engage with users as to their needs and wants, I don’t just push it out and hope for the best.

Forums are clearly standing up to the test of time and wrecking the competition of AI-generated slop and heavy-handed corporate-controlled blandness, and now, us forum admins are saying forums aren't good enough. Really?
Citation needed.

Well, that just makes me even more impressed by SMF honestly. I really do think they got the short end of the stick in terms of popularity and I have no idea why. Maybe super long development times if I had to guess...
They were already in that position 15 years ago before the 2.1 dev cycle even began. Though they are a fine lesson in how to be an ivory tower that utterly refuses to listen to the community’s needs or wants.

same thing is used but displayed totally different.
if you can not see the difference then i will not take the time to point it out to you.
He doesn’t want to see the difference, because if he admits it, it might just be real.

Not everything in life should be taken literally.
There is a very real point being made here: customers, paying customers, rightly or wrongly have an increasing impression that they’re not being listened to, that their feedback doesn’t matter. They’ll stay for the short term because the product does what they need in spite of their concerns, but the continued apparent reticence is making them think twice, especially given the competitors.

Uncomfortable truths are uncomfortable but they are also true. I sympathise immensely with your situation, possibly more than most, but change and improvement is necessary.

Being brusque with customers is also not a winning strategy, even if you feel they deserve it.
 
I know that XF 2.3/2.4 will require some front end changes to support XF3 but the backend is largely compatible. Does the XF team anticipate creating a section for XF3 in resources or is XF2 going to be updated to XF2 / XF3?
 
Most likely there will be a new category - many 2.x add-ons and styles won't work on 3 due to the new templates.
Is the syntax bound to change like it did in 1 to 2 (<xen:> to <xf:>) or will it just be the same, possibly with new attributes and even tags?
 
syntax will be change to <superduperxfversion3.0omg>
I mean I could see it as <x3:>, but the attributes changing would take an adjustment to learn. I believe some did from 1 to 2, but can't recall.

The way if statements are written, etc., would be the more challenging thing to get used to.

Additional tags to do more things without add ons would be welcomed too.
 
I mean I could see it as <x3:>, but the attributes changing would take an adjustment to learn. I believe some did from 1 to 2, but can't recall.

The way if statements are written, etc., would be the more challenging thing to get used to.

Additional tags to do more things without add ons would be welcomed too.
I dont see any reason for change these tags, they already useful and simple.
 
There are some new tags and helpers in XF3 already but little point in discussing them at this point as nothing is finalised. Also nothing too exciting either way.

2.4 is aiming for backwards compatibility so we’re not really looking to make any groundbreaking changes there.
 
There are some new tags and helpers in XF3 already but little point in discussing them at this point as nothing is finalised. Also nothing too exciting either way.

2.4 is aiming for backwards compatibility so we’re not really looking to make any groundbreaking changes there.

Well, the new editor does seem a very big change, but I guess we'll see what happens with that.

While I'm talking about that by the way, will we get user criteria requirements for BBCode tags? At the moment, I need to use the Editor and BB Code Manager add-on to be able to restrict access to the IMG tag a bit, and it looks like XF 2.3 may be the last version compatible with it as the add-on is now, generally, no longer maintained.
 
Yeah the big caveat to backwards compatibility is clearly the editor but it was important to get that in 2.4 as it’s a worthwhile change rather than waiting for 3.0 and it was mostly complete so it hasn’t taken a tonne of work to get it ready for 2.4.
 
Back
Top Bottom