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

What is this about not supporting Markdown? No, the limited markdown support in XenForo should be expanded to support both full BBCode and full Markdown, resolving conflicts wherever necessary automagically. Easier said than done, but that would be my feature request.
There is a magical suggestions forum. lol.
 
Markdown support isn’t going anywhere and I don’t believe anyone has said anything to the contrary.
Just out of curiosity, has there even been some talks about a XenForo app? If yes, would you guys ever consider this to make a reality?
 
Thanks for letting us know, team! (y)

Are any other community software devs using TipTap in their products already? I'm curious if XF (meaning all of us) will be walking the bleeding edge or a well trodden path.
 
It's not ready
No ****, that's why I asked what's the hold up? Just a few months ago it was going to be the next release prior to Jan. Now it's delayed, hence the question. What I'm hearing is that the majority of dev's cannot work on 3.0 with new styling, so XF are doing a 2.4 so that those dev's have something to do.
 
No ****, that's why I asked what's the hold up? Just a few months ago it was going to be the next release prior to Jan. Now it's delayed, hence the question. What I'm hearing is that the majority of dev's cannot work on 3.0 with new styling, so XF are doing a 2.4 so that those dev's have something to do.
It makes more sense to replace the editor (as the current one is problematic) prior to the style update, as they can both bring a large number of issues separate from one another.

They have also changed their release structure (which @Jeremy P also slightly covers), and the previous ETA for 3.0 was before or shortly after 2.3's release. I would assume that they made more headway into the editor, giving them a chance to release it sooner and also start delivering on the promise of smaller and faster updates.

2.4 coming out likely won't delay 3.0 much, and even if it does it's better for a major style update to be delayed than to be pushed out quickly with a lot of bugs 🤷‍♂️.
 
it's better for a major style update to be delayed than to be pushed out quickly with a lot of bugs 🤷‍♂️.
Each version brings its share of bugs, this seems quite understandable, the problem is that they are added to those noted in previous versions... Bugs noted in 2.3 have not been resolved in 2.3.1, 2.3.2 or even 2.3.3... This is terribly frustrating. Quite honestly I would like an XF 2.4 "Bug Fix" version, which would resolve the vast majority of bugs and which does not add any other functionality, the new versions cycle would start again on a healthy basis.

Time stamps that don't work properly, alerts that disappear, windows that open in the background of lightboxes, and more should be resolved promptly before adding anything else.
 
Quite honestly I would like an XF 2.4 "Bug Fix" version, which would resolve the vast majority of bugs and which does not add any other functionality, the new versions cycle would start again on a healthy basis.
But if all they are doing is bug fixes, those can be done in 2.3.x releases. You don't generally increment the middle number for bug fix releases. A second decimal release us for new features, which is the editor. They could actually keep doing 2.3.x releases for bug fixes alongside development of 2.4 rather than holding the bug fixes for 2.4 as Chris clearly says they are doing.
 
I can't deny that each new release fixes many bugs, most likely many more than it creates. I'm going to speak without really knowing what's going on in the background and certainly with a lot of naivety but I thought you could say: "stop! we have several dozen bugs to resolve, let's put all our resources on that and implement pause the rest." It's true that currently no bug completely breaks XenForo even if some penalize the user experience, but as a customer and user it is really frustrating to see bugs cross several versions without being resolved.
 
But if all they are doing is bug fixes, those can be done in 2.3.x releases. You don't generally increment the middle number for bug fix releases. A second decimal release us for new features, which is the editor. They could actually keep doing 2.3.x releases for bug fixes alongside development of 2.4 rather than holding the bug fixes for 2.4.
These are unimportant technical details on the subject... They could call it XF 3,14159265358979 that would be just as good.
 
These are unimportant technical details on the subject... They could call it XF 3,14159265358979 that would be just as good.
But it matters for those in the development process, even if it doesn't for us on the outside. Having a defined syntax actually makes the numbers meaningful rather than slapping a nonsense marketing name on like, oh, "XP" or "Vista" (hi, Microsoft ;)). The bottom line is that the announcement of 2.4 being the release of the new editor in no way stops them from doing patch releases for the bugs in 2.3.
 
We’re keeping it but, no, it won’t retain the functionality of the toolbar.

Ultimately I would be surprised if people even need to use BB code mode anymore.

What do you feel the use case for keeping it is?
There are times I need to edit the raw code to remove an image tag or url. Not often, but, there are times.
 
We’re keeping it but, no, it won’t retain the functionality of the toolbar.

Ultimately I would be surprised if people even need to use BB code mode anymore.

What do you feel the use case for keeping it is?
Can we just retire BBCode someday, or make it an option so if people really want it, they can enable it? To me, BBCode feels like we are trying to hold on to the glory of MySpace. Seems like a lot of code that wouldn't need to be maintained anymore as a bonus. :)
 
Can we just retire BBCode someday, or make it an option so if people really want it, they can enable it? To me, BBCode feels like we are trying to hold on to the glory of MySpace. Seems like a lot of code that wouldn't need to be maintained anymore as a bonus. :)
What is "MySpace"?
 
Back
Top Bottom