"Editor Only" Role for Content Creation
Sat, 05/16/2009 - 5:35am
I'm designing a Drupal website for an organization.
I've sold them on using Drupal, but they were rather daunted by the "admin mode's" array of menus. As a note, I had "admin_menu" module installed.
I am interested in creating an "editor" role, so that editing content and creating new pages is as easy and painless as possible for non-technical people.
As an open question to DRUPALug:
If you have some content editors who will only be doing a few specific things, like adding pages, just create a role and set the permissions for that role, and then put those user into the role. You probably don't want rank-and-file content editors messing around with the admin functions, anyway.
* Modules: Depends on site requirements. I look for modules that are relatively mature, seem to be supported actively, don't have a lot of nasty-looking open bug reports, and play well with others.
* I use FCKeditor. It's a big pain to set up, manage and update, but I have yet to find another one that is both better in that regard and doesn't have some critical failing.
Main issues with FCKeditor:
(a) The role-based permission hierarchy is complicated and anti-intuitive.
(b) If you don't set the default to have FCKeditor take over text area fields of, say, 4 rows or more, you end up manually adding it all over the place. If you do set it up that way, you end up manually removing it all over the place. For any field that can't have html in it (like fields that contain clean urls for redirecting the user after filling out a webform, for instance), you MUST turn of FCKeditor, because it will take over the field and stick p tags in it, even if you view the field in text-only mode and then just save it.
(c) There are a million files in the module, and some have permissions set so you can't easily remove them via FTP. This makes it cumbersome to update the module.
(d) You have to edit the config. file to do things like enable the block-quotes button, because there is no admin function for this.
(e) The styles for the actual editor box don't work properly for a lot of sites. I know I could mess with the CSS settings, and/or write CSS to make them work properly, but I never have time for that. It's not as simple as just opting to use the standard CSS, as the admin page for FCKeditor implies.
--Todd
-----Original Message-----
From: nsteier [mailto:admin@techmaine.com]
Sent: Saturday, May 16, 2009 6:35 AM
To: todd@techmaine.com
Subject: TechMaine - Drupal User Group (DRUPALug) - "Editor Only" Role for Content Creation