View permission lost after migration to 2.5

Migrating Plone site from 2.0.5 to 2.5.2.

Our site has custom roles
and restricts View permission on some objects. After
migration, I
noticed that object View permissions have not been
preserved. I have
verified this in the debugger:

BEFORE:
>>> i._View_Permission

('Manager', 'Ph_Member')

This object's View permissions are not
acquired, and only Manager and Member (custom role) have
view
permission.

AFTER:
>>> i._View_Permission 
['Manager']

This object
acquires View permission from parent.

Is this expected? Some objects
*do* have View permission preserved. It seems to affect
objects with
View permission assigned to our custom roles. What things
might be
involved in causing this?

Another interesting note:

None of the
objects with custom View permission seem to be indexed in
portal_catalog before the migration. (They did not appear in
queries
even after clearing and rebuilding the catalog. They do
appear in
catalog after migration.) Should this matter?

Thanks!
Ed
Eddington
Priority Health


-- 

I'm trying a new usenet client for Mac, Nemo OS X.
You can download it at http://www.malcom-mac.
com/nemo



_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup

This problem may be related to workflow. The
_View_Permission that is
reset during migration appears to be set to the object's
published
workflow state. However, in our case, we have a workflow
script that
is supposed to run before/after the publish transition to
preserve the
_View_Permission. Can anyone clarify what workflow related
updates are
done during a migration (are objects "published",
or "retracted and
republished", etc.)? It appears as if _View_Permission
is simply being
reset to the permissions defined in the workflow state -
WITHOUT
running the transition scripts.

In article <nemoTue061207084043news.gmane.org> Ed
Eddington<edinternethut.com> wrote:

>  Migrating Plone site from 2.0.5 to 2.5.2.
>  
>  Our site has custom roles
>  and restricts View permission on some objects. After
migration, I
> noticed that object View permissions have not been
preserved. I
> haveverified this in the debugger:
>  
>  BEFORE:
>>>>   i._View_Permission

>  ('Manager', 'Ph_Member')
>  
>  This object's View permissions are not
>  acquired, and only Manager and Member (custom role)
have view
>  permission.
>  
>  AFTER:
>>>>   i._View_Permission 
>  ['Manager']
>  
>  This object
>  acquires View permission from parent.
>  
>  Is this expected? Some objects
>  *do* have View permission preserved. It seems to
affect objects with
> View permission assigned to our custom roles. What
things might
> beinvolved in causing this?
>  
>  Another interesting note:
>  
>  None of the
>  objects with custom View permission seem to be indexed
in
> portal_catalog before the migration. (They did not
appear in queries
> even after clearing and rebuilding the catalog. They do
appear
> incatalog after migration.) Should this matter?
>  
>  Thanks!
>  Ed
>  Eddington
>  Priority Health
>  
>  
> 


-- 

I'm trying a new usenet client for Mac, Nemo OS X.
You can download it at http://www.malcom-mac.
com/nemo



_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup

On Thu, 21 Jun 2007 06:26:42 -0700, Ed Eddington  
<edinternethut.com> wrote:

> This problem may be related to workflow. The
_View_Permission that is
> reset during migration appears to be set to the
object's published
> workflow state. However, in our case, we have a
workflow script that
> is supposed to run before/after the publish transition
to preserve the
> _View_Permission. Can anyone clarify what workflow
related updates are
> done during a migration (are objects
"published", or "retracted and
> republished", etc.)? It appears as if
_View_Permission is simply being
> reset to the permissions defined in the workflow state
- WITHOUT
> running the transition scripts.

This is how workflows work. Never set permissions manually
outside of  
workflow states. They will be reset to what the state
specifies.

(unless I misunderstood what you're explaining above)

-- 
Alexander Limi · http://limi.net


_______________________________________________
Setup mailing list
Setuplists.plone.org
http://
lists.plone.org/mailman/listinfo/setup