Are clashes between Addons/Plugins less likely with Xenforo ?

Not open for further replies.

Digital Doctor

Well-known member
the old VB mod clashes .... I don't miss at all ... install a mod by itself, it works, add some other specific mod, now both don't work, or only one works....
Question: Is there any fundamental design reasons why Xenforo will have less Mod clashes than vB ?
Yep... the way in which the core of the product integrates with a mod. Vastly different systems... VB doesn't keep mods separate, XF does.
Does anyone know more details about how Xenforo's core is better designed to keep prevent Addons / Plugins from clashing ?


XenForo developer
Staff member
I believe the Zend Framework has a lot to do with it, and the shift to pretty much completely OOP coding.
We actually use very little of the Zend Framework - the vast majority of the code that runs XenForo is bespoke. The plugin system in particular is entirely unique to XenForo.

To answer the question though, yes, collisions are far less likely and better handled by XenForo than by the vBulletin plugin system due to the fact that XenForo's plugin system has strict control over the data exposed to each callback function, whereas vBulletin's hooks for the most part exist in global scope, allowing them to modify just about anything at will. While the approach we took when we wrote vBulletin's hook/plugin system allows for great flexibility, it has the caveat that it's virtually impossible to avoid collisions, or to ensure backward compatibility through newer versions. Hence why we did it differently for XenForo.


Well-known member
Simply put, Better architecture. :)

Kier and Mike have done a really amazing job in creating the underlying framework. The framework upon which this Forum application sits. The clear logical separation of different application parts goes a long way in ensuring you can elegantly reuse something without resorting to hacks.

vB doesn't keep mods separate? I actually think, with vBulletin, it was quite the opposite. XenForo provides a level playing field for all the Addons; and better integration with the core components. So there's less hacking needed to just "get" things to work. The result? Less chance of addons stepping on each others' toes.

There are well defined interfaces for handling things such as attachments, likes, search, alerts, content moderation, news feeds, etc. Addons can implement each of these features without interfering with other addons or the core itself.

Anthony Parsons

Well-known member
I was actually just responding to Miko about his work... and XF being the foundation for his work, I have never seen such innovative or creative work able to be performed on other forum platforms as I'm seeing in development and "what's to come" developments from people surrounding XF.


Digital Doctor

Well-known member
I think:

Minimized Addon Clashing Infrastructure

is a major feature, and will warm the hearts of experienced forum admins.


That's not true:p

If the add-on coder have no idea what he's doing (like me some time ago) it will crash all the other add-ons running on this event*scnr*
This couldn't happen in vb, because you hadn't to run the parent action...
If something went wrong, you got an error, now with XF, it throws no error if you don't run the parent method.
In some cases you'll never realize that the other listeners weren't called


Well-known member
I actually wrote BBCM with a major clash in it. I didn't think of it till DarkImmortal's hack malfunctioning. It'll be fixed when I get time to start to finish it next week. :)


Well-known member
Anyone had any addon conflicts ?
Yeah... with my RecentThreads block in XenPorta. Several other mods are expanding the core functionality of the Thread model, so when I tried to expand the core functionality the same way, I started getting duplication errors. I fixed this by instead of expanding on the core model, I simply used the existing functions and put it together in my own thread builder.


Well-known member
Well it is used in the US, though I admit it is not often...just it's not in a custom tailored clothing is used as the past tense of bespeak which can literally mean to speak to, respond to, to address or to be accounted for. So in the context it was used (I believe) it would not be the same in both places. But funny thing is the present tense of the word can mean to request ahead of time or to engage in advance. I just found that to be a bit of awesome right there given the OP. LOL
Not open for further replies.