[CMS] "vBulletin CMS may already be installed. Please contact vBulletin support."

[milaszewski]

after upgrading from 4.0.2 to 4.0.3 CMS disappeared and I get this while trying to import it:
vBulletin CMS may already be installed. Please contact vBulletin support.

when I look at PHP MyAdmin I can see my articles and categories

[Zachery]

Opening a support ticket would be best.

[milaszewski]

I did that in the first place. But maybe someone will come up with a solution faster here.

[milaszewski]

I read on the forums that one solution is to reinstall CMS... but I don't want to loose my CMS articles...

[milaszewski]

Opening a support ticket would be best.

it is taking very long ... there is no response to my ticket yet
has anyone else had a similar problem? I tried to export SQL tables with cms_ and then import it to a fresh CMS install but it doesn't work and causes a huge amount of errors...

[milaszewski]

I exported all cms_ tables, imported them to a fresh install of vbulletin and it works fine... Ticket support failed me. They say there is nothing I can do. But it really works good on a fresh vbulletin install. On my main forums it doesn't - even when I reinstall CMS product.

[Michael König]

If anyone has the same problem, try this:

1. Create a backup of your database.
2. Execute this query:
   

   INSERT INTO product (productid, title, description, version, active) VALUES('vbcms', 'vBulletin CMS', 'Content Management System', '4.0.3', 1);

3. Execute this query:
   

   UPDATE template SET product = 'vbcms' WHERE title IN ('vbcms_widget_recentposts_config', 'vbcms_widget_recentposts_page');

4. Run finalupgrade.php?step=6 again

[milaszewski]

If anyone has the same problem, try this:

1. Create a backup of your database.
2. Execute this query:
   

   INSERT INTO product (productid, title, description, version, active) VALUES('vbcms', 'vBulletin CMS', 'Content Management System', '4.0.3', 1);

3. Execute this query:
   

   DELETE FROM template WHERE title LIKE 'vbcms_%' AND product = 'vbulletin' AND styleid = -10;

4. Run finalupgrade.php?step=6 again

I followed your instructions but then accessing home page returns this:

The default route 'content' is not valid on line 354 in  /home/jacek/public_html/vb/router.php
#0 /home/jacek/public_html/vb/router.php(318):  vB_Router::getDefaultRoute(404)
#1 /home/jacek/public_html/vb/router.php(207):  vB_Router::newRoute('content')
#2 /home/jacek/public_html/vb/bootstrap.php(58):  vB_Router::getResponse()
#3 /home/jacek/public_html/content.php(30):  require_once('/home/jacek/pub...')
#4 {main}


Fatal error: The default route  'content' is not valid on line 354 in [path]/vb/router.php  in [path]/vb/vb.php on line 287
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        #0  vb_error_handler(256, The default route 'content' is not valid  on line 354 in /home/jacek/public_html/vb/router.php , /home/jacek/public_html/vb/vb.php, 287, Array ([exception] =>  vB_Exception_Critical Object ([] => ,[] => ,[] => ,[] => ,[]  => ,[] => ,[] => The default route 'content' is not valid,[]  => ,[] => 0,[] => /home/jacek/public_html/vb/router.php,[]  => 354,[] => Array ([0] => Array ([file] =>  /home/jacek/public_html/vb/router.php,[line] => 318,[function] =>  getDefaultRoute,[class] => vB_Router,[type] => ::,[args] =>  Array ([0] => 404)),[1] => Array ([file] =>  /home/jacek/public_html/vb/router.php,[line] => 207,[function] =>  newRoute,[class] => vB_Router,[type] => ::,[args] => Array ([0]  => content)),[2] => Array ([file] =>  /home/jacek/public_html/vb/bootstrap.php,[line] => 58,[function]  => getResponse,[class] => vB_Router,[type] => ::,[args] =>  Array ()),[3] => Array ([file] =>  /home/jacek/public_html/content.php,[line] => 30,[args] => Array  ([0] => /home/jacek/public_html/vb/bootstrap.php),[function] =>  require_once))),[code] => 256)) called at [(null):0] #1  trigger_error(The default route 'content' is not valid on line 354  in /home/jacek/public_html/vb/router.php , 256) called at [/home/jacek/public_html/vb/vb.php:287] #2  vB::handleException(vB_Exception_Critical Object ([] => ,[] =>  ,[] => ,[] => ,[] => ,[] => ,[] => The default route  'content' is not valid,[] => ,[] => 0,[] =>  /home/jacek/public_html/vb/router.php,[] => 354,[] => Array ([0]  => Array ([file] => /home/jacek/public_html/vb/router.php,[line]  => 318,[function] => getDefaultRoute,[class] =>  vB_Router,[type] => ::,[args] => Array ([0] => 404)),[1] =>  Array ([file] => /home/jacek/public_html/vb/router.php,[line] =>  207,[function] => newRoute,[class] => vB_Router,[type] =>  ::,[args] => Array ([0] => content)),[2] => Array ([file] =>  /home/jacek/public_html/vb/bootstrap.php,[line] => 58,[function]  => getResponse,[class] => vB_Router,[type] => ::,[args] =>  Array ()),[3] => Array ([file] =>  /home/jacek/public_html/content.php,[line] => 30,[args] => Array  ([0] => /home/jacek/public_html/vb/bootstrap.php),[function] =>  require_once)))) called at [(null):0] 

What is very weird, when I take all "cms_" tables and import them to a fresh installation of VB 4.0.3 it works just fine. Just right now with my main forum I have an option of creating completely fresh CMS tables. Importing "cms_" tables fails and always gives me the error above.

[milaszewski]

any ideas?

[milaszewski]

vb ticket support is terrible very slow

if I import cms_ tables from my 4.0.2 backup will I be able to to re-run step 6?

[Seven Skins]

If anyone has the same problem, try this:

1. Create a backup of your database.
2. Execute this query:
   

   INSERT INTO product (productid, title, description, version, active) VALUES('vbcms', 'vBulletin CMS', 'Content Management System', '4.0.3', 1);

3. Execute this query:
   

   UPDATE template SET product = 'vbcms' WHERE title IN ('vbcms_widget_recentposts_config', 'vbcms_widget_recentposts_page');

4. Run finalupgrade.php?step=6 again

I had the same issue.
CMS disappered after upgarde.

Followed the above steps and got CMS back.

Thanks

[TheLastSuperman]

If anyone has the same problem, try this:

1. Create a backup of your database.
2. Execute this query:
   

   INSERT INTO product (productid, title, description, version, active) VALUES('vbcms', 'vBulletin CMS', 'Content Management System', '4.0.3', 1);

3. Execute this query:
   

   UPDATE template SET product = 'vbcms' WHERE title IN ('vbcms_widget_recentposts_config', 'vbcms_widget_recentposts_page');

4. Run finalupgrade.php?step=6 again

I logged in just to say thanks for that

Worked like a charm and CMS is back, Milas did you make sure to rerun it from the finalupgrade.php?step=6 after running those two sql queries?

[milaszewski]

I logged in just to say thanks for that

Worked like a charm and CMS is back, Milas did you make sure to rerun it from the finalupgrade.php?step=6 after running those two sql queries?

no, I had to revert to backed up copy of 4.02 and I re-run the upgrade