On Dec 20, 2011, at 12:52 PM, Paul Libbrecht wrote:
How hard would it be to add two actions
/begincompoundedit/
/endcompoundedit/
If by this you mean not creating revisions then I don't like it too much. For me
it's very important that any action is logged in the revision history and that we keep
this concept consistently everywhere. For me it's as important as the concept of
documents. It's one of our basic concepts.
Now it's ok for some use cases to perform some post cleanup actions to group revisions
together. A good use case is the real time edition one.
In addition to this we need to always ensure the following:
- allow any # of revisions for a document without causing any performance issues
- make it extra fast to save a revision
Thanks
-Vincent
?
I think this is what a normal text editor does before calling a macro.
paul
Le 20 déc. 2011 à 12:33, Sergiu Dumitriu a écrit :
On 12/20/2011 06:17 AM, Kjartan Hauksson wrote:
Hello all
I intend to do a lot of updates to a single page via a python script but I
don't want/need a huge history file. Is there a way to either disable
versioning for a single page or purging it periodically with a script ?
Disabling history for just one document, no. Resetting, yes.
There's the /reset/ action that can do that manually from the UI, and there's the
internal XWikiDocument.resetArchive(xcontext) method that you could use from a script. And
you could even make a scheduler job that runs periodically and does that.
If you want to keep a bit of history instead of deleting everything, you could look at
what the /deleteversions/ method is doing here:
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users