In reply to Peter Knight.

By security I do not mean simply hackers getting in although that is a major component. I've seen the code editor used in a hijacking before to modify the theme to start injecting malvertising. The admins would go to bed one night and then wake up the next morning to e-mails reporting the problem. Wash, rinse, repeat. It's the reason one of my former employers now bans WordPress 100% across the board sans one site.

But part of security is maintaining integrity of the site. Allowing destructive editors with no safety whatsoever is just asking for trouble, especially if it is a site managed by one entity but maintained by another.

I get that a lot of people learn to mess with WordPress this way, but it doesn't change the fact it is not an advisable method. Do we teach people how to drive by simply putting them in the driver's seat of a car on the high way and say "Good luck"? No.

They're better off being encouraged to download a *AMPP program, WordPress, and a theme and go to town on that where there's no possible way to damage a live site or worse.