I have to stop using ModX :(

Hi all,

Today is a sad day. As much as I love it, I have decided I can no longer afford to use ModX. I thought I would write this in hopes of someone taking note of it and solving some of these issues:

• Whilst it seems ok for smaller sites, sites with high traffic get viruses constantly - there seems to be a lot of issues with security
• TinyMCE is extremely buggy and rarely works correctly. I would say it is broken on about 50% of the Evo and Revo sites I have made
• Updating from one version to another only works some of the time. Often it will break my site completely and I will actually have to down grade to solve the problem
• Entries in RTFM are sporadic and often missing key points.

Im sure people will have issues with these but here they are.

I have developed and maintained about 50 Revo and Evo sites over the years and dearly loved ModX but I just cannot keep up with the issues.

Thanks for all the support everyone and good luck!

TinyMCE isn't the only RTE. CKEditor is free and a premium RTE is in the works. What kind of viruses/security issues have you had? When upgrading sites is the issue usually depreciates TVs?

Quote from: dinocorn at Apr 22, 2013, 10:35 PM

TinyMCE isn't the only RTE. CKEditor is free and a premium RTE is in the works. What kind of viruses/security issues have you had? When upgrading sites is the issue usually depreciates TVs?

I have tried CKEditor as well and it has similar issues where I cannot browse for image files. When I upgrade I either get loads of PHP errors, cannot access manager or the site just appears as a blank page. As for viruses - there are loads of different kinds (mostly just spam). Usually I find them in the root directory or in the plugins database table.

Been using Moxd for the best part of 6 years, all hosted on one of 7 of our VPS's and can't remember ever getting hacked, in fact Modx ( in my opinion ) is one of the securest CMS's out there and when a vulnerability is spotted it's patched almost instantly, so if your always getting hacked I would recomend you look at the computers that are accessing the sites via FTP for viruses, what other software you have installed on the server and if it's a shared server speak to your hosts as any other software that is on there is a back door to your files.

As for upgrades I can only remember 1 time when it's broken a site and that was down to me doing things the wrong way round.

Sounds like the security problems are host and/of permissions related meaning you'd encounter them with any CMS. Curious what your upgrade process is, do you use SSH or manually upload files? Are you skipping several MODX versions?

Quote from: dinocorn at Apr 22, 2013, 11:27 PM

Sounds like the security problems are host and/of permissions related meaning you'd encounter them with any CMS. Curious what your upgrade process is, do you use SSH or manually upload files? Are you skipping several MODX versions?

I follow the steps in RTFM (http://rtfm.modx.com/display/revolution20/Upgrading+MODx) for upgrading. Sometimes I find it easier to wipe the site and install the new version afresh, then copy across the necessary tables, assets and reinstall plugins. I do the latter with large updates where I skip a few versions.

I've never used Evo but imagine the same would apply. If you are comfortable with SSH you can write yourself a build script that will upgrade quickly and assuringly.

http://devries.jp/blog/2013/04/16/make-upgrading-modx-sites-easy/

Sometimes I find it easier to wipe the site and install the new version afresh, then copy across the necessary tables, assets and reinstall plugins. I do the latter with large updates where I skip a few versions.

This is asking for trouble, IMO. Sometimes the tables themselves are changed in an upgrade and sometimes the form of the data *in* the tables is changed, putting old tables into a new install can be a recipe for disaster.

Here is the method I use: http://bobsguides.com/modx-upgrade-faq.html. I can do it in about 15 minutes. I've never had a problem with an upgrade that wasn't cured by deleting all files in the core/cache directory and clearing my browser cache and cookies. I would say that about 90% of the problems I see with upgrades are due to a leftover cookie or leftover code in the browser's cache. Also, some browsers don't fully clear the cache when you tell them to (I'm looking at you, Chrome).

Quote from: BobRay at Apr 23, 2013, 12:28 AM

Sometimes I find it easier to wipe the site and install the new version afresh, then copy across the necessary tables, assets and reinstall plugins. I do the latter with large updates where I skip a few versions.

This is asking for trouble, IMO. Sometimes the tables themselves are changed in an upgrade and sometimes the form of the data *in* the tables is changed, putting old tables into a new install can be a recipe for disaster.

Should clarifye: I copy the contents of the old tables into the new one - I dont overwrite the new tables

Ya you shouldn't have to mess with tables for upgrades, just when migrating content from a dev site to production site for example