In short, yes.

Since version 1, the links template parser and other config modules, have been using cascaded inheretance (for lack of a better term).

The earliest version was if you added in a category footer/header those footers/headers would be used on that category, and any category below them.

This was expanded to include all fields (if I'm not mistaken), so that category specific data could be passed down and inhereted. This included meta tags, and all the other stuff. This portion of links has changed greatly through the various versions from 1.x to 2.x

Also, the templates use a .tplinfo file to point to where the parser should look if it can't find the requested file. So, in the local directory, the .tplinfo file would be:

{
inheritance => '../default'
}

This is a bit different, in that you can explicitly force the templates to load from a different area if you need to, or expand the search path to include files in other areas. I'm not sure if the field can be more than one other directory, but sometimes that is enough to do what you want, if you want to do fancy things.

Back to the issue:

So, if you create a field "banner code" every sub category would inheret the banner code from the category above, unless a banner code was specifically set in that subcategory.

If you create a Show_Title, the "Show_Title" will appear in all pages below the category that has it.

At least that is how it _should_ work ;)


PUGDOG� Enterprises, Inc.

The best way to contact me is to NOT use Email.
Please leave a PM here.