Hey guys,
I was just wondering something about the way Radiant deals with page
parts.
If I create a new page, wouldn’t it be nice if I could have it
inherit the page above its parts? What I mean is, a project I am
working on now has a solid 50 or so pages… the way this site is
setup, we have 5 parts per page… going through, 1 by 1 is awfully
painful.
I kinda thought that’s what the “inherit” option was for in the
Layout drop-down but it doesn’t seem to do this behavior.
Thanks guys,
–
Travis B.
[email protected]
Could someone quench my curiosity and explain the format that would
require
5 page parts (besides maybe for a custom extension)? I’m not sure I
fully
understand their usefullness and feel like I’m missing out.
Thanks everyone.
On 7/26/07 12:55 PM, “Travis B.” [email protected] wrote:
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
–
Kyle Daigle
DigitalWorkbox
[email protected]
C: 860.324.8173
This is possible already. In your layout call your part like this:
<r:content part="sidebar" inherit="true" contextual="false"/>
I do it a good deal myself.
-James
We’re using them for 2 primary reasons.
- The obvious “body” and “sidebar”
- For some SEO stuff… custom, per page meta keywords, footers etc…
There could be other ways of doing this but this works incredibly
well and have found it to be the best way our client can understand
where to go to edit each element ie. keeps the body and sidebar areas
pretty lean and less chance of them messing shit up 
Cheers,
–
Travis B.
[email protected]
I don’t know about five, but with inheritance I suppose you could get
to that point. I use two to separate main content from contextual
sidebar material. I suppose if you have more extensive regions that
you needed to have available for customization you could get to a
fair number of page parts.
-James
Most excellent. I must have missed that tag option.
Thanks,
–
Travis B.
[email protected]
I accomplish most of this with snippets, but I guess in terms of having
clients editing the page it would make more sense to move them into page
parts.
Thanks! I’d be interested in hear however anyone else is using them.
On 7/26/07 1:05 PM, “Travis B.” [email protected] wrote:
Cheers,
On 26-Jul-07, at 1:57 PM, Kyle Daigle wrote:
On 7/26/07 12:55 PM, “Travis B.” [email protected] wrote:
painful.
–
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
–
Kyle Daigle
DigitalWorkbox
[email protected]
C: 860.324.8173
Ya, on a small site I would use snippets as well, but we have one
client in particular who’s site has 50 some pages all with per custom
footers and keywords… creating 100 different snippets sounds like a
bit of a headache to manage
Cheers,
–
Travis B.
[email protected]
In a site I’m working on, I have a page that displays a list of
football teams.
Each team is a hidden child of the page “Teams”.
In the Teams page i loop through all its children and I display :
- with a h2 the team name (title of the page),
- with a h3 the short-description (page part called description),
- with a ‘p’ the story (page part called story)
- with another ‘p’ the team players (page part called players)
I used DefaultPageParts extension for the Team page…each time my
client click on the add-child button, he has a new page with the 4
default page parts created.
Il giorno 26/lug/07, alle ore 21:57, Kyle Daigle ha scritto:
Kyle Daigle
DigitalWorkbox
[email protected]
C: 860.324.8173
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Andrea F.
[email protected]
http://bigchieflabs.com/blog/
http://think.bigchief.it