PP5.0 w/ vb3.0.7 upgrade, no admin
 

I hate asking since this has been gone through a million times, but after a rather large upgrade of VB and PP (and vbportal), I can't get into the PP admin panel. I've checked the cookie settings, the paths and tried every combination of each. The license is in the config-inc.php file (L1234567). I've cleared my cache, tried different browsers, and deleted all relevant cookies several times. All I get is "Invalid login. Please check your username and password, or register." I did notice that the cookie PP sets doesn't have the password encoded, but didn't see any reference to the cookie in the forums. This was a major jump in versions. vb 2.3.5 -> 3.0.7. PP 4.6.6 -> 5.

Amazingly, everything else seems to fine. Integration is working, except for the login. Any help?

Sorry, more info:

Gentoo Linux, PHP 4.3.10, MySQL 4.0.23a, currently non-public development server (trying to get upgrade done, which requires total style upgrade)

My setup is still not working. I've now totally redone the upgrade with PP5.03 and I still cannot login to the admin panel for photopost. To add to the fun, I no longer have any photos. Somewhere it broke my path settings and doesn't know where they are.

I am successful at logging in, but when I press "Admin", it tells me "Invalid login. Please check your username and password, or register.". I've verified the cookie prefix is bb in both PP and vbulletin. My license is located in the config-inc.php.

Anyone have any idea? I need to get started on finding a new Style for my site, but would rather it work first.

I've gotten virtually no where with this and I've tried everything the forums suggest. I can grant some access if someone thinks they can help me with it.

Well if your on 503 lets see this is definately cookies and license number

L1234567 THIS IS HIGHLY SUSPICIOUS. I DOUBT THATS YOUR VB LICENSE CHECK AT THE TOP OF YOUR CONFIG AND CORRECT.

Also view your photopost settings table through your database viewer(phpmyadmin) and settings 171-173 are the cookie settings. Make sure to correct as necessary to match VB most common culprit people forget to set the cookie prefix which in vb by default is bb

Well L1234567 is clearly not my license, but a representation of what a license would look like so it was not suspected that I had the customer number in there instead. I have my correct license in place.

I have tried every combination of settings for 171-173 that I can think of. Comparing these settings with those of VB and they match up perfectly, including the prefix of "bb". But for clarity, how can I verify that these three settings are what VB is set to? Where are they set in VB?

EDIT: Fixed spelling for people searching.

Well I just dealt with a guy who thought he had everything correct and he had someone else's vb on his system so check your global and see what the vb license really is

To verify your cookie settings you need to login to each and record how the cookies are being written. If you are darn sure your cookie settings match it has to be the license number

i had this EXACT same problem. i upgraded my vbulletin from 2.x.x to 3.0.7 and Photopost from 4.8 to 5.0.3. i kept getting that crazy "Invalid login" problem. here's the only thing that seemed to work for me.

in phpmyadmin, in the settings table, check id #41. that's the vbversion varname. it probably says vb2. edit it to say vb3. that's what worked for me. hope that helped.

edit: oops, i saw pictures and no table formatting. so just a reminder that you might want to set to integrated vb3 forums. this is under Forum Settings.

For everyone getting this problem, i hope this helps somewhat.

Yes and also if you switch integration types as jetrome states make sure to switch photopost from vb2 to vb3 ;)

i should mention that i had to go through phpmyadmin because when i tried editing the config files, i'd write it as vb3, but it wouldn't get written to the database settings thus giving the errors. therefore, i went through phpmyadmin.

Alright, that fixed my problem with not being able to login. Now for the rest of my issues. :)