[Product-Developers] [plone.app.iterate] Why is working copy support tied to versioning?

David Glick (GW) davidglick at groundwire.org
Wed Apr 25 15:23:04 UTC 2012


On Apr 25, 2012, at 8:10 AM, Andreas Jung wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> David Glick (GW) wrote:
>> On Apr 24, 2012, at 11:53 PM, Andreas Jung wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>
>>> Hi there,
>>>
>>> I wonder why the working copy support of Plone is only working for
>>> content-types with versioning enabled? Is there any particular
>>> reason because I consider both features (working copy support and
>>> versioning) independent of each other.
>>>
>>
>> I'm not sure. I just glanced through plone.app.iterate and didn't see
>> anything that would obviously make it require versioning. In what way
>> does it fail without versioning?
>>
>
> There is an explicit check inside checkout_allowed() that is related to
> versioning enabled. Without having versioning enabled for my types,
> checkout_allowed() will always return False.
>

Ah yes, I see. I guess you could experiment with removing that check and modifying subscribers/versioning.py to not break if the object isn't versionable.
David



----------
David Glick
 Web Developer
 davidglick at groundwire.org
 206.286.1235x32

GiveBIG is coming! Mark your calendar for May 2 and get ready to give big to Groundwire
on this community-wide day of giving.

http://www.seattlefoundation.org/npos/Pages/Groundwire.aspx




More information about the Product-Developers mailing list