No access to admin functions after upgrade and change

[russellw]

I upgraded our PP Pro installation from 5.02 to 6.1 without any real dramas.

After doing so I successfully logged into the admin section and changed a few settings to our normal preferences.

At this stage everything was working fine until I noticed that the forum home page had these two errors:

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /photos/inc_photopost.php on line 68

Warning: mysql_free_result(): supplied argument is not a valid MySQL result resource in /photos/inc_photopost.php on line 89

A search here led me to make a change in the integration settings by adding the pp prefix but immediately after doing so I was given a login screen that while it logged me into the gallery does not provide me with an Admin link as I had before.

Attempts to log into adm-index.php requires two attempts and then I am just at the gallery home page (index.php) and still with no admin link.

The forum home page now shows no errors so that was fixed at least!

... BUT the gallery home page shows two above the header:

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /photos/forums/vb3.php on line 32

$results = mysql_fetch_array($queryv);


Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /photos/pp-inc.php on line 4146

while( list( $usergroup,$cpaccess_a,$modaccess_a,$diskspace_a,$uploadsize_a,$uplimit_a,$uploads_a,$comments_a,$ueditpho_a,$ueditposts_a,$useralb_a,$reqmod_a,$assign_a ) = mysql_fetch_row($result) )


I have triple checked that the config-inc.php and config-int.php files are exactly as they were in the 5.02 configuration and the critical elements read thus:

config-inc.php -

$VERSION = "6.1";
$PP_PATH = "/var/www/html/photos";
$TMPL_PATH = "templates"
$host="localhost";
$database="forum";
$mysql_user="admin";
$mysql_password="xxxxxx";
$pp_db_prefix = "pp_";
$host_bb="localhost";
$database_bb="forum"
$user_bb="admin";
$password_bb="xxxxxx";
$mogrify_command = "/usr/local/bin/mogrify";

I've just noticed the comment in that file about the $pp_db_prefix setting -

// If you want to use a prefix for your database, enter it here.
// NOTE: This variable can only be set PRIOR to your first installation of PhotoPost;
// existing databases will not be changed and you will be unable to connect if you change
// this variable after performing a default installation.

That sounds as if I did change that setting when I edited the integration settings in the admin section - although the field was blank and I added the value pp (which probably should have been pp_) but it was in the config-inc file anyway as I had copied the information in that from our old one. Just guessing!

config-int.php -

$vbpath = "/var/www/html/";
$pppath = "/var/www/html/photos";
$url_path = "http://www.fordforums.com.au/photos";
$vb_urlpath = "http://www.fordforums.com.au/";
$data_dir = "http://www.fordforums.com.au/photos/data";
$pp_db_prefix = "pp_";
define( "MOBILE_CAT", -1 );
define("VB3_INTEGRATION", 'on');
define("VB3_ENHANCEDINT", 'on');
define("VB3_COMMWYSIWYG", 'on');
define("VB2_INTEGRATION", 'off');
define("VBP2_INTEGRATION", 'off');
$vbportal="/home/sites/yoursite/web/vbportal";

The vBulletin version is 3.0.3; pHp 5.1.6; mySQL 5.0.45

My thoughts are that it is an integration issue of some kind - it looks as if PP is not recognising me as having admin rights.

Any help appreciated.

Cheers
Russ

[russellw]

Having done some more reading it seems that there might be a cookie issue (it was mentioned in the upgrade.txt file) but in the default config-inc and config-int files there is no setting for it?

I might try entering the values and see what happens.

Cheers
Russ

[russellw]

Update:

After editing the pp_settings table in mySQL to remove the pp_ setting from Forum database table prefix (which was wrong of course), I now have access to the admincp again and the errors have gone as well!

I don't know whether I still need the cookie settings in there but they don't seem to have broken anything on either end so they may as well stay.

There are a couple of look and feel items I'd like to change but I will post that question in the appropriate place.

Cheers
Russ

[Chuck S]

Russ no problems let is know but what do you mean you upgraded to 6.1?

Our current code is 7.01 as 6.1 was released maybe 2 years ago.

[russellw]

Hi Chuck

We were 5.02 (a combination of no time and a lot of modified vbulletin code). I upgraded to 6.1 as it was the last version I had in my downloads folder and only then after somebody had managed to hack the showphoto.templ file to display an ad that linked to a site full of viruses.

My fault as the dir permsisions had not been reset after the last HDD crash and I've made sure it won't happen again.

I am planning an upgrade to 7.01 for next weekend after ensuring it isn't going to cause any dramas with the ancient vbulletin version.

Cheers
Russ

[Chuck S]

ah okay well 7.01 like any of our versions should work with any prior versions what do you mean by ancient?

[russellw]

Hi Chuck

Ancient = 3.0.3

Cheers
Russ

[Chuck S]

should be okay might be one or two issues depending you would really need to test it. I dont think anyones ran 3.03 in along along time.