On this page some remarks regarding MODx revolution can be found. See the sidebar for some Revolution links, see the xPDO page for information regarding database interaction and see the page regarding MODx Revolution packages, for a packages overview.
This website is now finaly on MODx revolution.
There are some disadvantages to MODx revolution:
But it's the way to go - because of the many positive aspects:
See below for some revolution remarks - things I found out during the migration/development work.
Normally I develop new sites on my own pc (using the newest version of XAMPP). Hopefully at some day I would want to copy the site to the production environment.
According to some discussions in the MODx forums (mostly Bob Ray's comments) the right approach is the following:
See below for some information about error messages and debugging in MODx Revolution. I hope this information is correct, but I can not guarantee it; checking wouldn't hurt...
The MODx Revolution errorlog can be found in the MODx manager menu: Reports -> Error Log.
Or in the file core/cache/logs/error.log
Writing errors to the error log can be done using a statement like:
Lexicon is used in this example to make sure that the standard "permission denied" message will be used for the language selected. If only one language needs to be supported and error messages do not need to be standardised, a normal string could be used.
Debugging information could be written to the error log using a statement like the following:
$modx->log(modX::LOG_LEVEL_DEBUG, "this is a debug text");
To get the logging of the errors and debugging information working the following statement could be used:
For error reporting in MODx between connectors and processors MODx uses a different kind of error handling, handled by the class modError() in core/model/modx/error/moderror.class.php.
Methods of modError: