How Can I Tell What Version I am Upgrading

[warc1]

I am trying to upgrade to V7.01. I uploaded the new version but forgot to check the version number of the old one. I backed up the old version but don't know where to look for the version number. There is a version number in the config file, but I'm not confident that I didn't use an old config file from a previous version.

[Chuck S]

The version number is in the settings table of the database also. You should be safe running upgrades from 5.1 forward without messing things up.

[warc1]

The reason I ask is because of a database connection error when trying to upgrade. I'm 90% sure that I was running v5.6. I still have the installation files for this version and the file names and sizes appear to match. I also downloaded V6.1 some time ago, but it appears that I never upgraded to it since the file names and sizes do not match my backup from yesterday.

I need to upgrade Photopost to V7.01 because I just finished upgrading Vbulletin from V3.7 to V4.0.3. This corrupted the display of Photopost, but it was still working and accessing the dedicated Photopost database. However, after uploading Photopost V7.01 and running the upgrade script from v5.6 , I get a "cannot connect to Photopost database" error immediately after confirming that I want to upgrade. Initially, I used my old config files with V7.01 since I read a post on this forum that this approach should still work. Therefore, there cannot be any typos in the database config data since I did not change it.

After getting this error, I posted my original message above in case upgrading from an incorrect prior version was the cause. However, you seem to indicate that this should not be a problem. I also tried filling in the config files that came with v7.01 with the necessary data, but this also gave me the connect error. I don't know where to go next since the database connection was working right up to the point that I first attempted to upgrade a few hours ago.

[Geiri]

Version number should be in your config-inc.php file.

Content visible to verified customers only.

[Chuck S]

well you must ensure you have the correct database information in your config-inc.php file as the only reason you would get the message it cant connect to the photopost database is if this information is incorrect.

[warc1]

I am having our database support look into the connection problem. On a related matter, I note that there are no integration options for Vbulletin V4 in the "config-int.php" file and only options for V3. Therefore, I set all of the V3 variables to "no". Is this correct?

Regards
Warc1

[Chuck S]

You would set the vb3 variables to on.

we autosense whether you have vb3 or vb4.

[warc1]

Thanks Chuck.

[Chuck S]

Your welcome

[warc1]

Our database support has identified the likely problem. They had to install PHP5 to support VB4 and did this on a new server. They had to use a new port assignment for the new server, which is 13306 and not the default 3306.

Is there anyway to address this in the config files or do all of the intall scripts that reference port 3306 have to be changed. Our database support is willing to do the latter, but I thought I would check if there was a simpler solution.

[Chuck S]

You would simply have to change 3306 to 13306 in install.php and pp-inc.php but this is a good config issue to add in the future.

[warc1]

Problem solved.

Our database support suggested tacking ":13306" to the end of the database location and that worked fine.

[Chuck S]

okay enjoy your evening.