Cannot login to admin area after 4.8.5 upgrade

kall · December 17th, 2004, 06:56 AM

I have followed the instructions in the upgrade thread as far as I can tell.

Everything looks to be fine, except when I click the Admin link, I am greeted with a non-styled login page, and when it is sucessful, it reloads the main gallery page.

Where in 4.8.5 are the cookies info defined? I'm thinking this is the issue.

Michael P · December 17th, 2004, 08:44 AM

Which integration are you using?

kall · December 17th, 2004, 02:24 PM

Enhanced vb3 and normal vb3.

I may try a fresh install soon, see if that works.

Chuck S · December 17th, 2004, 08:12 PM

I do not beleive the style is pulled in the Photopost login page for Vb3 but michael may know better

kall · December 17th, 2004, 08:35 PM

I still think it had something to do with the cookies info not getting entered..

A fresh install of 4.8.5 is working relatively well, I have started a new tread for the 'Bulk move only showing default cats' issue.

Denz · December 18th, 2004, 10:52 AM

Hi,

I'm also having the exact same problem with the upgrade and the admin area.

gholsie · December 18th, 2004, 04:49 PM

Me too!

gholsie · December 18th, 2004, 05:08 PM

Ok, I've made some headway on this issue. The installation instructions are lacking some CLEAR understanding. When upgrading *DO NOT* upload the new config-inc.php. The script file upgrade482.php needs to see your old config-inc.php file so it can strip out the settings and put them into the database.

I ran the upgrade with the NEW config-inc.php format and it wasn't able to populate the databse with the necessary information!!

Anyway, here's what I did to get my admin login to work:

1) Restore my old database.
2) Copy my OLD config-inc.php file to the photopost directory.
3) Run the upgrade482.php (make sure it's in the root photopost dir).
4) Rename my old config-inc.php file to config-inc.php.XXX
5) Modify the NEW config-inc.php to match my system.
6) Copy the NEW config-inc.php file to my photopost directory.

-- Mike

Chuck S · December 18th, 2004, 05:19 PM

Actually I beg to differ.

The upgrade documentation has stated for a long time never to overwrite your config-inc.php

2) Upload all files - except config-inc.php, unless you modified it from the ZIP file - to
your server. You do not need install.php for an upgrade.

But yes your right if you overwrite your config file you do not have any cookie entries as the new install file populates that for you.

gholsie · December 18th, 2004, 05:43 PM

Agreed, the install instructions do say that you should NOTupload the new config-inc.php. I must have seen the new format of the file and used the new one instead of keeping my old one. I simply modified it and uploaded as if it were a new installation.

However, I must say that it is a good idea to put the newly formatted config-inc.php file on a system AFTER it has been completely upgraded.

-- MIke

Chuck S · December 18th, 2004, 05:48 PM

If you go to your admin edit config and save the config your old config is written to the new format so you never upload a new one IMO

wajones · December 19th, 2004, 01:41 AM

I had the same problem upgrading from 4.7h and found that the "Forum Cookie Prefix" didn't get set, I believe this may be because I didn't edit the config-int.php, but that's only a guess. It's a new file and easily overlooked. I fixed by editing the 'settings' table 'Forum Cookie Prefix' field and setting to 'bb' for vBulletin using phpmyadmin.

spinaltoad · December 19th, 2004, 05:59 AM

I found that the intergration didn't work the way I liked it when I upgraded photopost and vbulletin. Here is what I did.

CODE REMOVED TO NOT CONFUSE PEOPLE AND STAY TRUE WITH THE TOPIC.

Chuck S · December 19th, 2004, 09:59 AM

What did you do the above for?

I think your confusing steps. There is no code modifications needed. you just need to take care of each issue one at a time.

If you upgrade your VB naturally you then UPDATE Photopost to use VB3 not VB2 and then when correctly able to login you then UPGRADE THE SOFTWARE TO THE NEW 4.8.5 VERSION

You were trying to do two things at once and confused yourself on what steps come where and then think there is a problem when there is not.

The cookie variables are no longer stored in the config file but in the database. and no matter what if you switch integration types of course you would need to switch the type in mysql if you cant login.

wajones · December 19th, 2004, 12:15 PM

Chuck, I ran the upgrade several times and it missed updating the 'Forum Cookie Prefix' each time and I was not able to log into the admin until I manually entered it using phpmyadmin.

kall · December 19th, 2004, 01:23 PM

This exact thing happened to me each time I tried to upgrade....and in each case, running upgrade482.php gave 'cannot connect to the photopost database' ...the $link values were not getting pulled from anywhere.

After dropping every table and starting a fresh install, the old prefix appeared in the config display.

Other things also had to be re-entered/changed after installation.

Chuck S · December 19th, 2004, 02:01 PM

Are you overwriting your old config before an upgrade? Because the upgrade instructions are explicite not to do this.

On a new installation you input your cookie settings etc and VB license number etc upon install.

I have done an upgrade and an install and in both cases everything is fine.

The only issues reported and solved is alot of users where overwriting there config files on upgrade which is a no-no.

Upon an upgrade you would do two things.

First go to admin options and input the proper cookie variables under cookie settings.

Second go to config options and save that to make the config save as a new one.

On an install all values are entered by what you place them to be when installing. If you set VB3 integration to yes then we bypass the photopost cookie settings and use your Vb cookie settings so there the automatic login is full proof IMO.

If you are deviating from the normal upgrade instructions that is where you could have had issues or on a new install not entering the proper cookie stuff then I can see you having an issue with cookies.

Even more so if you are using the VB3 enhancements and we are using your vb3 cookie settings I fail to see how there could be an error at all.

kall · December 19th, 2004, 02:13 PM

Quote:

Originally Posted by omegatron

On an install all values are entered by what you place them to be when installing.

No they are not. The following is from the fresh install I did yesterday:

At no point during install did I tell the script that my admin address was admin@domain.com, I entered the correct one. After install, it said admin@domain.com in 2 places.

Also, at no point during install did I specify that it should use the old (deleted) database prefix. After install, in the bit that says (MUST NOT BE CHANGED AFTER INSTALL), it had pp23_, which was not entered during install and was in fact no longer in the database.

Now, my host has the TurckMM cache thing turned on. Could *this* be affecting things?

Chuck S · December 19th, 2004, 02:55 PM

It could be.

You where talking about cookie settings and not being able to login in above how did we get to admin emails?

I would definately say you have something on your server interfering with things as I have done new installs and upgrades many times over trying to find issues.

The instructions posted above are accurate and the only issue related to people not being able to login is user error thus your issue would have to be server related to some sort of cache thing.

Reading up on this turck cache thing I would definately suspect that as its holding php scripts in buffers to execute things.

Jarvis · December 19th, 2004, 04:12 PM

I cannot log into the admin area, either. I did a new install of 4.8.5 and have vb3 integration turned on. Each time I try and login to the admin area, I am challenged with the login screen and upon successful login taken back to the user index. The integration appears to be working as the auto login between forums and photopost is working, but admin area is unavailable.

Thanks.