We have a rule that does just this. Previously our editors may put any type
in a container with any method and it would really screw the page up. We
hacked the default rule together to limit type and method by default and
then made this rule the only rule per container.
Russell Brown
Internet Application Developer
Freeserve.com Plc, PO Box 452, Leeds LS2 7EY
-----Original Message-----
From: Tristan Roddis [mailto:[EMAIL PROTECTED]]
Sent: 17 August 2001 13:10
To: Spectra-Talk
Subject: Constraining types and methods to use in a container?
Does anybody have any good ideas for how I can constrain what object types
and methods a site administrator can drop in to a container?
My current best guess is a) create a publishing rule that has an edit
method that only allows a certain type or types to display in the
selection (read from where? set this in the request space on the page that
has the container?) followed by b) set the lAvailableRuleTypeIDs and
lDefaultRuleTypeIDS parameters of the relevant cfa_container to force the
application of this rule.
However, I'd be very grateful if anyone knows of either an easier way to
do this or has edit/execute code for a rule that will work similarly to
that mentioned above to save me writing it from scratch.
Thanks,
-T.
[EMAIL PROTECTED] http://www.roddis.org
................................oOo..................................
"GNU Graphics" http://www.gimp.org
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
