I love the page defaults feature, but I believe that currently it does not allow you to set defaults for additional content fields that you include in your template using the {content block = "foo"} tag.
I recently designed a site with an additional column containing mood-setting images. I created a new content block called mood_images, which every page has. But of course for any new pages, this defaults to empty. It would be nice to have a default of pretty images that the user could change later if they feel the pages are looking too similar.
I am sure it would have many other uses too!
Page Defaults extended to additional content blocks
-
calguy1000
- Support Guru
- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: Page Defaults extended to additional content blocks
That's because each template can have any number of content blocks all named differently.
it'd be better to do {content block='blah' defaulttext='blahblahblahblah'}
it'd be better to do {content block='blah' defaulttext='blahblahblahblah'}
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
-
Short
Re: Page Defaults extended to additional content blocks
I think I get it. (Bit slow!)
But what if you want a large amount of default content in the block? Could the content tag's block parameter accept a global content block name?
Or maybe there could be the facility to create special "default" pages, in the main pages section. That way you could assign them to templates...
However, the more I type, the more this feels like feature-creep...and a drift away from "simple". I'll go with your idea!
But what if you want a large amount of default content in the block? Could the content tag's block parameter accept a global content block name?
Or maybe there could be the facility to create special "default" pages, in the main pages section. That way you could assign them to templates...
However, the more I type, the more this feels like feature-creep...and a drift away from "simple". I'll go with your idea!
