NOTICE:
This content is in the "archives" of a retired blog called Gadgetopia. It has been moved to this subdomain as it is no longer considered relevant to the site. It is being hosted here for a indeterminate period of time. Its existence at this URL is not guaranteed, and it may be removed at any time. If you would like to refer to this content in the future, you are encouraged to save it to your local file system.

Some content from Gadgetopia was moved to the technical blog on deanebarker.net

WordPress Gets Versioning

Originally published by "dbarker" on 2008-07-15 15:22:00Z

Version 2.6: WordPress v2.6 gets versioning.

Version/revision saves a copy of a post every time you edit it, allows you to view (not edit) each of those copies (revisions), Shows forward (in time) diffs between any two revisions.

I’m a big fan of versioning. As I discussed in this post, I think it’s a core component of content management, and it’s tough to call a system a true CMS without. This argument managed to persuade Josh Clark, so perhaps Matt Mullenweg read it too?

Comment by "Justin Hayes" on 2008-07-15 16:42:00Z

This is a feature in Drupal as well. Very handy feature, I agree it should be part of any CMS.

Comment by "Deane" on 2008-07-15 17:43:00Z

The thing that always bothered me about versioning in Drupal is that it's option. Maybe that's not a big deal, but it just bugged me that you could shut it off. I'm probably being silly.

Comment by "Justin Hayes" on 2008-07-15 06:19:00Z

It could potentially cause a lot of unnecessary (depending on who you ask) database bloat that some administers don't appreciate. That's why I think it's better that it's opt-in rather than opt-out. But really, you can't complain too much so long as the option is available :)