XF2 support

[CedricV]

lol I didn't start anything. Stop being so sensitive. Forums are for discussion and, yes, for disagreement. Maybe ESPECIALLY for disagreement. The point is to talk and discuss and share viewpoints so an issue or issues can be resolved effectively.

People talk and discuss their grievances and issues they see here because they (including me) care about XenForo. They want to see it succeed. What would be far worse is if this thread was completely dead and nobody cared.

I’m just here to say he has a point.

I’m off again.

 

[smallwheels]

Why on earth after fnally realising that you have been riding a dead horse...

That's more than enough time for me. I would have considered 3 years good. I guess we're arguing over nothing.

... do you still try to ride it again?

Let's look at the release cycle again, shall we?

I don't know that, but technically, you actually don't fully know either

The difference is: You made claims about the need for a LTS (which obviosly should be somehow have a foundation in the current support cycle), I did not.

Forums are for discussion and, yes, for disagreement. Maybe ESPECIALLY for disagreement. The point is to talk and discuss and share viewpoints so an issue or issues can be resolved effectively.

No doubt. But as always this should not be an excuse for posting uninformed silly statements and wrong claims - it lowers the level of the discussion. A good and qualified discussion needs the participants to have done their basic homework before. Saying: "I can post anything I want and claim any false facts - there is nothing wrong about that, it's a discussion, so don't complain, why should I bother to inform myself before leaving strong claims and statements" is not my understanding of a useful discussion in a technical forum.

Apart from that: This is the thread for the upcoming 2.4 and once more I do have my doubts wether the discussion you brought up has anything to do with it or should be considered completely off topic and irritating noise in this thread. Just like the last one you brought up in the very same thread just a couple of posts/pages earlier, following exactly the same pattern: Making wild statements on the basis of having been too lazy to inform yourself by at least reading the thread you are posting to and then call this a "discussion".

 

[Chris D]

Hey my dudes, it’s Saturday. Go and enjoy your day.

For XF usually a new release immediately causes the previous one to be no longer supported and security updates will continue until the next version is out.

In other words, 2.1 was no longer supported after the release of 2.2 and is EOL now 2.3 is released.

However, it is true that we did things slightly different with 1.5 to 2.0. Whether we do something similar again with 2.x to 3.0 is currently undefined, but we will let you know in good time.

 

[Arantor]

Hey my dudes, it’s Saturday. Go and enjoy your day.

This comment here wins the internet for today.

 

[Arnox]

For XF usually a new release immediately causes the previous one to be no longer supported and security updates will continue until the next version is out.

In other words, 2.1 was no longer supported after the release of 2.2 and is EOL now 2.3 is released.

However, it is true that we did things slightly different with 1.5 to 2.0. Whether we do something similar again with 2.x to 3.0 is currently undefined, but we will let you know in good time.

Alright, sounds good. Thank you for clarifying that. <3

 

[smallwheels]

In other words, 2.1 was no longer supported after the release of 2.2 and is EOL now 2.3 is released.

Thanks for the clarification! Saw this in practice today:

Affected version2.2.16
Up until maybe yesterday links to Tweets were appearing fine when posted, but now they are just link.

XF 2.2 is no longer supported so assuming those posts embed here in 2.3, you will just need to upgrade.

In this case the embedding failure is more of a comfort feature than a threat to a forum but still: Though the policy is generally understandable it seems a bit harsh to me to not have any transition period - in this case 2.3 came out in July, so less than six months ago. There are still people that are willing to upgrade to 2.3. but are not able to, be it due to add ons or other reasons. If support is dropped basically the moment a newer XF version is released this is in my eyes not too helpful - the more as .0 versions often enough have issues (as we have seen with 2.3). So basically this policy means:

• If you want support you have to upgrade the day a new version is released
• to be able to do so you better should not have a single 3rd party add on installed (b/c else you might not be able to upgrade)

 

