Protecting Content Editors From Themselves
Sep 21

Protecting Content Editors From Themselves

Say you put together a nice, static site for a client. There’s a lot of CSS, a fair amount of scripting (in whatever language — we’ll assume PHP here), a handful of images, and a lot of HTML. The client is going to manage the site with a WYSIWYG editor.

What’s the biggest danger to your site? The person you hand it over to, of course. Invariably, they’ll get into files they shouldn’t, delete images they shouldn’t, or embark on CSS “upgrades” that they shouldn’t.

Shortly thereafter, you’ll get a call that begins, “The site doesn’t look right…”

How do you prevent this? Well, with a lot of hosts, you can finagle a few ways to prevent them from messing with things they shouldn’t by using additional FTP users and some Apache directives.

by Deane   September 21, 2004 4:36 AM    |   Follow Gadgetopia on Twitter   |  Tags:  Apache

Comments

by mbCodeMonkey,   September 21, 2004 3:17 PM  

Nice article, I once handed a site over to a client who had 'been on a course' and was 'more than capable of updating the site'

Hands up if you are suprised when I tell you that he deleted a page that he had spent hours working on and was asking if I had a copy

Well I did have a copy but it was months older than the work he had just lost and after a trawl through his Windows Trashcan came to no avail it was looking as if the file was gone forever

And then I had a brainwave, I Googled the site, hit the 'Cached' link and there in all its glory was the old copy

Add Comment