DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43243>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43243


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




------- Additional Comments From [EMAIL PROTECTED]  2007-11-28 21:02 -------
I am seeing this in my production version. When copying the publications in
question, I have yet to be able to reproduce this under trunk. However, it is
something that needs to be looked at. In a templated publication that looks like
this: default -> mychangespub -> stylepub -> contentpub I see this in the
usecase-policies.xml file for contentpub:

<ac:usecase id="sitemanagement.copy">
<ac:role id="admin"/>
<ac:role id="edit"/>
</ac:usecase>

However, after a restart, editors can't copy due to permission problems. It
might very well be my setup or my old version. However, can someone explain how
the aggregate-fallback is supposed to work?

<authorizer type="usecase">
    <parameter name="configuration"
value="aggregate-fallback://config/access-control/usecase-policies.xml"/>
  </authorizer>




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to