On March 26, 2019 we launched new MODX Forums. Please join us at the new MODX Community Forums.
Subscribe: RSS
  • What is the intended maintenance cycle for MODx revolution? User data is kept inside the core directory structure, so an upgrade will be more than a simple delete core + install new. Is the user expected to backup/restore user data on each upgrade, or will revolution have some upgrade management build in? Maybe through the package manager, since core is already a package?
    And just to eliminate confusion, I refer to all differences between the core release package and the installation environment as being user data here...
    • Quote from: Jacob at Sep 13, 2009, 11:34 AM

      What is the intended maintenance cycle for MODx revolution? User data is kept inside the core directory structure, so an upgrade will be more than a simple delete core + install new. Is the user expected to backup/restore user data on each upgrade, or will revolution have some upgrade management build in? Maybe through the package manager, since core is already a package?
      And just to eliminate confusion, I refer to all differences between the core release package and the installation environment as being user data here...
      The core/packages/ and core/components/ directories will be the only locations with "user data" and these will not be touched during upgrades. In fact, we use SVN to checkout just the core/ directory to a location on the server and use SVN update + uploading a newly built core.transport.zip into core/packages/ (from the same revision obviously) to do our upgrades of the core.