Just upgraded manager to 2.2.13 from 2.0.4 and cant login!

I've just upgraded manager to 2.2.13 from 2.0.4 and cant login to the manager despite all credentials being correct and even completing the forgotten login bits when it sends you a new password... any ideas???

Make sure that your browser cache and the cookies for the domain are cleared.

Quote from: sottwell at Jul 02, 2014, 09:48 PM

Make sure that your browser cache and the cookies for the domain are cleared.

Not sure how to clear domain cookies - but browser cache is defo clean.... Looking at the _users in the DB the hashclass for the user is hashing.modMD5 - looking at http://rtfm.modx.com/revolution/2.x/administering-your-site/security/troubleshooting-security/resetting-a-user-password-manually it would seem it should be hashing.modPBKDF2

Is this the issue?

Also SEO urls are not working - despite the .htaccess file being correct... index.php?id=1 works... so DB connection is working as MOST of the content is being pulled - some TV bits are missing though???

I am wondering if the DB structure / setup / code is so different from v 2.0.4 to 2.2.13 that an upgrade is not possible????

Please can someone help this really is a royal mess!

Managed to get in by reseting the password in the DB via phpmyadmin - so logged into manager but cant edit any pages as they just throw a black white page??? e.g. http://example.com/manager/?a=30&id=21 trying to edit resource 21 - a pure blank white page... nothing... nadda... ?

Looks like every resource has the same ID ?? Tried clearing cache and saw this:

Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 127
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 5
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 2
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 188

etc... for all resources...

????

OK, updated all addons, cleared cache manually via FTP clearing core/cache folder and after a few gos all looks ok once more...

The upgrade is supposed to set all the resource 'uri' fields, but sometimes it doesn't. If they're blank, they're all "duplicates," hence the warning.

For good measure, I would turn off friendly URLS in System -> System Settings, then turn them back on, which should make sure they're all set.

Quote from: BobRay at Jul 03, 2014, 11:03 AM

The upgrade is supposed to set all the resource 'uri' fields, but sometimes it doesn't. If they're blank, they're all "duplicates," hence the warning.

For good measure, I would turn off friendly URLS in System -> System Settings, then turn them back on, which should make sure they're all set.

Thanks bob - got rid of that odd kink now yep. One issue remains though - one of the TVs I have is not rendereding... I have a TV with text as the input on all pages which is used in the template to output inside a <p> - it's not doing it though... looking in the manager the TV has the data pulled from the DB but when I view the frontend page it does not render the data??? Any ideas??

Bob - dont worry fixed it... seems this TV had been applied to a resource group during the upgrade... lots of odd things happened in this upgrade - worrying really!