[ic] Location specific injected global code - or DEV setting?

[Kevin Walsh]

"Paul Jordan" <paul at gishnetwork.com> wrote:
> I was wondering how feasible it would be to have VENDROOT code be included
> in specific locations in all sub catalogs. First, for example, I'd be
> interested in including *any* catalog.cfg style directives/text in
> interchange.cfg. Possibly like:
> 
> CatalogCfgPrepend * <<EOS
> 
> # DEV account login
> UserDB    projects_access  user_field   username
> UserDB    projects_access  database     projects_access
> UserDB    projects_access  time_field   none
> UserDB    projects_access  crypt        0
> EOS
> 
> Notice the * as in a possible:
> 
> CatalogCfgPrepend catalogfoo catalogbar <<EOS
> EOS
> 
Have you considered the ConfigAllBefore global directive,
which defaults to catalog_before.cfg?

That file would cover all websites under the configured Interchange
instance, although you could probably restrict to specific websites
using an "ifdef", along with some sort of website list regex.

I'm thinking here of separate websites, configured with Catalog.
You mentioned SubCatalogs.  SubCatalogs will inherit settings from
their master Catalog, so master settings for hash-type directives
should be "prepended" already.

> 
> Also, in some global VEDROOT way, could it be possible to include code
> html/itl prepended into specific template variables?
> 
> Possibly like
> 
> TemplatePrepend LEFTONLY_TOP <<EOS
> 
> 	[if !scratch active][bounce getaccess][/if]
> 
> EOS
> 
Again, perhaps you could define (in the catalog_before.cfg config)
a LEFTONLY_TOP_PREPEND variable, and then use __LEFTONLY_TOP_PREPEND__
in your LEFTONLY_TOP definition.

-- 
   _/   _/  _/_/_/_/  _/    _/  _/_/_/  _/    _/
  _/_/_/   _/_/      _/    _/    _/    _/_/  _/   K e v i n   W a l s h
 _/ _/    _/          _/ _/     _/    _/  _/_/    kevin at cursor.biz
_/   _/  _/_/_/_/      _/    _/_/_/  _/    _/