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

[Suzanne O]

Just to clarify as I've never had someone in two different groups with different values of the same permission.

In this example, I'd have them in Group A or Group B, but not both:

Are you saying that if Group A has an editing time limit of 10 minutes and Group B has one of 20 minutes, and a member is in both, is it cumulative as in a total of 30 minutes,

Or, what I thought due to "never", does the greater of the two apply (Group B with 20 minutes)?

Cumulative - increasing or increased in quantity, degree, or force by successive additions.

I've seen super admins carry both moderator and admin roles before.

 

[Mendalla]

Cumulative - increasing or increased in quantity, degree, or force by successive additions.

@ENF is right. When we talk about permissions being cumulative, it means that the user gets the most permissive of all the permissions from all the groups they are in. So if one group has a "No" for "Edit Own Thread" and another has "Yes" and a user is in both, they get "Yes". You can block that by using "Never" when there are cases where a certain group should never be able to do something in a given node. Where things like the timeout are concerned, then. most permissive means the most generous value, so "30 min" trumps "20 min".

I am used to the somewhat similar permissions used in Microsoft Windows Access Control Lists so it was fairly easy for me to understand and pick up but I know it is not totally intuitive.

 

[frm]

Thanks for the clarification, @ENF and @Mendalla. I've always been super careful after all these years to remove someone from Group A to put them in Group B when I could've just ticked Group B and forgotten about it. Though, I've only ever had but 10 user groups, so it wasn't an issue. I only asked because I'm making "signature level" user groups and I didn't want the last group to have 50 lines or something as the cumulative phrasing threw me off. Now I know I can just tick Level 1, Level 2, then Level 3 and know for certain they'll only inherit the maximum of 5 lines (as opposed to 1+3+5...).

Now that's out of the way, where's that XF 2.4 HYS I saw spoken of this weekend..

 

[bzcomputers]

I would really like to see the suggestions forum cleaned up - there are over 1,000 suggestions which is an absurd number.
Since most of them are not going to be implemented it will be great if XF staff can weed them down to those they think that are relevant.
The same for the bug reports forums, which have 649 bugs active.

Weed them down to those they think that are relevant? The whole purpose of the suggestions and voting to find out what is relevant to the customer. XenForo already knows what they want.

I think putting more emphasis on implementing popular suggestions and actually fixing bugs at a quicker pace is needed. I think XenForo had intentions of this, but for one reason or another it still hasn't come to fruition yet.

In both cases I assume that many are already implemented/fixed/not relevant, so the housekeeping is needed.

Not true at all. There are very few open suggestions and bug fixes that are implemented or fixed - as for relevant that is completely subjective.

 

[Suzanne O]

Looking forward to this coming out.

 

[WoodiE]

Looking forward to this coming out.

Sometime Soon™

 

[MentaL]

Looking forward to this coming out.

Hope not too soon. There is a lot of catch up from 2.3.

 

[bzcomputers]

Hope not too soon. There is a lot of catch up from 2.3.

2.4 is not suppose to have 3rd party add-on breaking changes like 2.3 had. So there shouldn't be any needed add-on updates over those required for 2.3 ...or at least that was the original intention of putting out 2.4 before they rolled out 3.0.

3.0 is expected to have additional breaking changers and they didn't want to compound the problems of releasing 2.3 and then 3.0 one right after the other, so 2.4 is giving add-on developers a little break while still improving on the code.

 

[Suzanne O]

Hope not too soon. There is a lot of catch up from 2.3.

Hope it is soon actually. From what i read in the announcements section @Chris D said it was going to be soon. It's just an editor change from what we have now to what it's going to be (tiptap)

2.4 is not suppose to have 3rd party add-on breaking changes like 2.3 had. So there shouldn't be any needed add-on updates over those required for 2.3 ...or at least that was the original intention of putting out 2.4 before they rolled out 3.0.

3.0 is expected to have additional breaking changers and they didn't want to compound the problems of releasing 2.3 and then 3.0 one right after the other, so 2.4 is giving add-on developers a little break while still improving on the code.

Plus what you said.

 

[MentaL]

2.4 is not suppose to have 3rd party add-on breaking changes like 2.3 had. So there shouldn't be any needed add-on updates over those required for 2.3 ...or at least that was the original intention of putting out 2.4 before they rolled out 3.0.

3.0 is expected to have additional breaking changers and they didn't want to compound the problems of releasing 2.3 and then 3.0 one right after the other, so 2.4 is giving add-on developers a little break while still improving on the code.

Unless @Xon decides he's done, I have faith 3.0 will he a success. But, I would give it at least six months before upgrading.

 

[javakhir]

already massive bugs fixed, the next one will be XF 2.3.4

 

[Kirby]

So there shouldn't be any needed add-on updates over those required for 2.3

Add-ons that directly touch editor (JavasScrript) code will most certainly require updates for 2.4 (or become useless like https://xenforo.com/community/resources/editor-multiple-dragndrop.7921/), others may require updates if for example template modifications break.

 

[Ferdinand]

Is it possible to create an add-on-importer & converter? Our site relies on a few 3rd party add ons for full functionality. There are a couple of integrations I would love to be able to keep on using XF.

FYI, while writing this an error with the shadows has appeared:

 

[bzcomputers]

Add-ons that directly touch editor (JavasScrript) code will most certainly require updates for 2.4 (or become useless like https://xenforo.com/community/resources/editor-multiple-dragndrop.7921/), others may require updates if for example template modifications break.

Thanks for the reminder. Forgot the editor swap was moved up to the 2.4 release.

I guess the "focusing on backward compatibility" didn't pan out for the XenForo team on this one. As this was a major point they expressed as they have attempted to move into more frequent software updates. Anyways, the number of add-ons affected by 2.4 will be significantly less than 2.3.

As for template modifications, those will always be a roll of the dice on any release.

 

[Forsaken]

Thanks for the reminder. Forgot the editor swap was moved up to the 2.4 release.

I guess the "focusing on backward compatibility" didn't pan out for the XenForo team on this one. As this was a major point they expressed as they have attempted to move into more frequent software updates. Anyways, the number of add-ons affected by 2.4 will be significantly less than 2.3.

As for template modifications, those will always be a roll of the dice on any release.

Backwards compatibility means the majority of things will not break, not that nothing will break.

 

[Chris D]

Certainly “focusing on” or “aiming for” as we might have said elsewhere wasn’t a promise that there would be no breaking changes.

Not least stuff regarding the editor. It should go without saying that completely replacing the editor would likely not maintain backwards compatibility.

But focusing on / aiming for backwards compatibility where possible is still very much in our minds.

 

[Forsaken]

Certainly “focusing on” or “aiming for” as we might have said elsewhere wasn’t a promise that there would be no breaking changes.

Not least stuff regarding the editor. It should go without saying that completely replacing the editor would likely not maintain backwards compatibility.

But focusing on / aiming for backwards compatibility where possible is still very much in our minds.

Waiting for the 3.0 announcement where you remove hooks, and spin it as a good thing.

 

[Sim]

Waiting for the 3.0 announcement where you remove hooks, and spin it as a good thing.

v4.0 is traditionally where software companies start removing functionality - as a "feature"

 

[Forsaken]

v4.0 is traditionally where software companies start removing functionality - as a "feature"

We do need to account for XF slower dev cycles though.

 

[Chris D]

After a long time soul searching we have decided to remove posting from 2.4. Nothing good can ever come of it.