At what System-Event is the template for Resource determined?

483 Posts

Fuzzical Logic Reply #1, 14 years, 1 month ago

I'm writing a plugin that performs "Template-Switching". The use-case for this is to make AJAX pages return data when it is retrieved via JavaScript and a full-page when it is navigated to. I already have the decision engine created, but I need to know when MODX determines which template it will use to render the document. I'm of the assumption that this happens after OnWebPageInit but before OnWebPagePrerender. Would I be correct in this assumption?

This question has been answered by BobRay. See the first response.

Website: Extended Dialog Development Blog: on Extended Dialog
Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".

discuss.answer

24,544 Posts

BobRay Reply #2, 14 years, 1 month ago

I did all the searches I could think of in the core code (even the 198 non-case-sensitive places where 'templatevarresource' appears and the 268 places where 'template' appears) and couldn't find where MODX actually gets the template.

This is from my book, but I doubt if it will help:

OnHandleRequest — Fires when any request for a resource is received in the front end.

OnWebPageInit — Fires after determination that the site is online and the requested resource is located.

OnLoadWebDocument — Fires after the requested resource is loaded, but before it is parsed.

OnParseDocument — Fires just before the MODX tags are processed.

OnWebPagePrerender — Fires just before a completed web page in the front end is sent to the browser, after all tags have been processed.

The only thing I can think of is to put $modx->resource->set('template', $id) in all of the above, one at a time, and see where it has any effect.

------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

483 Posts

Fuzzical Logic Reply #3, 14 years, 1 month ago

Thanks for looking for me! I wasn't expecting that! I was just hoping somebody knew the answer. Alright, I guess that is what I'm going to have to do. My spidey-sense just tingled though, so when I break my MODX (honestly, I'm lucky I haven't broken it before now), I now have a scapegoat. LOL! (just kidding)

On Dasher!....

Website: Extended Dialog Development Blog: on Extended Dialog
Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".

5,888 Posts

Bruno17 Reply #4, 14 years, 1 month ago

I'm writing a plugin that performs "Template-Switching". The use-case for this is to make AJAX pages return data when it is retrieved via JavaScript and a full-page when it is navigated to.

I like to use a snippet for switching between AJAX and full-page - output.
Just have the snippet-call ,which switches between ajax/full-page - chunk, on the template.

With this solution its also easy to cache one or both results.

-------------------------------

you can buy me a beer, if you like MIGX

http://webcmsolutions.de/migx.html

Thanks!

483 Posts

Fuzzical Logic Reply #5, 14 years, 1 month ago

Agreed. I'm just looking for a more efficient solution. (Plus, it will be unlikely that I can cache the results of these pages) If I use a Snippet (which I already do for my AJAX calls) and then switch, then I'm allowing extra processing to occur that doesn't need to occur. Otherwise, it would be an absolutely fine way to accomplish these results.

If I do it after the template is set, but before it is parsed, then I'm saving a lot of energy.

Just a theory, though. I have to see whether it tests true, but its been working so far...

Website: Extended Dialog Development Blog: on Extended Dialog
Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".

483 Posts

Fuzzical Logic Reply #6, 14 years, 1 month ago

Alrighty. Changing the properties during OnLoadWebDocument is the place. Everywhere else, there is either no object, or you get the same results

Website: Extended Dialog Development Blog: on Extended Dialog
Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".

24,544 Posts

BobRay Reply #7, 14 years, 1 month ago

Did you use $modx->resource(set, 'template'), or did you have to use something else?

------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

483 Posts

Fuzzical Logic Reply #8, 14 years, 1 month ago

set('template', x) worked perfectly. Allowed the parser to do what it needed to. Word of caution: You don't actually have access to $_REQUEST variables during this phase. Even if you've set them dynamically, they are not reset until after this event.

Additional note: Because of the above issue, if you set the template to a page that uses dynamic $_REQUESTs, you will get an infinite mirror renderring, which is awesome to see, but not so awesome to fix...

Website: Extended Dialog Development Blog: on Extended Dialog
Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".

483 Posts

Fuzzical Logic Reply #9, 14 years, 1 month ago

This event is incredibly hard to debug, as it does not accept echo, you cannot sent $output, etc. The parser hasn't run yet, so it overrides any output you try and send.

Website: Extended Dialog Development Blog: on Extended Dialog
Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".

Answered At what System-Event is the template for Resource determined?