Re: FW: [Vasudeva SysAdmin] more probs on races - permissions

Hi everybody,

I just sent a message answering Jwalanta's first 'problem report' about
changing the order of documents etc. Now about his list of non-corresponding
security settings, I wouldn't be concerned about that. It is on our
Zopestage/Live sites that the editors actually have a few more rights than
they should have according to VSAPloneSetup.doc, but these rights are hardly
relevant and they came up through all our debugging efforts. When we create
our next Plone site from scratch, we should start from the VSAPloneSetup.doc
permissions definition, of course, but for the time being, it doesn't really
make a difference.

Should we create a fresh Plone site right now, as Priyadarshan suggests (see
below)? Maybe, but if we do, we don't do it because of the permissions. I
understand the permissions-related issues quite well, and I do not see a
necessity for changing anything at the moment. (However, Jwalanta has got
quite a few good ideas and is experimenting with them on his local machine
right now; he may come up with some suggestions, but that's for the
future...)

What I still do not understand fully, and the only thing that really
troubles me right now, and the only thing that may force us to recreate our
Stage/Live-sites from scratch in the near future, is the join-error. As I
see it now (and as I explained in today's other messages), a partial
corruption of the Data.fs is probably involved. But it would be nice to
understand what that means for the future. Will we have to recreate our
Plone sites every three weeks because this corruption happens again and
again? I don't know. Maybe we will have to find out the hard way...

Greetings
Dhyani



> This is a problem!
>
> To solve it, this would be my strategy:
>
> Dhyani and/or Jwalanta should:
>
> 1) create a fresh plone site in local
> 2) consolidate the workflow to make a latest version of the workflow
> document
> 3) apply the workflow document to your new local plone
> 4) test that the workflow works as intended, with nothing in it, just
> the bare plone site
>
> If (4) is satisfied, then:
>
> 5) export all the content from the live site
> 6) import it in your local plone
> 7) test it to see it is still working
>
> if (7) is satisfied, then
>
> 8) apply vsaCore in local
> 9) test if it still working
>
> if (9) is satisfied, then
>
> 10) apply vsSriChinmoyRaces (the skin) in local
> 11) test it if it still working
>
> if (11) is satisfied, then
>
> 12) give it to Jagrata to stage it
> 13) test it on Vasudev
>
> if (14) is satisfied, then
>
> 15) substitute the messed-up plone site with the working one
>
> I do not think this would not take too much time, and if at a certain
> point things would go haywire, at least we would know what is wrong.
>
> ~priyadarshan
>   Vasudeva server
>
> On May 6, 2004, at 07:32, (Jwalanta) wrote:
>
> > Hi everybody,
> > Viliam requested me to check the permissions again.
> > Here my dicoveries of differences:
> >
> > Root folder - Security Tab
> >
> > VSAPloneSetup.doc               srichinmoyraces settings
> > ------------------------------------------------------------
> >                                 Access contents information
> > Access future portal content    Access future portal content
> > Add PloneArticles               Add PloneArticles
> > Add portal content              Add portal content
> >                                 Add portal events
> > Add portal folders              Add portal folders
> >                                 Copy or move
> > Delete objects                  Delete objects
> >                                 Import/Exprot objects
> > List folder contents            List folder contents
> > List portal members             List portal members
> > List undoable changes           List undoable changes
> >                                 Modify portal content
> >                                 Request review
> > Set own password                Set own password
> > Set own properties              Set own properties
> > Undo changes                    Undo changes
> > Use external editor             Use external editor
> >                                 view
> >
> >
> > Just a guess: We might have to do changes in to the
> > permissions-tab of the different states
> > (/portal_workflow/plone_workflow/states/)
> > to achieve what we want.
> >


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