If you are reading this, chances are you are wondering why after applying the patch from the vBulletin announcement that your version number hasn’t changed. This short post will explain the differences of patching, and upgrading, so hopefully in the future this question will come up less.
Patching:
What it is;
- To patch something is to fix it, temporarily. It is not meant for a long term solution
- It does fix the problem and allow you to continue operating safely.
- It is not upgrading
Why do we patch instead of upgrade?
- Patching can be quicker, especially for users who are on lower grade connections
- To fix the security exploit now, if you do not have the time to manage a full upgrade
- For users who do not wish to upgrade due to massive core code changes
What doesn’t patching do?
- It doesn’t fix the other bugs in the software, it only fixes the immediate security risks that are present.
- It doesn’t change your version number.
If you want to get all of your bugs fixed, and security issues, you need to upgrade.
Upgrading consists of uploading most of the vBulletin files from the zip; you are not required to re-upload the images folder or the cpstyles folders. Once the files have been uploaded you must run install/upgrade.php.
If you have more questions about upgrading, please see our Upgrading FAQ’s and the Online Documentation on Upgrades. If you still have questions please Start a New Thread.
