Quote from: Pandy06269 at Nov 12, 2008, 07:59 PM
To all the MODx developers who know the structure of the new "core" and Revolution :-
Where should I begin looking (in the PHP code) to try and debug this issue? I was going to raise a bug in Jira, but afraid of it being closed as it seems to be working in opengeek’s case.
I’d like to lend a hand in tracking this down as it is hindering a project I’m working on, but I’m very lost when it comes to the layout of Revolution!
As a side question, do you know when you expect to release alpha-6? I cannot install TinyMCE as apparently the packages on the wtf have been re-designed to work with alpha-6 onwards, and I don’t know enough about Revolution (yet!) to install it manually.
Thanks,
Andy
Andy,
Jason and I talked about your issue today, and we just patched the SVN version with a fix for it. It *should* (in theory) work now. If you could try it out, that’d be great.
To give you an idea of what we fixed, if you go to core/model/modx/modtemplatevar.class.php (the class for the modTemplateVar object), and look at the functions ’renderOutput’ and ’renderInput’, you’ll notice that there was something like this:
$outputRenderPath = MODX_PROCESSORS_PATH.'element/tv/renders/'.$this->xpdo->context->get('key').'/output/';
That would find the render template for the TV, based upon the context. However, what it wasn’t doing is that if you wanted a TV in a context that’s not web/mgr, and that didn’t have custom renderers already packaged in, then it wouldn’t load the right file.
So, we patched it with this:
$outputRenderPath = MODX_PROCESSORS_PATH.'element/tv/renders/'.$this->xpdo->context->get('key').'/output/';
if (!file_exists($outputRenderPath) || !is_dir($outputRenderPath)) {
$outputRenderPath = MODX_PROCESSORS_PATH.'element/tv/renders/web/output/';
}
Now it will default to the web context should no overrides be found, which should fix your issue. Thanks!
P.S. We are shooting for a release of alpha-6 in the next week or so. We’re trying to nail down an issue with packaging and the uninstallation of packages that contain pre-existing objects. As soon as we finish that, we should be near 100% ready for alpha-6, and then the next step onward should be beta-1.
MODX Staff
