Hello everyone
/TLDR - aiming to upgrade to V6 on Friday
The site has been "problematic" over the last few months. Numerous bugs and general weirdness have been battled with patch upgrades, RAM and processor upgrades and work arounds. At this point, we can't do anything else to save the patient. We have to upgrade.
Starting on Monday the site will be migrating (likely in stages, we are still talking with vBulletin on this upgrade path) from v 4.2.5 to the latest revision of vBulletin V6
Upgrading vBulletin is no simple task, and it must be performed in stages:
We are now in a virtual environment, that means we can clone the current production site and create a duplicate we can break without impacting production. We can do this over and over again very quickly, providing we can troubleshoot any issues quickly. We have vBulletin hired on for realtime support on this upgrade so hopefully we can get all the bugs ironed out by the end of the week.
If we hit our mark we should be ready to upgrade production on Friday.
If anything changes with the intent or timings of this project I will update here.
/TLDR - aiming to upgrade to V6 on Friday
| Step | Action |
|---|---|
| 1 | Buy vBulletin 6 license (possible upgrade discount) |
| 2 | Clone your site to a staging server or subdomain |
| 3 | Update PHP to 8.1+, MySQL to 8.0+ if needed |
| 4 | Backup everything |
| 5 | Upload vBulletin 6 files to staging, run upgrade script |
| 6 | Test plugins, themes, user flows |
| 7 | Once happy, schedule live upgrade |
| 8 | Repeat process on production site |
The site has been "problematic" over the last few months. Numerous bugs and general weirdness have been battled with patch upgrades, RAM and processor upgrades and work arounds. At this point, we can't do anything else to save the patient. We have to upgrade.
Starting on Monday the site will be migrating (likely in stages, we are still talking with vBulletin on this upgrade path) from v 4.2.5 to the latest revision of vBulletin V6
Upgrading vBulletin is no simple task, and it must be performed in stages:
- Core code and Hosting Environment
- Theme and plugins
- Customizations
We are now in a virtual environment, that means we can clone the current production site and create a duplicate we can break without impacting production. We can do this over and over again very quickly, providing we can troubleshoot any issues quickly. We have vBulletin hired on for realtime support on this upgrade so hopefully we can get all the bugs ironed out by the end of the week.
If we hit our mark we should be ready to upgrade production on Friday.
If anything changes with the intent or timings of this project I will update here.
Remember there's no buying or selling on there, so just dont or you'll either get banned if its found by the mods or you'll get the group shut down if its found by facebook. Discussion only please. 
