Considering
New member
What would you say are the major benefits of xenforo over other forum software?
Thanks!
Thanks!

I used both IPS and Xen. Both are very easy to use admin wise. The major difference in my opinion between the two is that Xen has a larger selection of 3rd party add ons. One thing that IPS has that I think is a plus is a page editor. You could create pages very easily on it.
Why do you say that?
I donāt think itās a competition, but their community forum has significantly higher activity the last few days vs XF.
Right now they have a lot of talk going on because of the upcoming release of v5 of the script.I say that because on average that isn't what I observe, not just over the last few days.
You mean codeless? If so, greatPlus finer control over permissions, style settings and settings generally. Whether or not these are major depends on the use case.
XF is one of the easier scripts to "style" in many ways. There are a ton of style properties available that control many aspects of it when compared to IPS (4.3 version I ran, but I doubt it's improved much considering what they did with ability to do custom CSS edits).You mean codeless? If so, great
extra.less
which is a standard template in XF.extra.less
with some slightuse of the style properties options.That's what I've done basically too. Made a copy of the default XF theme (then unchecked it from use), then changed the colors and added backgrounds behind the content to make our own style/theme in a sense, but also using standard XF style, so pretty much 100% of the addons should work with it no issue.XF is one of the easier scripts to "style" in many ways. There are a ton of style properties available that control many aspects of it when compared to IPS (4.3 version I ran, but I doubt it's improved much considering what they did with ability to do custom CSS edits).
You can also tweak a site quite a bit with simple CSS/LESS code inextra.less
which is a standard template in XF.
In fact, the pipe site in my sig is basically a default XF style that has been primarily tweaked viaextra.less
with some slightuse of the style properties options.
Made a copy of the default XF theme (then unchecked it from use),
This.It isn't necessary to make a copy of the default style.
Just style the original one.
I did so for debugging purposes, in a sense. To see if it was something on my customized version of default, or it also affects the default style too.It isn't necessary to make a copy of the default style.
Just style the original one.
Errr... until you need to test something under a default style and don't want to have to go through the trouble of creating it again.It isn't necessary to make a copy of the default style.
Just style the original one.
Default theme just inherits from Master, so you can just create a new Default.Errr... until you need to test something under a default style and don't want to have to go through the trouble of creating it again.
It's simpler leaving the default style untouched and disabled for normal users, create a new style and mess with it. How often have we been asked "does it work under the default style" when pursuing support (either via ticket or from community).
The point is... why?Default theme just inherits from Master, so you can just create a new Default.
Plain Jane shipping XF default
so there is no mistaking that it is a totally unmodified style to test against.You can add it back later.The point is... why?
You can simply KEEP the default one, create a working one and then if you DO need to "test on a default", it's already there but is simply disabled for normal user choice.. you as an admin can still immediately select it to test to see if it is specific to your style you are working on due to add-on interaction or whatever. Saves having to regenerate it time and time again.
In fact, mine is calledPlain Jane shipping XF default
so there is no mistaking that it is a totally unmodified style to test against.
Once more... WHY?You can add it back later.
no need to debug it as it's already a stablised version.
Point was that editing the default doesn't actually break anything, so it's not like it's an issue.The point is... why?
You can simply KEEP the default one, create a working one and then if you DO need to "test on a default", it's already there but is simply disabled for normal user choice.. you as an admin can still immediately select it to test to see if it is specific to your style you are working on due to add-on interaction or whatever. Saves having to regenerate it time and time again.
In fact, mine is calledPlain Jane shipping XF default
so there is no mistaking that it is a totally unmodified style to test against.
Agreed, but neither does simply creating a new one and modifying it and leaving the default alone and unselectable by users. That way if you need to test against a default style it is already there and you can immediately do so.Point was that editing the default doesn't actually break anything, so it's not like it's an issue.
Can 100% guarantee more people are going to edit the base style rather than create a new style.Agreed, but neither does simply creating a new one and modifying it and leaving the default alone and unselectable by users. That way if you need to test against a default style it is already there and you can immediately do so.
Yep.... and frequently they leave it named asCan 100% guarantee more people are going to edit the base style rather than create a new style.
Default
...And thank you for simply re-enforcing that what was mentioned earlier is the better choice to do... creating a different style from any "base" and work off of it.The biggest frustration I had with Xenique was literally undoing peoples edits, and then helping them redo them under a child style.
This is incorrect.when you already have the default base and can easily on the front end (and only once) create a separate/child style off of it
We use essential cookies to make this site work, and optional cookies to enhance your experience.