[Chromaniac]

embedding support should be a modular feature imo. requiring a new version update just coz embeds broke on a popular site is kind of a hassle considering it might take a few days for an update to be released and other reasons. anyways, i imagine you have a good reason not to use an addon for embedding functionality. if you don't, it might be worth considering using S9E Media Sites. 2.2 support is still listed though you might need a more recent version of PHP to be able to use latest releases.

 

[Arnox]

Though the policy is generally understandable it seems a bit harsh to me to not have any transition period

After getting on my back about me bringing up support periods, I don't think you have any ground to stand on here, man. And especially since I wasn't even wanting bug fixes like you're asking about, but just security patches.

 

[smallwheels]

embedding support should be a modular feature imo. requiring a new version update just coz embeds broke on a popular site is kind of a hassle considering it might take a few days for an update to be released and other reasons. anyways, i imagine you have a good reason not to use an addon for embedding functionality. if you don't, it might be worth considering using S9E Media Sites. 2.2 support is still listed though you might need a more recent version of PHP to be able to use latest releases.

I quoted a recent support question from another thread of anohter person to illustrate the issue - it is not my case. And yes, I am using S9e Media Sites. So any advice for the problem should probably to the quoted thread, not here.

 

[smallwheels]

I don't think you have any ground to stand on here, man. And especially since I wasn't even wanting bug fixes like you're asking about, but just security patches.

You seem quite aggressive. I am not asking for anything. I was just wondering about the pretty harsh "not our problem mate" attitude where a bit of friendlyness wouldn't have cost a dime. You may not realize it but support is not necessarily updates or bug-fixes - the majority of support work typically consists of anaylsis and helpful hints. Even if there is unwillingness to help the person who asked actively there would have been the option of hinting to the S9e Media Sites add on as a possible alternative to maybe solve the problem. Leaving the customer completely in the dark by refusing even this bit of support is - well - not too helpful.

I'll btw. put you on the ignore list for now.

 

[Arnox]

You seem quite aggressive.

Nah. You're just too sensitive.

I was just wondering about the pretty harsh "not our problem mate" attitude where a bit of friendlyness wouldn't have cost a dime.

What do you want them to do that isn't a patch? If they go to the trouble of analyzing and debugging the code and then telling you what's wrong, then they might as well ship a patch at that point.

Leaving the customer completely in the dark by refusing even this bit of support is - well - not too helpful.

If you want official support, it's best to open a ticket, although sometimes, they'll jump into threads as well to help, depending.

I'll btw. put you on the ignore list for now.

Only the weak add people to the Ignore list. Unless someone is spamming you though. Then it's pretty justified.

 

[Forsaken]

Thanks for the clarification! Saw this in practice today:





In this case the embedding failure is more of a comfort feature than a threat to a forum but still: Though the policy is generally understandable it seems a bit harsh to me to not have any transition period - in this case 2.3 came out in July, so less than six months ago. There are still people that are willing to upgrade to 2.3. but are not able to, be it due to add ons or other reasons. If support is dropped basically the moment a newer XF version is released this is in my eyes not too helpful - the more as .0 versions often enough have issues (as we have seen with 2.3). So basically this policy means:

• If you want support you have to upgrade the day a new version is released
• to be able to do so you better should not have a single 3rd party add on installed (b/c else you might not be able to upgrade)

You can look around the help forums, they still provide support for older versions, just they no longer develop for those versions. LTS would include things other than security updates, like PHP compatibility updates, or bug fixes. Even then, they have in the past made a PHP compatibility patch (or I could be losing my mind because I just woke up after barely sleeping).

People who stay on 1.5, 2.0 or 2.1 generally know that they're on their own, and for bigger communities they are maintaining things themselves to some extent.

 

[smallwheels]

You can look around the help forums, they still provide support for older versions, just they no longer develop for those versions.

