As an existing user of vbGallery on a VB3.8 board, I am planning to upgrade to the forum to v4 very soon and just curious what the smoothest path will be to get vbGallery working on the vb4 upgrade/retaining everything from the vb3/vbGallery system.
Please confirm if I have the right approach mapped out here...
Current system with vBulletin 3.x and vbGallery (and vbAdvanced, vbLinks, etc.)
1. Turn off vbGallery in admincp (looks like this just ables access to registered users, and doesn't disable the module.
2. Disable other installed products (vbAdvanced, etc.).
3. Upgrade vBulletin to 4.x.
4. Upgrade vbGallery to 3.x.
5. Turn vbGallery back on.
6. Upgrade vbAdvanced and other scripts.
Its been a long time since I've installed a vB upgrade, so I'm wanting to make sure I do this in the right order. My users have over 15K images in vbGallery, so I don't want to find myself in a state where they are lost. It seems like after I upgrade vBulletin, and have not yet upgraded vbGallery, that things could be in a messed up state there... or will it just be broken until I complete the vbGallery upgrade?
Chuck, I've gotten further and think I'm close to having this figured out. The process I'm following is this...
1. Remove vbAdvanced.
2. Remove vbLinks.
3. Remove all plugins and products.
4. Change to default template and revert all parts of template to default.
5. Upgrade vBulletin to 3.6.
6. Upgrade vbGallery to 2.4.2.
7. Upgrade vBulletin to 3.8.
8. Upgrade vbGallery to 2.5.2.
This is going clean up until this point. All looks good and everything works. I "should" at this point have a clean vBulletin 3.8 system with vbGallery 2.5.2. The nav bar does have the vbGallery little drop down menu there... and the one for vbLinks is still there too for some reason.
9. Upgrade vBulletin to 4.0.
The upgrade goes smoothly until its done and I try to log-in. I can't get into the admincp at all and I get similar errors on all pages...
Content visible to verified customers only.
I also get an error about the cookie already being written only when trying to log into admincp.
Any ideas what is causing these errors? It is definitely something left over from vbGallery. I tried going ahead and installing vbGallery 3.0 but it fails out of the gate because it can't get logged into admincp to do the upgrade.
I think if I can figure out this last issue I'll be able to go ahead and install this puppy. Ideas?
Thanks for the reply. That is what I intended to do, but didn't get that far. Based on the steps posted up earlier in the thread, I thought the order was to upgrade vBulletin to 4.0 and then upgrade vbGallery to 3.0. Once I upgrade vBulletin to 4.0, the errors persist and the vbGallery install script won't run. Should I upgrade vbGallery to 3.0 first?
If there is something else going on here, any ideas where I should be looking for problems? I am going to get it back up to the step prior to 4.0 and hopefully will have some ideas. It takes me about 2-3 hours to go through all those steps again, so I guess I'll take another backup at that point next time.
Well have you done as instructed on the vbulletin site on upgrading
From what I remember the plugin system should be turned off when upgrading to vb4. If your getting some errors as your suggesting that suggests your plugin system is on. I beleive the vb support site has a line you can put in your config file that turns off the plugin system globally that should solve your error. You can then go in and install the vbgallery upgrade.
To my knowledge you must be on the vbgallery page when trying to log in as I do not understand why your calling gallery templates on a forum page but anyway that should solve the problem by turning plugins off all together.
Thanks Chuck... I'll look at the plug-in instructions on vbulletin site and review everything. I'm definitely not on the vbGallery page when trying to log in... it actually generates those two errors on any page... blog, cms, or anything. I'm going back through the process again and will update you when I get to that point again.
One question for you... where does this stuff in the navbar get put in? This is one thing I was thinking may be causing an issue, but maybe not. Also, I uninstalled vbLinks, yet its still there so I'm wondering if this is something I added or it gets put in with the installation. Since vbGallery is there, I figured you might know where this is coded?
Scratch that last question... I found that not all my templates were reverted.. I had to open each template group and found more in red... navbar being one of them. I've now reverted everything and if I turn off plugins, the vbgallery navbar entry goes away, and if I turn on plugins, the vbgallery navbar entry is there... and vblinks is gone. I've backed up here and will now try the vb4 upgrade again.
It failed again. I had upgraded to vb3.8 and vbg2.5.2, stripped all other plugins and such, reverted all template changes, and deleted all templates except the default. I turned off plugins in admincp before running vb4 upgrade and I'm getting similar errors again. If you want to see what I'm seeing, the test site is at NorthEastFoto.com TEST2 - The Front Page ... you'll notice a hosed up template, and then click on forum or blog and you'll get the errors.
One more question... where is vbgallery 3.0 pulling its url from? On my test site it keeps going back to the main site's url and not the test site url http://mysite.com vs. http://mysite.com/~testsite. I have the correct url set in the vbulletin options, and its working for all the other components, but vbgallery is going back on every click to the main url.
Getting so close here. I went ahead and installed vBulletin 4.1 ... figured I might as well go all the way there while I'm doing this, and now I seem to have lost the vbGallery admin functions from admincp. They were definitely there after 4.0 was functional. Any idea how to get them back?
OK... so many places to trip up. I inadvertently dropped myself in the superadmin list in config.php, and then I saw that I had to add vbgallery back in on the admin permissions. Did that, got the urls set, and now the test seems to be going well. May be ready to give it a go on production.