Hi there.
I have just been put in charge of modernising my company’s website. I have suggested that they implement a CMS and they agree that this would be a good idea. I have tested out various CMSs and identified MODx as the most appropriate for our needs. Then I remembered that there is a company QA requirement that all source code (xhtml templates, css etc.) be versioned. We normally use some kind of source control system , such as Microsoft Source Safe or subversion.
In an old post with the subject "Using version control and a programmers editor" (or something similar), I read that including versioning functionality was planned for in MODx. Could someone please give me an update on that? Given that it’s not implemented yet, has anyone devised any good strategies for versioning? Is simply putting the assets folder under source control with CVS and then committing after working on the website each time the best option for the moment?
Thanks.
-
MODX Staff
- 10,725 Posts
You could put all the files in SVN along with a regular SQL dump of the database, which is where most of the (X)HTML/CSS/JS/PHP code is going to be.
You could also create a plugin that could handle storing each previous version when a change was made, perhaps to a custom data table.
Otherwise, it’s going to be post-0.9.7 before native content versioning and rollback features are available in the core API or the default manager interface.
Okay. Thanks for your advice. I’ll store everything under source control. I’m new to plug-ins, but writing one to do svn commits after save events would seem like a good idea. If I make any progress with that, then I’ll let people know. Of course, if someone has already done it or can offer some advice about how to go about it, I’d be glad to hear from them in order to avoid re-inventing the wheel.
Cheers.
