💬 Platform Discussion XenForo 2.3 preview

[Arantor]

You could have said nothing and it wouldn't have changed the point of anything I'd said. We've all heard it all before, nothing has changed.

 

[Tyrsson]

They're all like that. The bigger they are the worse they are

Github GraphQL.... Need I say more?

 

[Tracy]

You could have said nothing and it wouldn't have changed the point of anything I'd said. We've all heard it all before, nothing has changed.

Of course, we all know you are the final say in all things reasonable with scripts and the final say in what words mean.

 

[Arantor]

Finally you’ve recognised my rightful place in the universe. My work here is done!

 

[Arantor]

Github GraphQL.... Need I say more?

GraphQL is usually a way to introduce a lot of complexity for little benefit to the maintainer, just for apparent convenience for the consumers who inevitably misuse the endpoints like REST anyway.

 

[joelr]

Grass is always greener. You're getting quite worked up. If you want to switch switch.

No no, you can keep him.

Github GraphQL.... Need I say more?

Just curious, can you explain for the non technical people?

 

[Arantor]

No no, you can keep him.


Just curious, can you explain for the non technical people?

GraphQL is a way of letting the client specify what data it wants from an API.

In a forum context, let’s say I have an endpoint that provides topics. In GraphQL I could just say “give me the list of topic titles in a board”, or reframe it to “give me the list of topics in a board plus the first post, plus the details of the topic starter”.

This seems very flexible and notionally cuts down the amount of data over the network, but in practice produces a lot of headaches for the API designer, not least performance, because they can’t entirely predict what a client will ask for.

Worse, though, practically everyone treats GraphQL like it’s a REST endpoint: you get what you get and that’s that, and if you need extra info that’s another round trip (rather than expanding the one request to get extra data), meaning that for a lot of uses, it’s the worst possible outcome for everyone.

 

[Tracy]

No no, you can keep him.

Don't worry... for the Astro site it would never happen because IPS doesn't offer what I require for extending it, and even Pages doubtfully has that ability.
Now, for the other sites.... yep, I could easily get Pages to work for them as it's not as complicated.
And as I said, I honestly don't know if I want to waste money on scripts for domains that are just of marginal interest right now and were more "playgrounds" to get exposure to stuff.

 

[Empire]

How many people moved over from other forum software

 

[Cedric]

Seems that 2.3 beta is out.
Announcement:

XenForo & Add-ons 2.3.0 Beta 1 Released (Unsupported)

We are delighted to announce that XenForo 2.3.0 Beta 1 is now available to all customers with active self-hosted licenses. XenForo 2.3 includes a large number of new features and improvements, including: Dark mode and style variants Extensive performance improvements Featured content Image...

xenforo.com

 

[Tracy]

Seems that 2.3 beta is out.

As many bugs as they have, I'd be hesitant of running on a live site. Might be OK to play with on a development site.
Didn't someone make a post over there about the gigantic increase in the outstanding bug reports numbers recently?
(as I go check again).... well, looks like that thread got moderated and posts calling stuff like that out appears to have been removed.
But 22 pages of listed bug reports (with maybe 2 pages worth having 3rd party or cannot reproduce comments and that only dealing with the core and not importers or 1st party add-ons) dating back to 2019 is quite a few open bug reports.

 

[Cedric]

As many bugs as they have, I'd be hesitant of running on a live site. Might be OK to play with on a development site.
Didn't someone make a post over there about the gigantic increase in the outstanding bug reports numbers recently?
(as I go check again).... well, looks like that thread got moderated and posts calling stuff like that out appears to have been removed.
But 22 pages of listed bug reports (with maybe 2 pages worth having 3rd party or cannot reproduce comments and that only dealing with the core and not importers or 1st party add-ons) dating back to 2019 is quite a few open bug reports.

What's obvious is that some fanboys will not see the problem there, lol.

 

[Tracy]

What's obvious is that some fanboys will not see the problem there, lol.

