Re: Contents Tab

Notes below.

  (Dhyani) wrote:

> Hi Jagrata / Priyadarshan,
> 
> it's quite complicated. First, let's look at displayContentsTab. It can't
> really be customized, whatever I do, the "real" displayContentsTab is being
> called, not my customization. Whatever the reason for that may be.



> Now, when you look at the code, they say in their comment that one of the
> three Permissions Copy or Move, or Modify portal content, or Add portal
> content has to be set, or at least on the parent level. But the code itself
> does something else: It demands that ALL of the following three Permissions
> are set: 'Copy or Move', 'List folder contents', 'Modify portal content'. On
> the parent level, only two of them would be required.

ok. recap.

1. If the object has those three props, we show the tab.
2. If the object fails to have those three props, show the
    tab if and only if (a) we are authorized to query
    parent perms AND (b) the parent has both
    'Modify portal content' and 'Copy or Move'.

> 'Modify portal content' in our case is State-dependent, which means that if
> the State=Published, we do not have this Permission, with the result that we
> don't get a Contents Tab. If I change this setting in the workflow, then the
> editor can edit published content, something we decided not to allow.

Given our workflow, let's identify the logic
we want and change displayContentsTab.

> Why did we see the Contents Tab previously? I'm not quite sure, since there
> are so many things involved. But I guess that we had some private stuff in
> the folder - or even on the parent folder level - and thus got a different
> set of Permissions from the workflow.

Yes, and for that matter, why have we seen different behaviors
on Windows and Linux?

I have changed (in place) 'AND' above to 'or' on the stage.
You can confirm that the contents tab does show
for editor_usa in places where it didn't before.
I am not saying this is the right config, but at
least the change is showing up on the stage.

> Some things are quite confusing. I found out that when you take away the
> View Permission from the Anonymous User on the Zope Root, even the Editor
> cannot access the site anymore. Isn't that terrible?
yes good to know.


--------------------------------------------------------------------------
This message is sent to you because you are subscribed to the mailing list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.