Answered Setup 404

Revo 2.4.2

Two issues:

1. Logging into the Manager works ok but as soon as I try to navigate to any page or perform any action I get this, https://db.tt/ltsmzuoO. Even if I logout I'm not redirected to the login page, instead it just loads whatever page I'm currently on.

2. So I tried upgrading to 2.4.3. After moving all the 2.4.3 files into place I ran the setup only to find it throwing a 404.

It was working fine yesterday, now...

Could this be a server issue and not a MODX thing?

The site was working fine under 2.4.2 now it's in limbo. All the config paths are correct and I tried clearing core/cache. I don’t know what else to try.

Ideas?

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

I did. No love.

Try upgrading again, only use the install.php script here https://github.com/sottwell/installer

It's primarily intended for new installation, but it does upgrades as well.

Check your database to make sure you don't have any corrupted tables.

Thanks Susan.

Oddly enough even this file throws a 404. Houston, we have...

I believe the tables are ok. I did a MySQL dump of the "problematic" db and am running it locally without any issue whatsoever. Whatever the problem it seems unlikely it's the db.

I don't think it's the htaccess either.

I can't help but wonder if the host made some recent server changes that threw a wrench in the works. That's a possibility, isn't it?

Check your files to make sure that the setup directory did get uploaded in the right place. The only time that script throws a 404 is if the files actually don't get uploaded. The worst you'll get if it's just a matter of server changes is the setup will warn that it can't find the core where it's supposed to be.

Everything is where it should be.

I'm stumped.

Disable all plugins - if any

Look at the network tab in Chrome or Firefox's dev. tools (Ctrl-shift-i). See what file request gets the 404.

I wonder if it's possible that some kind of server configuration has stopped using index.php as the server's primary index page? And/or perhaps mod_rewrite has been disabled?