I've never seen this issue before. Fresh install on a new host (MivaMerchant) that I'm not too familiar with. They have an older plesk interface setup, so I don't know how much control over php.ini I have.
I'm looking to create a new context and the manager page displaying all contexts says action_err_ns where the table should be. then when I hit the add button I get the same error.
Help?
Sorry, I forgot to include some details:
MODx 2.2.7
PHP 5.3.3
MySQL 5.1.69
-
☆ A M B ☆
- 3,141 Posts
What's the link in the url bar when you get that error?
action_err_ns means "action not set" which sounds like it didn't get the ?a=<number here> parameter, or the action it points to doesn't exist.
Did you do a manual install or use some sort of one-click install offered by the host?
Are you getting any errors in the MODX error log, or the server error log?
I unzipped the .zip file on my local machine and uploaded the whole structure to the hosting server. Traditional version.
I get the same popup error when I use the Manager->clear cache menu item, and also when I pull up the Reports->System Info.
Thanks for the help Mark.
Still looking for any good ideas on this one.
I have the network tab open and nothing is throwing a 404 or any other error. I've tried a few things but nothing is really shedding any light. Any ideas?
Did you run setup on the host after moving the files? That's necessary to straighten out all the paths.
Thanks for the kind words. I'm assuming that you ran setup, though you didn't really answer that question.
I can see where the code in modconnectorrequest.class.php could use some better sanity checking. Unfortunately, the action value is coming from somewhere else and I don't know where.
Have you tried deleting all files in the core/cache directory and clearing your browser cache and cookies? A leftover cookie can cause all kinds of weirdness in the Manager.
Sorry about that. This was a typical install, upload, browse to /setup, run the checks, got the green light and everything installed correctly.
I just manually deleted everything in the /core/cache folder and popped it open in firefox (never browsed to it before, so no cookies previously existed). Same issues, it's gotta be server side issues...