View Single Post
Old November 24th, 2008, 12:04 PM   #3 (permalink)
bennyng
Junior Member
Verified Customer
 
Join Date: May 2005
Posts: 21
Hi Chuck,

I'm sorry to say this, but it looks like you did not read most of my post. If you did, you would know I have already gone through the install script, figured out the problem and completed my upgrade.

My so-called "hack" is a true plug-in only product for vBulletin and requires no modification to vBulletin nor vbGallery code at all. So the problem is not because of code modifications in my copies of vBulletin and vbGallery. The only modifications are in the templates and those do not affect the installation/upgrade scripts.

The problem seems to be in the install script which is not accounting for a version before or near 2.0B2. At least, that is what my experience with the upgrade is suggesting. I share with you what I did to make it work, so you can figure out the root cause.

In order for my upgrade to happen correctly, I had to change the gallery_version stored in my UNALTERED adv_setting table from '2.0' to '2.0B2'.

Please, I am not here to make trouble. I am just doing my part as a member of the community to share what I went through and report a potential flaw in the install script.

I've done tech support before and I know it's easy to assume that the user did or is doing something wrong. I'm here trying to present my experience and findings as clearly as possible for the benefit of the other users. It is sad for the community that my post is brushed aside as a problem associated with a so-called "hack".

I am still happy to answer any queries from the tech team if they have any.
bennyng is offline   Reply With Quote