On Wed, Jan 13, 2010 at 8:38 AM, Peter Degen-Portnoy <[email protected] > wrote:
> 1. Add a part called ³No_<SNIPPET>² to the page where the targeted snippet > should NOT be displayed > I've done this kind of thing quite a bit, but I'm turning against it. The problem for me is that the "magic" page parts seem to proliferate, and soon I need an encyclopedia of things that my content editors have to remember, spell correctly, and then ignore (or, worse, format properly). At this point I lean toward a site-specific extension that just knows what the major page options are, and presents them as checkboxes (or select boxes, or text input), clearly labeled for the editors. It's not reusable from site to site, but on the bright side, this kind of extension is really easy to write. 2. Extend the snippet tag to have a new attribute ³suppressable² so that a > snippet that is flagged as ³suppressable => true² has a check box generated > & displayed on the /admin/page/x/edit view when the layout with that > snippet > is selected. We can serialize the set of check boxes to support future > expandability. > I may be wrong, but I don't think there's an easy way for the code to figure out which layouts contain which snippets. You might need an admin tool for manually declaring which checkboxes apply to which layout. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
