Someone else may have more knowledge on the specific errors you are getting, but the fact that you were hacked could mean any number of things with the existing files on your site. They could have incorrect permissions, they could have been modified, some could be completely missing, etc.
A couple of brute force tactics to try (again, assuming no one else with more knowledge on the specific error chimes in):
1) Running an upgrade to hopefully reset perms, etc
If the "setup" directory has already been deleted, then snag a new zip file containing the installer for whatever version of MODx you are running, unzip the whole thing and transfer *only* the setup folder to one of the affected sites.
Once the setup folder is loaded, try browsing to
http://yoursite.com/setup and see if the installer fires up. If so, select the "upgrade" option and run through all of the screens. If it completes successfully, try browsing to the site home page and see if you still get the errors. I expect one of three scenarios from this "fix" -
a. Installer fires up, completes successfully, and everything magically works (yay!)
b. Installer fires up, completes successfully, but does NOT fix the problem
c. Installer totally freaks out when you try to run it and spits errors all over the place
2) If you get anything other than scenario "a", then try this export/import/new installation method:
If you let the installer delete the "setup" directory in the first test, then you’ll need to copy it back again. After you have that back in place, you’ll need to access the MODx database with, hopefully, something easy like phpMyAdmin. On my sites, I have one of those nice "cpanel" things I can access and fire up phpMyAdmin from there. Hopefully you can do that, or have *some* way of accessing the database. If you can, then you need to run an EXPORT of the MODx database and save the export file to your local workstation. Be sure to note the exact name of the database, as well as the table prefix and name of the database "user" that MODx will be using for access.
The next step is kind of scary, so you’ll want to be extra mega confident that you have good, usable export before proceeding. It sounds like multiple sites are affected, so I’d pick the least valuable of the bunch as your first one to try this on. In phpMyAdmin (or whatever your DB admin poison is), you’ll now what to DROP ALL of the tables in the MODx database. After dropping the tables, run the installer and select the New Installation option this time. Make sure to input the same database name, database user, and table prefix as before (should have been noted above).
If the installer completes successfully, you’ll now want to DROP all tables in the database again, then perform an IMPORT and use the file you saved from your EXPORT earlier. At this point, you should have a pretty fresh installation with a freshly imported copy of your database... and it’s time to test again. So browse to
http://yoursite.com and/or
http://yoursite.com/manager and see if your site fires up.
If *neither* of these options works for you, then let’s hang out for a bit and see if anyone else chimes in. Option #1 is totally safe, so there’s really no reason not to try it before waiting for more advice. Option #2 is a little more hacky and my yet to be listed option #3 is even more hacky. So, try #1. If it works, then high five. If not, you can try #2 or wait for others to chime in. If you try #2 and it still doesn’t work and no one else has any better ideas, then hit me up and I’ll present the super secret option #3.
Thanks!
Swill
