vBulletin 5 is actually more customizable than vBulletin 4. It was more customizable at release but in different ways. The API is more robust, you can control the entire look and feel via CSS, and every page is customizable with modules. The module system itself is extendible so you can create custom modules. You can add to templates without actually editing the templates we ship through template hooks. You can expand the API with PHP Extensions. New phrases, style variables, and templates can be added using the Product System just like in vBulletin 4. You can run your own custom code. Using the API, you can actually do things programmatically in templates without the need for PHP. Things like retrieving values from the database and displaying them on a page. All of this was available at release.
The only thing that vBulletin 5 didn't ship with was the ability to store PHP Code in the database as Plugins. Since then, we have even added a plugin system but still do not allow PHP code to be stored in the database.
The only thing that vBulletin 5 didn't ship with was the ability to store PHP Code in the database as Plugins. Since then, we have even added a plugin system but still do not allow PHP code to be stored in the database.
Comment