I have recently logged into my site after about 2 years and noticed a number of security announcements. What would be a sensible way to address them. Should I tackle them each separately or would creating a new install be a better option.
-
MODX Staff
- 12,272 Posts
Back everything up. Twice for good measure in fact. Then copy everything to a local dev server and upgrade to the latest 1.0.5 and see what happens. If that works try it in place on the live site.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
☆ A M B ☆
- 24,524 Posts
1. rename new folders and files in the root (index.php.new, manager.new, assets.new) with a .new at the end and upload.
2. Copy your original manager/includes/config.inc.php file to the manager.new/includes folder.
3. Rename the original files/folders in the root with .old (index.php.old, manager.old, assets.old)
4. Rename the new assets/snippets folder to assets.snippets.new, and copy over your original assets/snippets folder.
4. Rename the new ones, removing the .new suffix. Run the installer in upgrade mode (if it doesn’t offer upgrade mode, check to make sure you put the config.inc.php file in the correct place, manager/includes/config.inc.php and that it’s writable), but DO NOT upgrade the snippets. Plugins and modules should be upgraded.
The reason why you shouldn’t try to use the new snippets is that some of them have changed enough to not work with the old snippet calls you’ll have. You’ll need to upgrade the snippets manually one at a time to see what breaks, and fix the snippet calls (such as Wayfinder or Ditto) to use the new parameters.
Also make sure to copy to the new assets/templates folder your old templates folders, and any custom plugins or modules you had on the old installation.
