opengeek created Redmine issue ID 9165

modError::hasError() returns true automatically after loading modError via getService calls like:

$modx->getService('error', 'error.modError');

This is because getService passes the second parameter to modError's constructor as an empty array, instead of an empty string. Since hasError checks for $this->message != '', and array() != '', many processors fail with a general error but with no error messages.

Loading it like this gets around the problem for now:

$modx->getService('error', 'error.modError', '', '');