PhotoPost Community - View Single Post

bennyng · November 23rd, 2008, 12:44 PM

Hi,

I just upgraded my forum to 3.7.4 yesterday and tried upgrading PhotoPost vbGallery. Had a hard time getting it to upgrade properly, but finally solved it by looking through the installer codes. I'm sharing my experience and the solution here in case anyone else has the same problem. vbGallery techs should probably investigate if they missed something in the installer code.

My vbGallery before upgrading was 2.0 (as stated at the bottom of my gallery pages.

Followed instructions and edited the config file, uploaded the files, etc. When I tried the Upgrade option in the installer page, it just kept coming back to the Installer option page without visibly doing anything.

The problem was with the gallery_version stored in the adv_settings table in the database. It was "2.0". But looking in the code, for case "2.0", it expected the ppg_ prefixed tables to exist, but my tables were still using the old prefix.

The case statement previous to that is "2.0.0" and it rename the tables from the old prefix to the new prefix, so I restored my gallery tables and changed gallery_version in my table to "2.0.0". Ran the upgrade again and it renamed the tables. However, when I viewed the gallery page, I got several "PHP Warning: Invalid argument supplied for foreach()..." message. I looked at the code lines indicated and seemed that some option variable was not being initalised. So back to the installer code and I noticed that for case "2.0B2" the installer did some things involving adv_gallery_opt in the datastore table.

Restored the my gallery tables once again and set my gallery_version to "2.0B2". This time the upgrade worked like a charm.

So, tech team, you might have missed one of the versions put out by the previous guy (who came onboard from VBA (iirc) when PP bought over vbGallery). Seems my copy of vbGallery is similar to 2.0B2, although the gallery_version was set as "2.0".

I can't remember the exact sequence of release, but I believe the version I had is before 2.0B2. The installer code looks for and removes the "vp_wol4vbagallery" product in version 2.0B2 case statement and that is actually a product that I developed and the previous vbGallery guy asked from me for permission to use in the next release (I assume to be 2.0B2). I did not install that version probably because (a) it was a minor release, and (b) I have that product.

I'll be happy to answer any queries from the tech team via PM. If I do not reply, please email me.

For others, please be sure what you are doing. I am a software developer and I know how to tinker with codes, databases, etc. I will NOT be responsible for any damage to your forum or gallery because you tried to do what I describe in this post. Best to get help from the vbGallery techs.

Please do not PM me for help. I am swamped by my own work, plus I do not know enough of vbGallery.

November 23rd, 2008, 12:44 PM	#1 (permalink)
bennyng Junior Member Verified Customer Join Date: May 2005 Posts: 21	Bug in installer? Hi, I just upgraded my forum to 3.7.4 yesterday and tried upgrading PhotoPost vbGallery. Had a hard time getting it to upgrade properly, but finally solved it by looking through the installer codes. I'm sharing my experience and the solution here in case anyone else has the same problem. vbGallery techs should probably investigate if they missed something in the installer code. My vbGallery before upgrading was 2.0 (as stated at the bottom of my gallery pages. Followed instructions and edited the config file, uploaded the files, etc. When I tried the Upgrade option in the installer page, it just kept coming back to the Installer option page without visibly doing anything. The problem was with the gallery_version stored in the adv_settings table in the database. It was "2.0". But looking in the code, for case "2.0", it expected the ppg_ prefixed tables to exist, but my tables were still using the old prefix. The case statement previous to that is "2.0.0" and it rename the tables from the old prefix to the new prefix, so I restored my gallery tables and changed gallery_version in my table to "2.0.0". Ran the upgrade again and it renamed the tables. However, when I viewed the gallery page, I got several "PHP Warning: Invalid argument supplied for foreach()..." message. I looked at the code lines indicated and seemed that some option variable was not being initalised. So back to the installer code and I noticed that for case "2.0B2" the installer did some things involving adv_gallery_opt in the datastore table. Restored the my gallery tables once again and set my gallery_version to "2.0B2". This time the upgrade worked like a charm. So, tech team, you might have missed one of the versions put out by the previous guy (who came onboard from VBA (iirc) when PP bought over vbGallery). Seems my copy of vbGallery is similar to 2.0B2, although the gallery_version was set as "2.0". I can't remember the exact sequence of release, but I believe the version I had is before 2.0B2. The installer code looks for and removes the "vp_wol4vbagallery" product in version 2.0B2 case statement and that is actually a product that I developed and the previous vbGallery guy asked from me for permission to use in the next release (I assume to be 2.0B2). I did not install that version probably because (a) it was a minor release, and (b) I have that product. I'll be happy to answer any queries from the tech team via PM. If I do not reply, please email me. For others, please be sure what you are doing. I am a software developer and I know how to tinker with codes, databases, etc. I will NOT be responsible for any damage to your forum or gallery because you tried to do what I describe in this post. Best to get help from the vbGallery techs. Please do not PM me for help. I am swamped by my own work, plus I do not know enough of vbGallery.