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

Did not read the whole 25 🤪pages , but i hope a few changes slide into the std version of 2.4;
  • Grid style variations to choose one you like
  • Style variation moved to top navbar
  • Banner in post and resource option
  • Add-on update checker (on the list :P)
  • Websockets for realtime content
  • Choose own node icons
Just a thought for bringing more options to XF instead of a forest add-ons.
 
Doubtful websockets will ever become core because running it on the hosting environments XF tends to support is hard. PHP doesn’t do websockets well which means you’re immediately talking about a bigger server that can also run something else (probably Node), and the support that goes with it is at least on par with ElasticSearch from XF’s point of view.
 
Doubtful websockets will ever become core because running it on the hosting environments XF tends to support is hard. PHP doesn’t do websockets well which means you’re immediately talking about a bigger server that can also run something else (probably Node), and the support that goes with it is at least on par with ElasticSearch from XF’s point of view.
Nah... move yours to xfcloud mate. You won't know yourself once you've done it.
You will be less grouchy about it all.
 
Nah... move yours to xfcloud mate. You won't know yourself once you've done it.
You will be less grouchy about it all.
Pretty sure cloud doesn’t have websockets. And no, I’d rather not, thanks. I run servers just fine (I’m a developer, I’ve been running forums on my own web servers before XF existed) and am perfectly happy to keep doing that.

I don’t need websockets, either, but I can see why some might - but it’s a niche feature that isn’t going to play nicely on a lot of hosting. Even XFcloud will need special setup for it.
 
So, about 2.4 ...

This is not the thread for an existential discussion on XF and the future of forums.

It's about the 2.4 release.

Feel free to start a new thread if you want to discuss that in any (more) depth.

Can we please get back to talking about the 2.4 release.
YES!

My 2.4 wishlist (same as 2.3 wishlist)
Oh and anything that makes @Bob happy makes me happy:)
 
2.4 is aiming for backwards compatibility so we’re not really looking to make any groundbreaking changes there.
If time allows, may I suggest a hashing/salting helper, be it in 2.4 or 3.0?

I like how the IP address on a forum (I don't know if I can name it, but a big board), displays the IP address in a hashed manner for registered and posted content.

For forums dealing with member-to-member transactions, a helper in helper_ip to conceal the IP in a hashed manner to certain user groups (registered, and {$ip|ip} to mod/admins) could make someone feel more comfortable dealing with someone if they know that the account is legitimate (to an extent). Something similar to {$ip|md5} (but not using md5 because there could be a database of all IPs hashed that way, but anything that can securely make a unique hashed IP; SHA1 perhaps, I don't know).

It could help people determine duplicate accounts without having admins investigate, giving some peace of mind.

An add on would probably be best to store it as a cache, but I don't think there'd be much performance issues on smaller boards using a template edit.

This would likely have to be in its own suggestion thread, but it alone isn't groundbreaking over having 10+ different helpers that can do various things which would typically require an add on to do with (more) variables accessible. I would assume more people would need to think of use cases like this and compile a list of helpers that might reduce the reliance of add ons to simple template edits.

Further, @Paul B already supplied us with a pretty exhaustive list that can be used, so I don't suspect many more need to be added.
 
@Chris mentioned that 2.4 would be a "QoL" update for members (including administrators and moderators) and while there has been some negativity posted about the two features mentioned so far (not specifically here, but in the usual places by the usual people), it's worth pointing out that these were fairly high up on the suggestion list.

1733414881324.webp

Yes, there are suggestions (much larger features) which have more votes, but of the ones revealed for 2.4 so far, one of them was just outside the top 10 and the other two were within the first 2-3 pages.

There is more to come though.
Who knows, it may even silence (some of) the critics for a short while*.




* It won't.
 
Here's hoping that there is a blocking feature implemented.
Adding trolls to your ignore list means you can't see their nasty comments but they can see theirs and my comments.
 
  • Haha
Reactions: AWS
@Chris mentioned that 2.4 would be a "QoL" update for members (including administrators and moderators) and while there has been some negativity posted about the two features mentioned so far (not specifically here, but in the usual places by the usual people), it's worth pointing out that these were fairly high up on the suggestion list.

View attachment 315082

Yes, there are suggestions (much larger features) which have more votes, but of the ones revealed for 2.4 so far, one of them was just outside the top 10 and the other two were within the first 2-3 pages.

There is more to come though.
Who knows, it may even silence (some of) the critics for a short while*.




* It won't.

The only thing that would make me pause about 2.4 is the new editor. Not that it's a bad idea at all. It's potentially pretty awesome. But... It's also potentially a very breaking change for what is a QoL (which I definitely like and am a fan of, by the way) update. It is true that people who need to use the old editor for add-on and/or template compatibility can just stick to 2.3, but that is also not ideal as the current editor has a few small issues such as how it handles quotes in WYSIWYG mode and also small issues at times parsing things such as content in spoilers.
 
Most annoying thing on current editor is if you try to make a bulleted list in Mobile it pushes the selections out of the way and you have to disable keyboard to see them.
 
So you want but don't want the new editor and want but don't want the current one at the same time. A bit of a unlucky situation: No matter what XF does: it is impossible to make you happy.

No it's not. XD There's lots of things they can do. That is, assuming they're not already doing one of them. Perhaps the new editor will be so good, it won't need any add-ons (at least for me personally anyway). Maybe they could ship a quick patch out for the 2.3 editor alongside 2.4. I dunno. We'll just have to wait and see.
 
No it's not. XD There's lots of things they can do. That is, assuming they're not already doing one of them. Perhaps the new editor will be so good, it won't need any add-ons (at least for me personally anyway). Maybe they could ship a quick patch out for the 2.3 editor alongside 2.4. I dunno. We'll just have to wait and see.
If they were able to patch the fixes they would have by now, the issues are in the core of the editor which XF does not control.
 
If they were able to patch the fixes they would have by now, the issues are in the core of the editor which XF does not control.

According to the "Have you seen... " article on 2.2's new editor, they were still using the Froala libraries which would be the same libraries that the quite stable XF 2.1 editor uses. This would heavily suggest, then, that the bugs are on XF. Unless I'm much mistaken. Maybe the Froala devs introduced some bugs to the libraries over time?
 
According to the "Have you seen... " article on 2.2's new editor, they were still using the Froala libraries which would be the same libraries that the quite stable XF 2.1 editor uses. This would heavily suggest, then, that the bugs are on XF. Unless I'm much mistaken. Maybe the Froala devs introduced some bugs to the libraries over time?
Bugs have krept up that Froala aren't taking the time to fix, again XF does not control the core code of the editor.
 
Back
Top Bottom