This project is read-only.

Non versioning attribute

Topics: Developer Forum
Aug 3, 2008 at 12:30 PM
Edited Aug 3, 2008 at 12:32 PM
I've looked into the saving and versioning mechanism in N2, and it's quite straight forward. Even though, I don't exactly know where to control versioning for specific item types (just like you use "NotThrowable" for the trash). The save button in edit mode is quite easy to modify, but the recursive save of child items etc. can be tricky if it's not implemented in the core.
Perhaps an attribute check can be made in the same place as the web.config settings is checked (enableVersioning="true")?
Aug 3, 2008 at 9:13 PM
Good idea. I've just commited [NotVersionable].

Aug 31, 2008 at 12:27 PM
Edited Aug 31, 2008 at 12:29 PM

It would also be awesome having some sort of maximum number of versions allowed (just like EPiServer), perhaps per Item type? If the maximum number of versions is reached, the oldest version should be deleted. It would be ok if the number is configurable by site (in web.config), but something I sometimes think is missing in EPi is the option to restrict the number of versions a specific type of page/item could have.