I asked this back in May. Here's the link to Sean's response: http://lists.radiantcms.org/pipermail/radiant/2007-May/005038.html
I'm wondering with facets maturing if this is more feasible now than it was then? The problem I still see is more of a conceptual one: what I (and I think you) want is a history of changes at the Page level. However, changes are done at the PagePart level. But keeping a version history for each page part separately wouldn't make sense to the end user, and it probably wouldn't help admins either. Also, version control is a solved problem (or at least one with a lot of good work already put in), whereas versioning inside of a relational database is a little tougher and solutions tend to be more one-off (at least in my experience). Alternatively, something I've been toying with (and I'd love to get feedback) would be to use a variation of the import/export extension to serialize the page tree (or a subtree of it) and then put that tree in version control. I was thinking of creating directories for pages and representing each part as a file within that directory (instead of the single file format that Import/Export does, so that changesets will be more meaningful). Reverting would be a matter of loading a previous revision into the database (or you could keep other revisions in separate databases). Some pros would be: 1) We don't have to make structural changes to pages or page_parts 2) We don't have to reinvent the wheel 3) We can use proven tools that already work with repositories, such as a) Capistrano for deploying from an internal staging server to a production one, b) Meld (or any other diff tool) for viewing diffs Cons: 1) If you actually want the revision data to be viewable, that might take a little bit of work to get it from the version control system to Radiant (I think it's possible though) 2) Database reload time when moving to different revisions will probably be high. There would probably be an easy way to only load changed pages based on the changeset, which would cut down on this, at least for moving forward in the history. Any comments? -Andrew On 9/20/07, Mohit Sindhwani <[EMAIL PROTECTED]> wrote: > Anyone? > > Thanks, > Mohit. > > > Mohit Sindhwani wrote: > > Hi Everyone, > > > > As I understand it, Radiant doesn't seem to support page versions and > > comments for the page versionsdirectly.. is there any extension that > > does? It seems that it should be easy enough to have support for > > comments about the different page versions. That would allow me to add > > something like: > > > > RECENT CHANGES > > Version 8: Sep 12, 2007 - Added detailed explanation for Installation. > > Version 7: Sep 10, 2007 - Minor changes; corrected punctuation errors. > > Version 6: Sep 2, 2007 - Global revision change. > > [Click here for earlier changes] > > > > The comments can be done by adding a 'has_many CommentsAbtversions' to > > the Page and then adding a small text input that allows the comment to > > be input. > > > > Q1: In an extension, how do I tell the difference between a 'Save' and > > 'Save & Continue Editing' - I thought it may be better to save comments > > only when one does a 'Save' as against when he does a 'Save & Continue > > Editing'. > > > > But I'm a bit more hesitant about how to actually add in the versions > > themselves without changing the page rendering system too much. > > > > Cheers, > > Mohit. > > 9/16/2007 | 6:46 PM. > > > > > > _______________________________________________ > > Radiant mailing list > > Post: [email protected] > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
