Which comes first? (Upgrading)

[oldengine]

Currently running vBulletin 3.6.2 (patched)

Currently running vBGallery 2.1 (10.27.06 download)

Looking to bring vBulletin up to 3.6.8 and vBG up to 2.3.

Which one gets updated first?

I'll also be installing some new styles - do they go in last?

My old saying is, "If it ain't broke, don't fix it." But, all other wisdom indicates that upgrading is important.

[Chuck S]

With those versions it would not matter what order you do things but I always do a forum first then anything else.

[Zachariah]

Currently running vBGallery 2.1

There were a lot of code changes. Make sure you disable add-ons in your site that pull gallery data before you update. Later you can turn them back on. It will cut down on errors that might pop up.

[oldengine]

How do I get update to run after it has already run once?

(I'm working with 1 gig of database)

Invalid SQL:
ALTER TABLE ppgal_images DROP INDEX dateline;
MySQL Error : Can't DROP 'dateline'; check that column/key exists
Error Number : 1091

Invalid SQL:
CREATE TABLE ppgal_stats (
dateline int(10) unsigned NOT NULL default '0',
necard mediumint(8) unsigned NOT NULL default '0',
nimage mediumint(8) unsigned NOT NULL default '0',
npost mediumint(8) unsigned NOT NULL default '0',
PRIMARY KEY (dateline)
) TYPE=MyISAM;

MySQL Error : Table 'ppgal_stats' already exists
Error Number : 1050

You are already running the current version of PhotoPost vBGallery Photopost vBGallery.

[oldengine]

Reloaded the backup database, turned off all products, rerun vbgallery_install and...

Invalid SQL:
CREATE TABLE ppgal_stats (
dateline int(10) unsigned NOT NULL default '0',
necard mediumint(8) unsigned NOT NULL default '0',
nimage mediumint(8) unsigned NOT NULL default '0',
npost mediumint(8) unsigned NOT NULL default '0',
PRIMARY KEY (dateline)
) TYPE=MyISAM;

MySQL Error : Table 'ppgal_stats' already exists
Error Number : 1050

[oldengine]

My tables:

vbul.ppgal_categories OK
vbul.ppgal_customfields OK
vbul.ppgal_customfields_entries OK
vbul.ppgal_ecards OK
vbul.ppgal_exif OK
vbul.ppgal_favorites OK
vbul.ppgal_filetypes OK
vbul.ppgal_images OK
vbul.ppgal_moderator OK
vbul.ppgal_permissions OK
vbul.ppgal_posts OK
vbul.ppgal_rate OK
vbul.ppgal_search OK
vbul.ppgal_setting OK
vbul.ppgal_settinggroup OK
vbul.ppgal_stats OK
vbul.ppgal_subscribecat OK
vbul.ppgal_subscribeimage OK

[oldengine]

I deleted that pesky TABLE ppgal_stats and I think I'm on the road to recovery.

[Zachariah]

Hows the progress ?

[oldengine]

Doing fine I guess. What a day!

Too many hacks and I waited too long for the main vBulletin upgrade. Like I said, if it ain't broke, don't fix it.

That upgrade section of the install program needs to be a bit more user friendly. On a fresh install, everything might be fine, but if you need to re-run install, some bullet-proofing is needed for those strange circumstances.

I have absolutely no idea why ppgal_stats was in my database unless it came in with 2.1 and if it came in with 2.1 then 2.3 should have been expecting to find it already in place.

Anyway, it's up and running and no errors are spewing forth from sql.

[oldengine]

Eleven days later and everything is running excellently (knock on wood) and now it's time for another upgrade. Noooooo!!!

Threads: 39,071, Posts: 243,214, Members: 11,665

Categories: 104, Images: 5,341, Posts: 210, Total Views: 978,084, Disk Space: 358.56 MB