Could not find action file at: controllers/default/index.php
Today I see this message in the manager while I can see the tree on the left. However When I press on a document nothings happens as well as when I choose anything from the top bar.
Any help would be appreciated
Thats because your cache was somehow emptied.
If anybody else encouters this problem. Just deleat the «core/cache» folder.
Just to be clear, don’t deleat the whole core folder.. just the cache folder in the core folder.
I have the same problem, how can I clear the case?
Manually delete all files in the core/cache directory (but not the cache directory itself).
If you have access to the Manager, you can also install and use the CacheClear extra.
As you go along, go ahead and make your own question, usually you can make them in the Revo or Evo sections, but don’t worry nothing gets by us 
Rather than pull up 5 year old threads that might not be your exact issue, its just a little quicker and easier to make a fresh one
Manually delete all files in the core/cache directory (but not the cache directory itself).
Could not find action file at: controllers/default/index.php
Could not find action file at: controllers/default/index.php
i don’t know what to do.
please help as soon as possible.
Thanks.
Don’t have a MODX.com account? Create one
In the time it takes to read this, you could start a new site with nothing to download or install.
Don’t Be That Guy
Be nice, respectful and patient. Inflammatory or inappropriate posts will get your post nuked and flood your life with bans and bad karma.
Thank the People that Help
Remember, this is an Open Source project and the volunteers here assist out of love for the project and a desire to help others.
Перенос сайта MODX Revolution и MODX Evolution на хостинг: проблемы и пути решения
При переносе сайта с локального компьютера на хостинг, разработанного на ModX Revolution периодически возникают проблемы. В основном они связаны с не отображением определенных частей сайта или сайта полностью. Разберем основные этапы переноса сайта:
define(‘MODX_CORE_PATH’, ‘ Z:/home/sitename /core/’);
define(‘MODX_CORE_PATH’, ‘ path /core/’);
$database_type = ‘mysql’;
$database_server = ‘ localhost ‘;
$database_user = ‘ root ‘;
$database_password = »;
$database_connection_charset = ‘utf8’;
$dbase = ‘ basename ‘;
$table_prefix = ‘modx_’;
$database_dsn = ‘mysql:host= localhost ;dbname= basename ;charset=utf8’;
$database_type = ‘mysql’;
$database_server = ‘ servername ‘;
$database_user = ‘ username ‘;
$database_password = ‘ basepassword ‘;
$database_connection_charset = ‘utf8’;
$dbase = ‘ basename ‘;
$table_prefix = ‘modx_’;
$database_dsn = ‘mysql:host= servername ;dbname= basename ;charset=utf8’;
Заменить пути и имя сайта выделенные красным цветом
$modx_core_path= ‘/path/to/modx_doc_root/core/’;
$modx_processors_path= ‘ /path/to/modx_doc_root/ core/model/modx/processors/’;
$modx_connectors_path= ‘ /path/to/modx_doc_root/ connectors/’;
$modx_manager_path= ‘ /path/to/modx_doc_root/ manager/’;
$modx_base_path= ‘ /path/to/modx_doc_root/ ‘;
$modx_assets_path= ‘ /path/to/modx_doc_root/assets/ ‘;
/* HOST (used for command-line PHP stuff) */
$http_host=’ yoursite.com ‘;
Если после авторизации в админке вы увидели похожую запись, удалите папку кеш в директории core:
Could not find action file at: /path/to/manager/controllers/default/welcome.php
Перенос сайта с локального помпьютера на сервер, разработанного на ModX Evolution осуществляется изменением всего лишь одного файла config.inc.php
$database_type = ‘mysql’;
$database_server = ‘localhost’;
$database_user = ‘root’;
$database_password = »;
$database_connection_charset = ‘utf8’;
$database_connection_method = ‘SET CHARACTER SET’;
$dbase = ‘`basename`’;
$table_prefix = ‘modx_’;
$database_type = ‘mysql’;
$database_server = ‘servername’;
$database_user = ‘username’;
$database_password = ‘basepassword’;
$database_connection_charset = ‘utf8’;
$database_connection_method = ‘SET CHARACTER SET’;
$dbase = ‘`basename`’;
$table_prefix = ‘modx_’;
Could not find action file: but with a twist
Modx Revolution 2.4.1, this happened on my local dev server a while back while I was synching the local db with the remote live db data. That is, updating the local to be the same as the remote.
Don’t read this too fast, note that the path is wrong: /default/aresource/update.php
I’ve grep’ed through core and manager to see if I could find any instance of ‘aresource’ but of course nothing appeared.
This error makes it impossible to work with my resource data in my local version, and I can’t figure out how to resolve it.
The live site is fine. I just tried updating the local db with the remote data, and the error still persists. Since that data is now in my local system, I have to assume the /aresource/ path error cannot possibly be in the live database, unless it can, somehow. And it’s not in any of the files of modx itself.
Also noteworthy is that there is no update.php file at all in either local or remote manager, just: update.class.php
I’ve cleared the core/cache repeatedly, made sure to give it 777 permissions, but nothing makes the error go away.
I guess I could nuke everything and reinstall, but given this issue might also hit the live site, I’d like to know how to resolve the issue without resorting to desperate measures.
Is that the ‘namespaces’ table? I don’t see anything in that one related to that path. Or is it somewhere else?
I also searched through the sql dump file and there’s no occurrence of ‘aresource’ in it, just to be on the safe side. So the system looking for a path that doesn’t appear to be in either the database of the physical files, which suggests a bug somewhere? [ed. note: lizardx last edited this post 5 years, 8 months ago.]
That’s it, but apparently the problem is not there. Is this happening for all Manager actions, or just specific ones?
You might also check the modx_actions table.
It happens when I try to view any resource/element from the left nav option list. I can’t see any other time it happens, unless I haven’t poked around manager options enough.
I checked those tables, and don’t see anything.
The questions I have would be: why is it adding the ‘a’ to /resource/ and why is it looking for a file that does not exist? update.php?
These seem like two separate issues.
I poked around a bit more, and found that I can edit Elements (chunks, snippets, templates) if I right click on the name in the left nav column and select the ‘edit’ option. If I try to edit a resource by right clicking the name and selecting ‘edit’, however, it says:
But if I click on them directly, the same ‘could not find action file’ message always appears for both resources/elements items.
Also note I’ve searched the entire dumped db sql file for ‘aresource’ and ‘update.php’ and those don’t appear in that file, or in any modx system file that I can find, which suggests that modx is constructing these file names out of something.
[ed. note: lizardx last edited this post 5 years, 8 months ago.]
Re ‘age’ of installation, it’s a modx revolution, I can’t remember when I installed it, was a few years ago. I wouldn’t call that ‘old’ myself. I forgot to mention, this is the advanced modx revolution.
Don’t know where the «aresource» is coming from, it should be «resource».
That’s the question I believe, so the answer is what is missing.
Same for the ‘update.php’ instead of update.class.php.
The browser cache was a good thing to remind users of, and me, so I cleared cache, and, even better, logged in with a browser I’d never logged into the manager before.
Same results. So the issue can’t be the browser cache since that browser had no cache of the manager, though it is a good guess.
Are there other locations in modx core or manager that might have cached files? the update.php seems like a dead giveaway that something cached or corrupted is being used when it shouldn’t be. As with the /aresource/ corruption.
Again, one of things I want to figure out is how to fix this in case this ever happens on the live site, if it does, I need to have it running very quickly, and since it clearly can happen, and has happened, what I need to figure out is how to fix it.
What we know so far:
2. The browser caches have been cleared, and a fresh browser has been used
3. The issue is only occurring on my local dev version
4. I’ve imported the live db sql several times to the local dev version, which means that the db tables are identical, except for the adjustment to the core path in the workspaces table required when moving it. Though there could be a table in there with a changed name left over in theory.
5. aresource and update.php do not occur in the actual files of core or anywhere else. Which does really suggest a caching issue, only as noted, the caches of browsers/modx have been cleared, repeatedly. Well, it does occur in the log data after the error happens, of course, but that’s it.
[ed. note: lizardx last edited this post 5 years, 8 months ago.]
I don’t think this will help you, but update.php is the legacy processor, which will be run if MODX can’t find update.class.php (which it wouldn’t because it’s looking in the wrong directory).
You might watch the Network tab in FF Chrome dev. mode (Ctrl-shift-i) to see if that gives you any clues about the steps leading up to the issue.
That’s helpful, so that narrows down the issue to the corrupted /aresource/ directory name alone. So there’s only that one issue.
To my eyes, it looks like the aresource is a constructed corruption, though that’s of courses only a guess, ie, something is appending the ‘a’ to ‘resource’.
Don’t have a MODX.com account? Create one
In the time it takes to read this, you could start a new site with nothing to download or install.
Don’t Be That Guy
Be nice, respectful and patient. Inflammatory or inappropriate posts will get your post nuked and flood your life with bans and bad karma.
Thank the People that Help
Remember, this is an Open Source project and the volunteers here assist out of love for the project and a desire to help others.
Answered Moving MODX site from local to server, can not log into manager
I built a modx site locally and am moving to a shared media temple grid. I’m using the most current version of MODX. I have followed the official documentation. http://rtfm.modx.com/revolution/2.x/administering-your-site/moving-your-site-to-a-new-server
I moved all my files, updated the config files with new paths and database info. I uploaded my database successfully with phpmyadmin. I didn’t think I needed to change my path (as described in «Update your database section»)at all, but perhaps thats the problem.
When I try to log-into my manager I get the following error:
Could not find action file at: /home/95094/domains/singleatlanta.com/html/manager/controllers/default/security/login.php
Any ideas whats going on?
This question has been answered by BobRay. See the first response.
This is what I do, and I always never have an issue.
I enter the live MODx Manager and chase out all sessions.
I manually annihilate the core/cache files, not the folder itself
I lastly upload my database, same db name structure and table prefix as the current new MODx site etc
I run /setup, and upgrade
@rrswans: You didn’t mention running setup. That will usually (but not always) straighten out the paths for you.
Delete all the files in the core/cache directory and clear your browser cache and cookies after running setup.
If that doesn’t work, it’s time to check the 4 config files:
core/config/config.inc.php
config.core.php (in the MODX root)
/manager/config.core.php
/connectors/config.core.php
@rrswans: You didn’t mention running setup. That will usually (but not always) straighten out the paths for you.
Delete all the files in the core/cache directory and clear your browser cache and cookies after running setup.
If that doesn’t work, it’s time to check the 4 config files:
core/config/config.inc.php
config.core.php (in the MODX root)
/manager/config.core.php
/connectors/config.core.php
If it can’t connect to the database, either the database info in the config file is wrong or the user whose DB credentials you put in the config file doesn’t have full rights to the database. Some hosts add a prefix to the database name. Check in PhpMyAdmin to see the true database name and make sure it matches the name in the config file.
Delete all the files in the core/cache directory and clear your browser cache and cookies after running setup.
Don’t have a MODX.com account? Create one
In the time it takes to read this, you could start a new site with nothing to download or install.
Don’t Be That Guy
Be nice, respectful and patient. Inflammatory or inappropriate posts will get your post nuked and flood your life with bans and bad karma.
Thank the People that Help
Remember, this is an Open Source project and the volunteers here assist out of love for the project and a desire to help others.
Answered Moving MODX site from local to server, can not log into manager
I built a modx site locally and am moving to a shared media temple grid. I’m using the most current version of MODX. I have followed the official documentation. http://rtfm.modx.com/revolution/2.x/administering-your-site/moving-your-site-to-a-new-server
I moved all my files, updated the config files with new paths and database info. I uploaded my database successfully with phpmyadmin. I didn’t think I needed to change my path (as described in «Update your database section»)at all, but perhaps thats the problem.
When I try to log-into my manager I get the following error:
Could not find action file at: /home/95094/domains/singleatlanta.com/html/manager/controllers/default/security/login.php
Any ideas whats going on?
This question has been answered by BobRay. See the first response.
This is what I do, and I always never have an issue.
I enter the live MODx Manager and chase out all sessions.
I manually annihilate the core/cache files, not the folder itself
I lastly upload my database, same db name structure and table prefix as the current new MODx site etc
I run /setup, and upgrade
@rrswans: You didn’t mention running setup. That will usually (but not always) straighten out the paths for you.
Delete all the files in the core/cache directory and clear your browser cache and cookies after running setup.
If that doesn’t work, it’s time to check the 4 config files:
core/config/config.inc.php
config.core.php (in the MODX root)
/manager/config.core.php
/connectors/config.core.php
@rrswans: You didn’t mention running setup. That will usually (but not always) straighten out the paths for you.
Delete all the files in the core/cache directory and clear your browser cache and cookies after running setup.
If that doesn’t work, it’s time to check the 4 config files:
core/config/config.inc.php
config.core.php (in the MODX root)
/manager/config.core.php
/connectors/config.core.php
If it can’t connect to the database, either the database info in the config file is wrong or the user whose DB credentials you put in the config file doesn’t have full rights to the database. Some hosts add a prefix to the database name. Check in PhpMyAdmin to see the true database name and make sure it matches the name in the config file.
Delete all the files in the core/cache directory and clear your browser cache and cookies after running setup.
Don’t have a MODX.com account? Create one
In the time it takes to read this, you could start a new site with nothing to download or install.
Don’t Be That Guy
Be nice, respectful and patient. Inflammatory or inappropriate posts will get your post nuked and flood your life with bans and bad karma.
Thank the People that Help
Remember, this is an Open Source project and the volunteers here assist out of love for the project and a desire to help others.