Note that although UpgradeMODX uses the Traditional distribution, it will respond correctly to those customized paths, although if you want to customize them during setup, you’d have to use the Advanced distribution at least once before using UGM.
I’ve been testing UGM and was able to upgrade directly from 2.8.3 to the current MODX 3 version (beta2). The problem was the Chrome browser cache. Once I turned on the Cache Killer Chrome extension, the upgrade went fine. There were no errors displayed during Setup (not the case without Cache Killer). I suspect that using Private or Incognito mode would work as well, though I haven’t tested it.
The specific problems I had without Cache Killer were:
- Unable to update modUser table during setup
- Various duplicate column errors during setup
- Unable to edit resources, though Quick Edit worked
- Keyword search in System Settings didn’t work, and the button to create new System Settings had no text.
I don’t think these errors were related to UGM, which simply puts the files in place and launches setup.
As far as I can tell, everything works now with Cache Killer, though it’s still possible that there are problems I haven’t discovered.