On 08.05.2012 23:23, Richard Frovarp wrote:
> On 05/08/2012 03:26 PM, Markus Angst wrote:
>>>> Is there (still) no possibility to delete old revisions of documents (via 
>>>> GUI or
>>>> otherwise) or have I overlooked something?
>>>>
>>>> If I have to do it by hand: is it enough to delete *.bak files and their
>>>> corresponding entries in the *.rcml file?
>>>>
>>>> Thanks for any hints :-)
>>>>
>>>> Markus Angst
>>>>
>>> That's pretty much what you need to do. You can reduce the number of
>>> versions kept around. From my experience, you don't actually have to
>>> clean up the .rcml file. It will take care of that without throwing an
>>> error.
>>>
>>> Richard
>> This sounds promising, so I experimented a little bit. I did the following:
>>
>> - identified the UUID of a document under Site / Overview
>>    (document has 53 revisions)
>> - stopped Lenya
>> - deleted the oldest 42 revisions from content/authoring/<UUID>
>> - started Lenya
>> - navigated to Site / Revisions of the document
>> - the tab still shows 53 revisions
>> - click "View revision" on the topmost line (revision 53)
>>    -->  document opens (ok)
>> - click "View revision" on revision 40 (has been deleted)
>>    -->  got error: Could not read resource
>>        cocoon://modules/xhtml/xhtml.xml/<pubname>/authoring/<UUID>/de"
>>    (which is no surprise :-)
>>
>> What do I have to do to trigger the automatic .rcml cleanup? Lenya version 
>> is 2.0.4.
>>
>> Thanks!
>> Markus
>>
> 
> For what I was doing, I never really worried about it, or just let it 
> roll off by itself.

Well, then I could make roll off as much as I want by lowering the max. number
of revisions? Do you know where this number is configured?

> I guess it kind of depends on what your usecase for doing this is.

To make a copy of a production publication (with lots of revisions) for a test
server.

Thanks
Markus

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to