I thought about the closeness of parents/parent but I think it will work
ok. But I think definitely group has to go if we want to make it a true
page variable. Unfortunately this will break templates with {+group}. I'll
put a site.deprecate flag in, but it will be after the fact unfortunately.
I should leave group in for awhile to give people a chance to catch it...Cheers, Dan On Tue, May 26, 2015 at 12:55 AM Tiffany Grenier <[email protected]> wrote: > Yes for the group thing, I didn't want to get rid of it, as I am using > both group and parents. And about the grandaparents, thank you for having > spotted the lack of logic. I have to confess it was untested code. > As you imagined, I have pages with a given logic in their hierarchy, but > for which I ignore the depth of the page tree... And I can't do {p{ p0 - 1 > }}... > > The parents and parent seem a bit close one to the other, and could create > stupid typos. Why not go for ancestors and parent, if you anyway consider > renaming group? > > Cheers, > Tiffany > > -- > You received this message because you are subscribed to the Google Groups > "BoltWire" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/boltwire. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/boltwire. For more options, visit https://groups.google.com/d/optout.
