Invision community Vs Xenforo

Someday I will buy Invision, I hope. I like the badge, article, and blog.
Page builder too.
 
Last edited:
I thought the good old days were 1.x when it was still free? I remember tons of people complaining that 2.x was paid commercial software.
I prefer 2.x. There was a large number of addons and free styles that weren't around during 1.x. But if I could I'd also probably use 1.x and build from there if I had the files.
 
Someday I will buy Invision, I hope. I like the badge, article, and blog.

I am in a confusion for days about buying between one of them, especially for the same features, including the default UI/UX. It would be great if the two of them join together ;)
 
Last edited:
Page builder too.
pages is what interests me.
my site was originally on invision when owned by the first owner.
he used pages for a lot of stuff that you have to buy extra add ons to do.
he did say that his was not as nice as the add ons but that someone familiar with working with databases and the invision templating could probably do a better job.
 
Invision Community 5 removed the ability to make most custom plugins that extend the base plugins (core, forums, cms, commerce, etc).

Matt - IPS Management said:
[Post] Correct, there is less opportunity to overload/hook into/touch Invision Community 5. If you can give me some examples of why you'd want to overload those methods, we can help guide you to newer tools or understand why there is a need and consider adjustments to the dev toolkit.

Monkey patching (code hooks) were convenient but the cost was very high in that we couldn't significantly alter our code without destroying most existing modifications causing WSOD, ISE500 or other errors on client communities.

We also want to be a little more protective of some of our UI and flows. We want to build a toolkit that lets you build amazing add-ons and extra functionality but it will mean there is less scope for smaller apps that change some of our existing functionality.

This effectively kills custom plugin development; it's not dissimilar to what IB did with the transition from vBulletin 4 to 5.

If XF 2 had feature parity with IPS 5, priced slightly lower than them, and keep perpetual licenses they would kill IPS.

Replicating those IPS plugins and building importers for them is a huge undertaking for a small team like XF's, though.

Also, I believe (someone correct me if I'm wrong) that IPS 5 licenses are only good for 24 months, and are then revoked if not renewed?
 
Last edited:
I think next XF 2.4 update will change your mind & make you smile!
Compare bug fixes & updates, easy to understand which team is the best!
Real hard workers are here, no matter what they say. By the time invision 5 stables, XF 3 will come out! That will be 2 steps ahead!

From personal experience: I bought an exsiting 17 years old forum for $50k on 2020
made 2 new domains, XF & IP
imported VB4 backup to both, hard worked & made paid memberships on both
after 1 year
XF brought me $60k (because users were using VB 4)
Invision brought me $2k (very hard to use for users)
after comparing both in real test, I deleted invision, because it can't even recover hosting.

bought another XF license & started the second fresh forum

after upgrade to 2.3, doubled my revenue, indexing goes very well, organic search traffic is perfect.
 
Last edited:
Invision Community 5 removed the ability to make most custom plugins that extend the base plugins (core, forums, cms, commerce, etc).
Totally wrong. They are doing away with hooks. They are changing the way mods work. They are working with the mod developers to make an easy transition. I have v5 beta installed on a test site. I also have a beta of 2 add ons installed. There are plenty of v5 beta plugins already available.

I have converted one of my sites to IPB 4 with the idea to upgrade as soon as RC 1 hits.

One should speak only when they know all the facts.
 
Screenshot.webp
 
Totally wrong. They are doing away with hooks. They are changing the way mods work. They are working with the mod developers to make an easy transition. I have v5 beta installed on a test site. I also have a beta of 2 add ons installed. There are plenty of v5 beta plugins already available.

I have converted one of my sites to IPB 4 with the idea to upgrade as soon as RC 1 hits.

One should speak only when they know all the facts.
He's not completely wrong, even if he was a bit hyperbolic. The changes will create a lot of limitations for what developers can and cannot do.

Matts talking points are the same as other services that have changed from on-premise to a cloud hosting focus 🤷‍♂️. Spin it as "better optimization, better performance" at the cost of ability to customize and extend the software itself.
 
Since I have hands on experience with v5 I can say the only thing that has changed as far as addons is they removed the hooks. So you have to use the application layer which most people did start to do when v5 was first talked about.

Matt and his team have been very straight forward with the developers, some that make a living off creating apps for IPB, telling them how the new sytem works. They have been very active in the beta discussions. There are already beta apps available.

Wouldn't it be nice if all forum software makers communicated with add on developers explaining what will change in the next major version?
 
Since I have hands on experience with v5 I can say the only thing that has changed as far as addons is they removed the hooks. So you have to use the application layer which most people did start to do when v5 was first talked about.

Matt and his team have been very straight forward with the developers, some that make a living off creating apps for IPB, telling them how the new sytem works. They have been very active in the beta discussions. There are already beta apps available.

Wouldn't it be nice if all forum software makers communicated with add on developers explaining what will change in the next major version?


You're apparently bitter from 2022-2023, so take your strawman argument elsewhere.
 
@Forsaken I am chatting with IPS devs who are unable to make v5 plugins (applications in v5) due to the removal of hooks. It has come to the point where the only solution to some problems is changing core files. That is something I thought we left behind over a decade ago.
 
@Forsaken I am chatting with IPS devs who are unable to make v5 plugins (applications in v5) due to the removal of hooks. It has come to the point where the only solution to some problems is changing core files. That is something I thought we left behind over a decade ago.
Also hearing from some developers I worked with when I still bothered with Invision, and none of them are that happy.
 
sounds familiar like vb5, isnt that what they did too that partly killed them, getting rid of hooks? i remember the same rhetoric like it will be fine, but we still didnt see the same custom and 3rd party supports....what a waste all that was but xf still wasnt ready to me back then.....it is unsetting to think it could happen again anywhere, even here things could slide off the edge, like they partway did with 2.3 taking so long but i dont see IPB doing that really.....from my perspective IPB is like a simple platform version, i dont really like the sites ive seen built with it, dont envy them etc.....

maybe that makes sense for them tho, simplify and simplify...i dont want XF to do that tho for sure ;P
 
You're apparently bitter from 2022-2023, so take your strawman argument elsewhere.
Not bitter about anything. I know how it works here. I wait. I also look at other options. When I find one I take action. Unlike many here I have no loyalty to xenforo or any other software product. My loyalty lies to my country and family.
 
Matts talking points are the same as other services that have changed from on-premise to a cloud hosting focus 🤷‍♂️. Spin it as "better optimization, better performance" at the cost of ability to customize and extend the software itself.
Agreed. Its going to be interesting to see how XF navigated this, as XF actively offers cloud too.
 
Back
Top Bottom