Borked MODX 2.3 Installations

I was thinking more from a backend management perspective rather than the end user's. As you say they will be restricted on what the can and can't do and really should be responsible for their data. There again end users can always manage to find ways to break something, given half a chance.

My recent experiences of broken CMS software has made me very wary about how I approach development with CMS platforms. My method to date has opnly involved non-database driven sites. So I simply back everything before I replace any files. If I find the changes break the site I simply replace the files with the backups. It normally only taks a few minutes at most.

I've got a lot to learn.

Thanks for the feedback, Graeme. Much appreciated.

Quote from: ridgedale at Jul 25, 2014, 08:14 PM

My recent experiences of broken CMS software has made me very wary about how I approach development with CMS platforms. My method to date has opnly involved non-database driven sites. So I simply back everything before I replace any files. If I find the changes break the site I simply replace the files with the backups. It normally only taks a few minutes at most.

I've got a lot to learn.

I am onboard with you here, I need to approach CMS driven development a bit more slow and steady. I finally resolved my issues. It was server issue involving shared hosting and mod_security.

http://forums.modx.com/thread/92290/modx-2-3-website-breaks-after-resource-save?page=3#dis-post-505069