Nope... they will simply be overly aroused by seeing 2.3 of some flavor being released. It's been so long since they released a "major" release that used a BETA (4 years approximately) I'm sure the fanbois are slavering.
Also, just checked and there roughly 80 more open bug reports (as reported in the appropriate location) on XFMG, XFRM and XFES. I won't even go into the open suggestion numbers for the script and 1st party add-ons. Other bugs get commented on in some of the normal discussion threads but never moved over into the bug report area by staff or a new bug report entered in the appropriate area.
So roughly... around 500 open bug reports dealing with their script and 1st party add-ons. Granted, all those may not be valid bugs.. but they are OPEN bug reports.

 

[Joeychgo]

So it is "Direct messages" now or "conversations"?

 

[Tracy]

The answer is... yes



But honestly, I can see it referenced as both from a grammatically correct point of view. They are conversations that contain direct messages. But it would be rather confusing for many. Settling on one thing would be best.
But it is similar to how a conversation between people contain vocalizations (direct messages) from each one.

 

[joelr]

As many bugs as they have, I'd be hesitant of running on a live site. Might be OK to play with on a development site.
Didn't someone make a post over there about the gigantic increase in the outstanding bug reports numbers recently?
(as I go check again).... well, looks like that thread got moderated and posts calling stuff like that out appears to have been removed.
But 22 pages of listed bug reports (with maybe 2 pages worth having 3rd party or cannot reproduce comments and that only dealing with the core and not importers or 1st party add-ons) dating back to 2019 is quite a few open bug reports.

Just curious, what was the release like for 2.2 or 2.1?

IPS was very rough with their releases in the early days (I distinctly remember releases like 4.0.19.4!), but it definitely got better as the product line hit 4.2 and 4.3.

 

[cpvr]

Seems that 2.3 beta is out.
Announcement:

XenForo & Add-ons 2.3.0 Beta 1 Released (Unsupported)

We are delighted to announce that XenForo 2.3.0 Beta 1 is now available to all customers with active self-hosted licenses. XenForo 2.3 includes a large number of new features and improvements, including: Dark mode and style variants Extensive performance improvements Featured content Image...

xenforo.com

I’ll be waiting till beta is over with to upgrade.

 

[Tracy]

I’ll be waiting till beta is over with to upgrade.

I'll be waiting until the BETA is over, and then the first release bug-squashing period is done and they release 1 or two more point releases.
With as few playing with the BETA as there are and then consider they have as many open bug reports as they still do (some going back to 2019) I prefer waiting so that the wider release will show the additional bugs because everyone has to have the latest/greatest immediately before I will be moving over to it.

 

[Tracy]

Just curious, what was the release like for 2.2 or 2.1?

IPS was very rough with their releases in the early days (I distinctly remember releases like 4.0.19.4!), but it definitely got better as the product line hit 4.2 and 4.3.

It wasn't bad.... the problem currently is they sat spinning on their thumbs spinning around for so long that a lot of 2.2 related bugs built up, then they've made changes in 2.3 that caused additional bugs (as well as apparently not addressing older bugs) so it's all catching up in one massive wave.
I guess that is what happens when you wait 2+ years to release a x.Y.z release because you were busy doing.... something?
They never got to the w.x.y.z level... but that's because they'd simply release a x.y.z release instead of using an additional point release.
Folks used to have a lot more faith in them... now the main ones that do are their cult members. But you have those with every script... they won't recognize when their is an issue because their cult leaders can do no wrong.
Hell, just look over at XF in the XFMG thread about how the gallery mirroring counts mirrored content against a users XFMG quota. I agree with several that it's not a bug in the way it works... just a piss poor design choice. But you have the cult members still trying to explain that issue away.
Of course, the mirroring in XF is a low-end implementation. Just to give enough so they can say they do it... but ignore other aspects of it that would actually make it beneficial, referring you to outside developers to do that even though it would be easier to code in the main script.

 

[Cedric]

Agreed. The increasing amount of bugs isn’t a good sign, I’ve installed the beta on a test forum and as I said before, I’m not really a fan of it considering the amount of time they had. I expected more but those fanboys on the support forum cheer all the way, and that’s the problem. Devs think they’re doing good while in reality they lack so much. There’s little to nothing with a focus on brining content. Where as Invision Community just left XF in the dark.