johnbristol
04-02-2014, 01:21 PM
I'd like to bring my VBulletin 4.0.4 site up to date with 4.2.2 patch 1. I've tried before but I hit a problem and I don't know how to get past it. It's a site I bought a couple of years ago so I don't know why cms was disabled in the first place.
The admin panel Plugins & Products has cms disabled - there's a line through the title:
vBulletin CMS 4.0.4 Content Management System
There are no tables prefixed cms in the database. I've listed all the tables and the error message at http://pastebin.com/wTaj1qWM
I can upgrade as far as here:
php -f upgrade.php
Upgrading to 4.1.1 Beta 1
----------------------------------
Step 1 - Deleting orphaned article records
----------------------------------
Table 'fg_422.cms_article' doesn't exist
and there it stops.
I have it in mind that if I could run the part of a standard install which generates the 13 cms tables then I could run the update. Might that work? How would I do that?
The site's been happy for years without any of these cms tables, I don't want them back, I just want to run the update to its conclusion. I've no idea what cms is for. So long as I end up with a 4.2.2 system with all my users and threads and posts intact I've no objection to any route at all. There's 5000 users, 60,000 threads and 1,450,000 posts so I obviously want to retain all the existing data.
I'd raise a support ticket but since it's so obviously my fault I doubt I'd get any help there.
The admin panel Plugins & Products has cms disabled - there's a line through the title:
vBulletin CMS 4.0.4 Content Management System
There are no tables prefixed cms in the database. I've listed all the tables and the error message at http://pastebin.com/wTaj1qWM
I can upgrade as far as here:
php -f upgrade.php
Upgrading to 4.1.1 Beta 1
----------------------------------
Step 1 - Deleting orphaned article records
----------------------------------
Table 'fg_422.cms_article' doesn't exist
and there it stops.
I have it in mind that if I could run the part of a standard install which generates the 13 cms tables then I could run the update. Might that work? How would I do that?
The site's been happy for years without any of these cms tables, I don't want them back, I just want to run the update to its conclusion. I've no idea what cms is for. So long as I end up with a 4.2.2 system with all my users and threads and posts intact I've no objection to any route at all. There's 5000 users, 60,000 threads and 1,450,000 posts so I obviously want to retain all the existing data.
I'd raise a support ticket but since it's so obviously my fault I doubt I'd get any help there.