Re: [Collective-versioning] Hook version creation in CMFEditions

[Gregoire W. <gr...@in...>]

Hi Sylvain,

Assuming you're meaning with *head* the newest version
*in the repository* and not the *working copy* in the
Plone tree:

     Write your own modifier which modifies the object to be
     saved prior it gets really saved to the repository.
     This is the standard way for manipulating what gets
     versioned at save time.

If you're talking about the *working copy*, then you could
hook in with a modifier as well that manipulates the working
copy on save. Although this isn't the intention of modifiers
and thus not the way to go for long time it could be a
solution for you in short time. The real place to do such a
thing is the repository level.

If you're not able to decide between the above possibilities
just two hints:

- If your intention is to alter *what* to store for later
   retrieval then you should go the modifier way.
- If your say: "I'm not interested how all this storing
   stuff works, I just want to set some kind of versioning
   related state information to the objects in the Plone
   tree then you should think about extending or help us
   extending the CopyModifyMergeRepositoryTool.py.

We're very interested if you could describe more in detail
what your use cases are. CMFEditions isn't really strong in
high level use case flexibility yet.

Gregoire

Sylvain Th=E9nault schrieb:
> Hi there,
>=20
> I've another question regarding CMFEditions: I have to hook new version
> creation to make some automatic changes on the head object. Do you know
> if this is currently possible ? If not, any idea about where could I pl=
ace
> a call to an external hook, or any other idea about how to acheive this=
 ?
>=20
> TIA