These are the only two that could do it, and they seem unlikely:
public_html/core/model/modx/processors/security/forms/set/import.php: $template = $modx->getObject('modTemplate',array(
public_html/core/model/modx/processors/resource/create.class.php: $this->template = $this->modx->getObject('modTemplate',$templateKey);
The first would be called very seldom.
The second could be it if somebody is calling runProcessor('resource/create') with the $templateKey field set to an array using 'name' => 'something', but $templateKey would normally be just an integer, so I think that's unlikely too. It would be very difficult to search for since $templateKey could be named anything on the sending end and the processor in the runProcessor() call could be dynamic (e.g, runProcessor($processorPath) ).
You would have to grep 'resource/create', then load all the files, view all the instances, and look at how the fields for the second argument to runProcessor were set.
It's too bad that the error in the log doesn't include the call stack. I think if you turn on PHP error reporting and set the level to:
ini_set('display_errors', 1);
error_reporting(E_ALL);
// or
error_reporting(E_ALL ^ E_NOTICE);
You may get things to crash when it happens and you'll see a call stack that should tell you exactly where the error is coming from.
[ed. note: BobRay last edited this post 12 years, 6 months ago.]
