> I think you got what I meant about the approved items. However since you
> keep referring to them as active, that leads me to another
> question. Are you
> using the active and archived bits for approval purposes? For instance, an
Yes.
> But back to my original question. When a user logs into the site with the
> query string designmode=1, they have access to the containers and the
> container rules. I don't want our users to be able to remove the filtering
> rule I'm going to write. If it's added in the list of active rules, then I
> assume that the authed user has the ability to remove it. I don't
> want them
Simple - don't use designmode. :) You can still use security and have your
own checks in. It sounds like you want:
Some admins can edit containers, but not remove my ActiveOnly rule.
Higher admins can do whatever they want.
So, for the first group, when they logon, use your own editing tools.
For the high admins, use designmode. I've done that before for clients who
didn't like the complexity of the container editor.
By the way, this is a tiny bit off topic - but did you know that the
container tags takes these two attributes:
lDefaultRuleTypeIDs (list, optional, default = Basic Schedule Rule) -
List
of type IDs of new rule objects that will populate the container by default.
lAvailableRuleTypeIDs (list, optional, default = all publishing rules)
- A
list of rule type IDs that are available for selection in the container
editor.
Of course, this won't help you since the default rule thing will (I believe)
allow you to remove the rule, and you want it to stick, but, I thought you
(and others) may find this interesting anyway.
> It seems best to implement this as a publishing rule although I can see
> implementing this filtering through the display handler for each content
> type. It's not desirable (or practical) to have to edit this for every
> display handler though.
Right, that's why I said you should edit your rules instead, that would be a
lot easier.
=======================================================================
Raymond Camden, Principal Spectra Compliance Engineer for Macromedia
Email : [EMAIL PROTECTED]
ICQ UIN : 3679482
"My ally is the Force, and a powerful ally it is." - Yoda
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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.