That's what was my impression until now as well and why I was wondering about this particular case. The more as it was moved to "resolved bugs" and closed as "not a bug" - while obviously not even having been looked at because it affected 2.2.16. I'd expected it to be either moved to the support forum or to be closed with a tag like "won't fix" if there's no willingness to deal with it.



Not exactly resolved if you ask me.

 

[Arantor]

The reality is, 2.2 is now only supported in the event of a major bug, or a security bug (the two aren't equivalent) - this strikes me as neither.

The question of whether it is genuinely not a bug is a different one: maybe Melon broke the embedding functionality from his side, maybe the topic opener's forum got blacklisted by X's servers, maybe there was a connection failure. Maybe they're based in Brazil where there's an ongoing dispute between the government and X.

Many of these would legitimately qualify as 'not going to be resolved by XF'.

It is, unfortunately, not that simple.

 

[smallwheels]

The reality is, 2.2 is now only supported in the event of a major bug, or a security bug (the two aren't equivalent) - this strikes me as neither.

The question of whether it is genuinely not a bug is a different one: maybe Melon broke the embedding functionality from his side, maybe the topic opener's forum got blacklisted by X's servers, maybe there was a connection failure. Maybe they're based in Brazil where there's an ongoing dispute between the government and X.

Many of these would legitimately qualify as 'not going to be resolved by XF'.

It is, unfortunately, not that simple.

Absolutely. And exactly that is why I don't get the answer "update or leave me alone" and then closing it als "solved" - b/c there is a myriad of possible reasons (including twitter/x making funny tings). As said before: Understandable to a degree if this is considered a minor comfort issue that XF does not want so solve - however: Giving the customer a more constructive hint than "update" (w/o even asking what may hold him back) would no doubt be a nice gesture.

 

[Arantor]

But this is exactly the sort of reason why Paul gets the criticism he gets. It doesn't feel like it's about solving the customer's problem - even if the answer really is (and it sometimes is) 'just upgrade'.

I get why he'd take the stance he did. In another life I'd probably have done something similar, but I came out the other side realising that this wasn't the best way to go about solving the problem.

There is the implicit 'assuming it is...' which is I suppose an invitation to refute it with evidence that might see it get reopened.

 

[Arnox]

But this is exactly the sort of reason why Paul gets the criticism he gets. It doesn't feel like it's about solving the customer's problem - even if the answer really is (and it sometimes is) 'just upgrade'.

I get why he'd take the stance he did. In another life I'd probably have done something similar, but I came out the other side realising that this wasn't the best way to go about solving the problem.

There is the implicit 'assuming it is...' which is I suppose an invitation to refute it with evidence that might see it get reopened.

Again though, smallwheels hasn't opened a ticket yet about this to my knowledge. He'd probably get a more helpful response at least going that route.

 

[Suzanne O]

That's what was my impression until now as well and why I was wondering about this particular case. The more as it was moved to "resolved bugs" and closed as "not a bug" - while obviously not even having been looked at because it affected 2.2.16. I'd expected it to be either moved to the support forum or to be closed with a tag like "won't fix" if there's no willingness to deal with it.

View attachment 315254

Not exactly resolved if you ask me.

Why complain all the time about social media sites that suck anyway?

 

[Suzanne O]

Absolutely. And exactly that is why I don't get the answer "update or leave me alone" and then closing it als "solved" - b/c there is a myriad of possible reasons (including twitter/x making funny tings). As said before: Understandable to a degree if this is considered a minor comfort issue that XF does not want so solve - however: Giving the customer a more constructive hint than "update" (w/o even asking what may hold him back) would no doubt be a nice gesture.

He probably thinks you're a troll. If you actually put your mind to things and find out why things don't work you should be going through the right way.
hit this button https://xenforo.com/customers/support/ and get a ticketed response there.

 

[Arantor]

I don't know why he would file a ticket, it wasn't his topic. But it looks like it was a blip that has solved itself, so all's well that end's well.