The following goes for 1.5.1. It might address what you're asking.
If you add the metadata "hidden" to an object type the object won't appear
in the object viewer. Alternately, you can modify the objectfinder so that
when it is used in the publishing rules it looks for some specific metadata
word and only displays those objects.
You can add metadata from the normal "Types" interface. It's accessed by
one of the 4 icons on the top right of that interface. There are actually 3
files you modify to change the objectfinder... the tag itself and two
includes (they start with _). I can't remember the exact locations. What I
did was to make copies of these includes and placed them in my
application... then I modified the objectfinder as needed, including adding
logic that looked for the key "request.cfa.spectrawebtop". If that key
didn't exist, I used my customized versions of the includes because that
meant the objectfinder was being called from within my application (i.e.
publishing rules). Doing it this way meant that the webtop would still
operate the normal way.
The same thing goes for methods.... When you create a new method there's a
checkbox for soemthing like "mark for display". If you do this, then
Spectra inserts a metadata word that the Basic Scheudle publishing rule uses
to show that method in the drop down box.
-----Original Message-----
From: Tristan Roddis
To: Spectra-Talk
Sent: 8/17/01 8:10 AM
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.
