Hi Michael,<br><br>Then the permission dialog is "too generic"? I mean what sense makes the possibility to add/change permissions for Admin/Admin Role which have no effect? That's the reason I think the result may be a bit surprising for (especially new) users.<br>
<br>Thanks!<br>David<br><br><br><div class="gmail_quote">On Thu, Jun 5, 2008 at 9:57 AM, Michael Moossen <<a href="mailto:m.moossen@alkacon.com">m.moossen@alkacon.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi David!<br>
<br>
this is not a bug, it is the intended behavior.<br>
administrators are allowed to do everything, and all permission checks<br>
are ignored. this is important also to have in mind, when testing a new<br>
feature/configuration...<br>
<br>
Kind regards,<br>
Michael<br>
<br>
-------------------<br>
<br>
Alkacon Software GmbH - The OpenCms Experts<br>
<a href="http://www.alkacon.com" target="_blank">http://www.alkacon.com</a> - <a href="http://www.opencms.org" target="_blank">http://www.opencms.org</a><br>
<div class="Ih2E3d"><br>
<br>
David Trattnig wrote:<br>
> Hi Kay,<br>
><br>
> IMHO it breaks the "principle of least surprise". When I have the<br>
> possibility to disable direct publish on a folder for the Admin user and<br>
> it's published anyway it's a bit irritating in my opinion. The admin<br>
> could change the permission back anyway to have full rights on the<br>
> folder again. Bug?<br>
><br>
> Rgds<br>
> David<br>
><br>
><br>
> On Wed, Jun 4, 2008 at 1:34 PM, Schliemann, Kai<br>
</div><div><div></div><div class="Wj3C7c">> <<a href="mailto:K.Schliemann@comundus.com">K.Schliemann@comundus.com</a> <mailto:<a href="mailto:K.Schliemann@comundus.com">K.Schliemann@comundus.com</a>>> wrote:<br>
><br>
> Hi Christian,<br>
> hm, interesting. Maybe it is a problem with the administrator<br>
> (role). I can somehow recall that an Administrator can do all and<br>
> everything. No matter how the permissions are set.<br>
> I am not sure. Probably somebody else can confirm that?<br>
><br>
> HTH<br>
><br>
> Regards<br>
> Kai<br>
> ------------------------------------------------------------------------<br>
> *Von:* <a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a><br>
> <mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a>><br>
> [mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a><br>
> <mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a>>] *Im Auftrag von *Krenn,<br>
> Christian<br>
> *Gesendet:* Mittwoch, 4. Juni 2008 10:32<br>
><br>
> *An:* The OpenCms mailing list<br>
> *Betreff:* Re: [opencms-dev] flag not to publish<br>
><br>
> Hi kai!<br>
><br>
> In version 6.xx, opencms ceases publishing if a subelement is not<br>
> allowed to be published.<br>
><br>
> In version 7.0.4, when I derive from a "Administrator" and adapt the<br>
> Role for the specific role, it is ignored.<br>
><br>
> I also tried to adapt the opencms-importexport.xml to set the folder<br>
> immutable to be not exported, but subfolders are still exported ;(<br>
><br>
> ------------------------------------------------------------------------<br>
><br>
> *From:* <a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a><br>
> <mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a>><br>
> [mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a><br>
</div></div><div class="Ih2E3d">> <mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a>>] *On Behalf Of *Schliemann, Kai<br>
> *Sent:* Dienstag, 03. Juni 2008 09:54<br>
> *To:* The OpenCms mailing list<br>
> *Subject:* Re: [opencms-dev] flag not to publish<br>
><br>
> Hi Christian,<br>
><br>
> maybe there is an other solution.<br>
><br>
> If you work with permissions, you can "not allow" publishing for all<br>
> users in the system for that subfolder.<br>
><br>
> Never tried it, but this should work as well.<br>
><br>
> Regards Kai<br>
><br>
> ------------------------------------------------------------------------<br>
><br>
> *Von:* <a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a><br>
> <mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a>><br>
</div><div class="Ih2E3d">> [mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a><br>
</div><div class="Ih2E3d">> <mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a>>] *Im Auftrag von *Krenn,<br>
> Christian<br>
> *Gesendet:* Dienstag, 3. Juni 2008 09:37<br>
> *An:* The OpenCms mailing list<br>
> *Betreff:* Re: [opencms-dev] flag not to publish<br>
><br>
> Yes, but it is no permanent solution. I'd like to declare a<br>
> subfolder to be not published permanently.<br>
><br>
> ------------------------------------------------------------------------<br>
><br>
> *From:* <a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a><br>
> <mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a>><br>
</div><div class="Ih2E3d">> [mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a><br>
</div><div class="Ih2E3d">> <mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a>>] *On Behalf Of *Carl Alex<br>
> Friis Nielsen<br>
> *Sent:* Dienstag, 03. Juni 2008 09:28<br>
> *To:* The OpenCms mailing list<br>
> *Subject:* Re: [opencms-dev] flag not to publish<br>
><br>
> You can use locking to prevent resources from being published.<br>
><br>
> -----Original Message-----<br>
> *From:* <a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a><br>
> <mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a>><br>
</div><div class="Ih2E3d">> [mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a><br>
</div><div class="Ih2E3d">> <mailto:<a href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a>>]*On Behalf Of *Krenn,<br>
> Christian<br>
> *Sent:* Tuesday, June 03, 2008 8:22 AM<br>
</div><div><div></div><div class="Wj3C7c">> *To:* <a href="mailto:opencms-dev@opencms.org">opencms-dev@opencms.org</a> <mailto:<a href="mailto:opencms-dev@opencms.org">opencms-dev@opencms.org</a>><br>
> *Subject:* [opencms-dev] flag not to publish<br>
><br>
> Hi!<br>
><br>
> Is there a possibility to set a folder to be not published? I<br>
> know the capability of setting export to false, but it doesn't<br>
> help me.<br>
><br>
> Thanks in advance.<br>
><br>
> Best wishes<br>
><br>
> ***************************************************************************************************<br>
><br>
> The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.<br>
><br>
> ***************************************************************************************************<br>
><br>
> BearingPoint INFONOVA GmbH<br>
> Sitz: Unterpremstätten bei Graz<br>
> Firmenbuchgericht: Landesgericht für ZRS Graz<br>
> Firmenbuchnummer: FN 44354b<br>
><br>
> ***************************************************************************************************<br>
><br>
> The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.<br>
><br>
> ***************************************************************************************************<br>
><br>
> ***************************************************************************************************<br>
><br>
> The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.<br>
><br>
> ***************************************************************************************************<br>
><br>
> BearingPoint INFONOVA GmbH<br>
> Sitz: Unterpremstätten bei Graz<br>
> Firmenbuchgericht: Landesgericht für ZRS Graz<br>
> Firmenbuchnummer: FN 44354b<br>
><br>
> ***************************************************************************************************<br>
> The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.<br>
> ***************************************************************************************************<br>
><br>
> ***************************************************************************************************<br>
> The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.<br>
> ***************************************************************************************************<br>
><br>
> BearingPoint INFONOVA GmbH<br>
> Sitz: Unterpremstätten bei Graz<br>
> Firmenbuchgericht: Landesgericht für ZRS Graz<br>
> Firmenbuchnummer: FN 44354b<br>
><br>
><br>
> _______________________________________________<br>
> This mail is sent to you from the opencms-dev mailing list<br>
> To change your list options, or to unsubscribe from the list, please<br>
> visit<br>
> <a href="http://lists.opencms.org/mailman/listinfo/opencms-dev" target="_blank">http://lists.opencms.org/mailman/listinfo/opencms-dev</a><br>
><br>
><br>
><br>
><br>
</div></div>> ------------------------------------------------------------------------<br>
<div><div></div><div class="Wj3C7c">><br>
><br>
> _______________________________________________<br>
> This mail is sent to you from the opencms-dev mailing list<br>
> To change your list options, or to unsubscribe from the list, please visit<br>
> <a href="http://lists.opencms.org/mailman/listinfo/opencms-dev" target="_blank">http://lists.opencms.org/mailman/listinfo/opencms-dev</a><br>
<br>
_______________________________________________<br>
This mail is sent to you from the opencms-dev mailing list<br>
To change your list options, or to unsubscribe from the list, please visit<br>
<a href="http://lists.opencms.org/mailman/listinfo/opencms-dev" target="_blank">http://lists.opencms.org/mailman/listinfo/opencms-dev</a></div></div></blockquote></div><br><br>