We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 11055 ☆ A M B ☆
    • 3,112 Posts
    It just a tickle thought of MODx’s system.
    It is very powerful system (as a CMS, or a web framework).
    But, it doesn’t support versioning, draft, or whatever, since its beginning, as its core feature.

    Why?
      Rico
      Genius is one percent inspiration and ninety-nine percent perspiration. Thomas A. Edison
      MODx is great, but knowing how to use it well makes it perfect!

      www.virtudraft.com

      Security, security, security! | Indonesian MODx Forum | MODx Revo's cheatsheets | MODx Evo's cheatsheets

      Author of Easy 2 Gallery 1.4.x, PHPTidy, spieFeed, FileDownload R, Upload To Users CMP, Inherit Template TV, LexRating, ExerPlan, Lingua, virtuNewsletter, Grid Class Key, SmartTag, prevNext

      Maintainter/contributor of Babel

      Because it's hard to follow all topics on the forum, PING ME ON TWITTER @_goldsky if you need my help.
      • 28215
      • 4,149 Posts
      Versioning is in the Roadmap for 2.1 and onward.

      Why hasn’t it been a core feature? For a few reasons:

      1. Versioning is very difficult to do well. What goes all into the version? Where is it stored? How does the UI work? How do rollbacks work? What about conflicts if 2 different users save at the same time?
      2. MODx Evolution did not have the underlying framework structure to properly support versioning. Revolution will solve that, but we didnt want to introduce too many new features with 2.0 (we fear we might already have!) and wanted to get it out sooner rather than later.
      3. Revolution will provide a proper migration path for Evolution users, both logically and in procedure, so that 2.1 can properly solve the versioning problem with proper efficiency.
        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
        • 13736
        • 345 Posts
        Maybe you’ve already figured out how the versioning interface should work, but I wanted to suggest a similar function to the way SilverStripe works. In SilverStripe, at any given time a page in the site has two copies. The draft copy and the published copy. So as an editor you can make as many changes and updates as you want without it going live to the public. Then it can be saved to the live site when finished or when approved by an admin. I’m not sure SilverStripe gives a full history, but having the staging area would be tremendously helpful as a mid point feature.