Thread

Hi, I’ve recently upgraded an EE site from v2.1.0 to v2.5 and after installation, I tried logging in with the correct credentials but it just reverts me back to the login page. If you enter incorrect login infos, it says it’s incorrect, so why when I enter the correct credentials will it not login?

Running on PHP 5.3. I kept the previous system files on the server so I could revert back quickly. (Which when I need to, the site works fine again)

Having looked around the forums, this http://ellislab.com/forums/viewthread/216012/ seems to be a close match to what I’m experiencing. But I’ve tried what they say and still no luck.

I’ve tried disabling add-ons by removing the third_party folder etc to see if these could be causing an issue but still no luck.

Also the frontend of the site does not work when under v2.5.

Can anyone help?

Kind regards,

Dan

I’m having the same issue. Upgraded from 2.3.1 to 2.5. When I try to login to the CP, it just takes me back to the login page - no error.

I tried deleting my cookies, restarting the browser and a different browser.

Bump. Can anyone help?

Might I also add that I also get this error when running the admin.php update wizard

Hi Daniel,

Sorry for your delay, we do our best to answer threads within 48hrs during the business week.

Bump. Can anyone help?

“Bump"ing doesn’t help - it doesn’t hurt though - however our tools allow us to track a thread based on the time of the original post. Your issue will not get lost in the pile, so no worries!

I am a little confused here - you first post mentions you were successful in the update, but your latest post says you are running the update wizard again? If the update wizard ran successfully once, there is no need to run it again.

Make sure the “installer” folder is out of /system at this point. Then try loading /admin.php and logging in.

If you get the same “redirect” loop as before, open your database using PHPMyAdmin on empty the exp_security_hashes table and try to log in again.

The most important thing at this point is a clear picture of the state of your installation and what steps you have taken so far.

Cheers,

Hey Dan

Thanks for your reply. Sorry my post(s) were a little confusing. Ok the screenshot I provided was the error message I received upon first attempt to upgrade to 2.5.  I’m still getting this after trying out lots of different things.  I can’t remember now how I managed to get to the login page, as the installer never got passed this stage. Maybe I deleted the installer without it ever succeeding? Anyhow, I’ve tried since to get to the login page with the installer and have been unsuccessful as the installer keeps crashing.

I’ve later tried to upgrade to v2.2.2 with add-ons disabled to see if there is some issue with v2.1.0 in upgrading but was presented with the same installer error.

Hi Daniel,

Ok, the installer is attempting to run from “the beginning of time”, as it were.

Before you run the installer again, open /system/expressionengine/config/config.php and tell me what you have for $config[‘app_version’] *and* look for any malformed keys that use the old $conf variable instead of $config

The installer can see those old style values and get confused about the version in should start with.

Cheers,

Hi Dan,

So I looked at the config file and seen that it was using the prior version number so I changed it to 250. I’m now at the login screen again, but back to the original problem now where I use the correct login credentials but it just refreshes the page.

Any ideas from here on?

Hey Daniel,

At this point, we need you to roll everything back to your backup. Grab you database and files from 2.1 and roll everything back - then try the update again.

So I looked at the config file and seen that it was using the prior version number so I changed it to 250.

It *should* be at the version you are starting at - that is the key that tells the installer where to start in the update process - if you set that to 2.5, no updates actually ran because the installer thinks you are up-to-date.

One thing to try before the roll-back is to set that to the version number you are running before the attempted update - “210” - and run the update again.

Also, make sure every key in /system/expressionengine/config/config.php is in the style of $config and not $conf

I look forward to your reply!

Cheers,

I still have issues logging in sometimes - I enter my credentials and I’m immediately bounced back to the login screen.

It’s somehow related to the expired logout and a cookie, although I’ve never looked into the details.

I resolve the issue by using Web Developer Toolbar in FF - I clear Session Cookies, Domain Cookies, and Path cookies and I’m able to login without getting bounced.

Hi vaughn-taylor,

Thank you for your insight and process!

Can you tell me what version of ExpressionEngine you’ve been noticing this problem?

Cheers,

Hi,

I just wanted to add that I’m having a similar issue (though from a fresh install v2.5.2 - Build Date: 20120606) with being kicked back to cp login screen with no error messages. I can’t seem to repeat the issue reliably I’m afraid, however from what I’ve seen when it does happen, I have duplicated cookies being shown in firebug. Some for sub.domain.com, some for domain.com. Both have a set of exp_whatever cookies, which I’m guessing is causing issues.

This only seems to be a issue in firefox as my client has also reported having the problem, and we’ve both “resolved” it by using different browsers (IE9 and chrome). Clearing all domain cookies also works, but I can hardly ask the client to do that everytime this happens, so any help would be appreciated.

I’m not sure if coincidence, but I only noticed this after installing the MSM. I followed exactly the steps listed in the install guide, but have not actually set up any sites as I don’t need the functionality yet.

I’ll try and spot what makes it happen, but I’m guessing it’s sort of triggered by timeouts. Let me know if there’s any other information that would help.

thanks,
Rob

Hey Rob,

You’ve given a clue:

Some for sub.domain.com, some for domain.com. Both have a set of exp_whatever cookies, which I’m guessing is causing issues.

Technically, those aren’t duplicates. sub.domain.com and domain.com are completely different and ExpressionEngine will set the cookie based on how you navigate to the site or Control Panel. With “www” for instance, is completely different to ExpressionEngine than without.

The key to to make sure you are consistent throughout the ExpressionEngine Control Panel and in .htaccess - with or without, EE doesn’t care. Consistency is important though.

~