ForumCrafts — plugins, themes, extensions, add-ons & tools for real boards — tools for real boardsDownloads & licences →

vBulletin guide

How to install a vBulletin product (vB4 and vB5)

4 minute read · last checked 25 October 2026

vBulletin calls its add-ons products. A product is an XML file that defines templates, phrases, settings and plugins, plus whatever PHP files the product needs on disk. Installing one is an import, not an upload.

1. Back up

Database dump and a copy of the forum root — for vBulletin the safest unit is the whole directory. If a product goes wrong it can take the admin panel with it, and then file access is the only way back.

2. Put the files where the readme says

VersionXML goes toOther files
vBulletin 5core/packages/core/ and its subfolders, following the archive structure
vBulletin 4includes/xml/usually includes/, plus images under the style folders

Keep the folder structure from the archive exactly. vBulletin products reference their files by path.

3. Import the product

vBulletin 5: AdminCP → Products → Add/Import Product → choose the XML from core/packages/.

vBulletin 4: AdminCP → Plugins & Products → Manage Products → Add/Import Product.

On the import screen, leave Allow Overwrite = No for a first install. Set it to Yes only when you are deliberately upgrading an existing product — that flag is what lets a new version replace the old one instead of being refused.

4. Check the obvious things

  • Settings — AdminCP → Options → find the group the product created.
  • Permissions — AdminCP → Usergroups → Usergroup Manager, if the product added its own permissions.
  • Cache — some products need the board to rebuild its caches; the readme will say so.

Uninstalling

AdminCP → Manage Products → the product → Uninstall. vBulletin removes its templates, phrases, plugins and settings. That is a real delete — this is one of the few places where "I will just uninstall it and reinstall" loses configuration, so take the dump first.

Then delete the files you uploaded from core/ or includes/.

If the import fails

The usual cause is a truncated upload: vBulletin XML files for large products are not small, and a partially uploaded file parses as garbage. Check the file size on the server against the file size in the archive, then re-upload.