I have done two 2.4 upgrades this week and on one I am unable to login as manager. Has anyone else encountered this problem or better still can suggest a solution?
Give a man the answer, and he’ll only have a temporary solution. Teach him the principles that led you to that answer, and he will be able to create his own solutions in the future.
-
☆ A M B ☆
- 1,780 Posts
Did you attempt another upgrade (reinstall) with new files?
What was your process for updating MODX? Did you SSH, FTP, or use the server's file manager to upload a 2.4.zip file? Or did you use an installer script such as Softaculous to update?
Does the front end work? (this answer would tell us if you may have overwritten the database accidentally). Can you log in as an editor or another user?
I used the same upgrade files on another installation with no problem. The upgrade process was FTP. The front end appeared to work properly but I am unable to login as Admin or editor.
Give a man the answer, and he’ll only have a temporary solution. Teach him the principles that led you to that answer, and he will be able to create his own solutions in the future.
-
☆ A M B ☆
- 427 Posts
Try looking in the logs at the root of the site and down in the core/cache/logs folder.
Try ftp /ssh into the site and remove everything in the core/cache folder. You might also have to clear your browser cache - but not usually.
After the cache is cleared try logging in again. If it doesn't work. Pull a fresh download and reupload it after it is extracted on your system and rerun setup.
Using FTP to transfer the files individually often leads to missing or corrupted files.
You might also want to check this out:
http://modx.com/extras/package/upgrademodx.
UPDATE: I've tried these suggestions and so far no luck, Ver 2.6 works on the site. I've used the same download on two other sites with no problem, so I don't think missing or corrupted files are the problem. Cache has been cleared before and after upgrade attempts. Will post progress if, no, when I'm successful. Thanks to all for your suggestions.
Give a man the answer, and he’ll only have a temporary solution. Teach him the principles that led you to that answer, and he will be able to create his own solutions in the future.
-
☆ A M B ☆
- 1,780 Posts
Please accept the suggestion to download a NEW MODX.zip file and try to reinstall. Do not FTP unpacked files. SSH or use the file manager or unzip script on your server control panel.
Just because files worked before does not mean they are working for this installation. Save yourself a ton of time and just get new files. I can't even tell you how many hours I've wasted when all it took was fresh files. Even when I knew the same files worked previously.
As a result, I haven't FTP'd MODX installs or updates in over 6 years. It's not reliable. I had to learn the hard way but you don't have to.
I feel like the documentation need a big fat NO FTP graphic with a red circle and slash. Sometimes it's fine, others it's not. Best not to even bother.
I'd love for you to try the UpgradeMODX packages. It's new, but I've used it to upgrade a number of sites. It lets you upgrade MODX from inside the Manager with a few clicks. It will download and extract brand-new files for you.
I recently used it to upgrade a MODX 2.0.3 site (in steps) to MODX 2.4.0. It was a breeze, and the new site worked perfectly right away.
UpgradeMODX is available in Package Manager.
Having the same problem. Upgraded from 2.3.5. The login box shows a red "1" right above "Username". I also tried resetting the password, but that didn't work either.
This is the 3rd site I have upgraded to 2.4, but the first time I couldn't log in. Tried wiping the whole upgraded site and re-upgrading it again, but same symptom.
One difference I noticed on this site compared to the others is it seems to have a lot more connectors folders/files for some reason. Not sure why since the plugins/snippet list is mostly similar between these sites.
[ed. note: pixelstuff last edited this post 11 years, 1 month ago.]
The 1 suggests that some plugin is crashing. If you go into the modx_system_settings table in the DB and set the 'debug' setting to -1 (then manually delete all files in the core/cache directory), you may see an error message that will help you figure out what's happening.
