empty Template outputs content by default

1,624 Posts

cipa Reply #1, 16 years, 5 months ago

Hi,

It seems that a page with the (empty) template will output the content. I like this but I want to make sure it’s a feature and not a bug.

Thank You

Responsive CSS Grid: cipalabs.com/projects/metal/
Blog: MODX Tutorials & Articles

153 Posts

oori Reply #2, 16 years, 5 months ago

yes, empty template would just outputs the content.
otherwise, you’d need to have your own empty template (with [[*content]]) for that.. and the built-in empty template would have been quite meaningless..

☆ A M B ☆
24,524 Posts

sottwell Reply #3, 16 years, 5 months ago

The parser gets the document from the database, and checks its template. If it has no template, then the parser just pretends that it’s using a template with only the [*content*] tags. If it does have a template, then the parser goes to the database to get the template and uses that.

if (!$this->documentObject['template'])
    $this->documentContent= "[*content*]"; // use blank template
...

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

1,624 Posts

cipa Reply #4, 16 years, 5 months ago

So it’s a feature

I use it in Revo to generate the header, menu and footer for the SMF install so I was just worried that it might change in the future.

Thank you

Responsive CSS Grid: cipalabs.com/projects/metal/
Blog: MODX Tutorials & Articles

MODX Staff
12,272 Posts

Ryan Thrash Reply #5, 16 years, 5 months ago

This is a changing behavior from Evo ... I like it better this way as well. I’m not sure how to address it going forward but we should put a stake in the ground and make a policy. It does however bring to mind the thought of having an option on "blank" template pages to have them act as snippets and parse the content of [[*content]]. Or maybe having a "Processor" resource type which can be used for Ajax calls, etc. (What we currently do now by just including a snippet on a blank template for Ajax calls, etc.) Hmmm.... Thoughts?

Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

1,624 Posts

cipa Reply #6, 16 years, 5 months ago

I’m ok with (empty).

I don’t currently see a reason for a Processor resource type. If you don’t like empty you can always create your own template called Processor, Ajax etc.

For ajax websites I usually set up a folder named ajax and I keep all my resources in there. Another way to do it is to prefix your documents with ajax so the generated alias is something like ajax-bla-bla.

Responsive CSS Grid: cipalabs.com/projects/metal/
Blog: MODX Tutorials & Articles

153 Posts

oori Reply #7, 16 years, 5 months ago

Quote from: rthrash at Apr 24, 2010, 05:43 AM

Or maybe having a "Processor" resource type which can be used for Ajax calls, etc. (What we currently do now by just including a snippet on a blank template for Ajax calls, etc.) Hmmm.... Thoughts?

You can make a static resource pointing at your connector that would actually become a "Processor resource type" as you suggested.

You can also not make any resource and just ajax call your processors (via a connector) directly.
This means you’re losing changeable friendly-url (would you really need it on a connector?) and ACL control via manager. but normally you’d anyway check permissions in your connector/processor (hasPermission).

jquery example (a processor that sends an activation to a user)
(the important things here are:
a. connector.php -or- static resource url
b. action path
c. ,json
all the rest is up to your processor

$.post('/assets/components/forces/connector.php'
	,{	action: 'web/services/sendActivation'
		,memberId: memberId
		,ctx: 'web'
	}
	,function(r){
		if (r.success == false) { alert(r.message); }
		else { alert("ok");	}
	}
	,'json'
);

MODX Staff
10,725 Posts

opengeek Reply #8, 16 years, 5 months ago

Quote from: rthrash at Apr 24, 2010, 05:43 AM

This is a changing behavior from Evo ... I like it better this way as well. I’m not sure how to address it going forward but we should put a stake in the ground and make a policy. It does however bring to mind the thought of having an option on "blank" template pages to have them act as snippets and parse the content of [[*content]]. Or maybe having a "Processor" resource type which can be used for Ajax calls, etc. (What we currently do now by just including a snippet on a blank template for Ajax calls, etc.) Hmmm.... Thoughts?

I think you are mistaken; Evo and Revo (should) behave exactly the same in this regards...AFAIK this is totally a non-issue. If Evo no longer parses the content when using the built-in "empty" template, then that is a bug.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

☆ A M B ☆
24,524 Posts

sottwell Reply #9, 16 years, 5 months ago

It parses the content on both the default "empty" template and a blank template.

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

MODX Staff
10,725 Posts

opengeek Reply #10, 16 years, 5 months ago

Quote from: sottwell at Apr 26, 2010, 10:39 AM

It parses the content on both the default "empty" template and a blank template.

IMO, a "blank" template, void of any content is an error; it should not be allowed to exist in Evo or Revo.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek