# Page versioning

**URL:** <https://www.ruby-forum.com/t/page-versioning/105537>\
**Category:** Radiant CMS\
**Created:** [May 30, 2007, 10:09pm UTC](https://www.ruby-forum.com/t/page-versioning/105537 "2007-05-30T22:09:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_OSBrien](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/d6d6ee/32.png) [@Andrew\_OSBrien](https://www.ruby-forum.com/u/Andrew_OSBrien)\
**Post date:** [May 30, 2007, 10:09pm UTC](https://www.ruby-forum.com/t/page-versioning/105537/1 "2007-05-30T22:09:21Z")

</div>

I’m sure this has come up before, but has any work been done on making  
page versions that can be rolled back and possibly diff’ed through the  
admin UI?

I can certainly understand not wanting to support it in the trunk,  
with all of the complexity it would bring that may not appeal to every  
user. It seems like aside from interface changes, all you’d have to  
do would be set-up acts\_as\_versioned in the PagePart model – all  
changes that could be done in an extension.

Has anyone tried to implement this? Are there more complicated issues  
at play?

Thanks,  
Andrew

---

<div class="post-metadata">

**Author:** ![Andrew\_OSBrien](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/d6d6ee/32.png) [@Andrew\_OSBrien](https://www.ruby-forum.com/u/Andrew_OSBrien)\
**Post date:** [May 30, 2007, 10:16pm UTC](https://www.ruby-forum.com/t/page-versioning/105537/2 "2007-05-30T22:16:25Z")

</div>

There have been attempts in the past on that. One thing that has  
hampered moves in that direction is the relative heaviness of the  
Radiant admin controllers – mostly with the creation or updating of  
pages. In the future, we plan to push a lot of the logic down into the  
models, which will in turn make things easier for extension developers  
and facilitate things like this.

Sean