[Imc-drupal-dev] Workflow for stories (i.e. draft -> review -> published)?

Rob Heck dejitarob at gmail.com
Tue Nov 13 08:04:10 PST 2007


I am just using the core upload module, tinymce with the built in (at
least to the drupal version) advanced image plugin, and the upload
preview module. I tried img_assist and a few other image modules, but
I got the impression that they might be too cumbersome for most users.
Upload preview displays attachments as thumbnails, e.g.:

http://tampabay.indymedia.org/article/thousands-anti-war-protesters-take-over-do

Not too pretty but I think it's the simplest solution I've found.

Peace,
Rob

On Nov 12, 2007 11:28 PM, Ben West <westbywest at gmail.com> wrote:
> Hi Rob,
>
> Thanks for the response.  I'll check out the node override module.
>
> Also, may ask how you set up the image attachment for your article
> submission page?  It looks like you're using the upload module, upload
> preview, tinyMCE, and img_assist?  No image module, right?
>
> stlimc currently uses the image field + imagecache + CCK, but this proving
> to be pretty unwieldy, and it will require some non-trivial layout coding in
> contemplate to tighten up the layout.  Probably also will need a custom
> module to override hook_form_alter() and sanitize the current article
> submission form.
>
> Although image_field/imagecache/CCK provide options for creating a image
> gallery, automatic resizing, and related bling, I'm still looking for a
> reasonably simple way to attach image (where image_field/imagecache/CCK
> leaves something to be desired).
>
>
>
> On Nov 12, 2007 9:57 PM, Rob Heck <dejitarob at gmail.com> wrote:
> > Hi Ben,
> >
> > Your site looks very nice! I've recently finished the very simple
> > http://tampabay.indymedia.org using Drupal. I'm currently the only
> > active editor, so I just set the default publishing options to
> > "published," which goes into the Newswire sidebar that I created with
> > the Views module. If I want to move a story to the front page, I edit
> > it and check "Promoted to front page." I also use vote up/down and
> > voting actions to automatically change a story to "promoted to front
> > page" when it receives a certain number of votes (from registered
> > users).
> >
> > In case I get help in the future, I have installed the Override Node
> > Options module ( http://drupal.org/project/override_node_options ) to
> > get around the issue you identify with giving editors the overreaching
> > "node admin" permission. It basically creates a more limited
> > permission that just allows the editing of the publishing/workflow
> > options.
> >
> > I'm nearly finished documenting exactly how I built tampabay
> > indymedia. I will share as soon as I'm finished.
> >
> > Take care,
> > Rob
> >
> >
> > --
> > Rob Heck
> > 352.613.0621
> > dejitarob at gmail.com
> > http://dejitarob.wordpress.com
> > http://tampabay.indymedia.org
> >
> >
> >
> >
> >
> > On Nov 12, 2007 9:32 PM, Ben West <westbywest at gmail.com> wrote:
> > >
> > >
> > >
> > > Howdy, I've been working on a drupal IMC at http://reboot.stlimc.org.
> The
> > > site dev has been done largely by me, and, unfortunately, not as well
> > > coordinated with this group as perhaps it should have been.
> > >
> > > Anyhoo, something that I've had difficulty setting up is a coherent
> workflow
> > > for editorial stories and newswire stories. In particular, I was hoping
> to
> > > implement the following workflows, based on those from dadaIMC:
> > >
> > > Editorial Features:
> > >  A. Draft (visible to eds) -> B. Peer Review (visible to eds) -> C.
> > > Published in center column (visible to all)
> > >  - transition from state A to B occurs when author has completed story (
> e.g.
> > > unchecks a box marked "Draft" or something)
> > >  - transition from state B to C occurs when a proposed feature receives
> > > enough votes from editors
> > >
> > > Newswire Stories
> > >  A. Initial submission (visible to all) -> B. Promotion to feature
> (visible
> > > only to eds?) -> C. Published in center column (visible to all)
> > >  - transition from state A to B occurs when the story receives enough
> votes
> > > from users or editors (different vote thresholds for users vs. editors)
> > >  - transition from state B to C occurs when a proposed feature receives
> > > enough votes from editors
> > >
> > > Users/editors should be able to opt for email notification about any of
> > > these state changes, e.g. "a story was just submitted for feature
> > > consideration..."
> > >
> > > Drupal has the workflow and actions modules, which should be ideally
> suited
> > > for this task, but I've encountered a problem with setting up workflow
> > > states with restricted access (e.g. draft stories only visible to eds)
> > > because of incompatibilities I found between the workflow_access and
> > > taxonomy access modules.
> > >
> > > Furthermore, I'm reluctant to use Drupal's built-in
> published/unpublished
> > > property since A) that only represents 2 states, and B) that would
> require
> > > giving all editors Node Admin access, which makes for very cluttered
> node
> > > submission forms that can confuse less-than-web-savvy editors. There are
> > > hacks related to the published/unpublished switch, but they don't look
> > > pretty. Also, the Node Admin access would let eds circumvent revision
> > > control (e.g. change a story w/o storing the previous revision), which
> can
> > > become a problem with accountability.
> > >
> > > On the up side, I was able to create a functional voting system whereby
> > > editors vote features into publication using a combination of taxonomy
> > > access, voting API, voting actions, vote up/down , and a custom action
> to
> > > assign taxonomy terms. Maybe this would be of use to the IndyDrupal
> project?
> > >
> > >
> > >
> > >
> > > --
> > > Ben West
> > > westbywest at gmail.com
> > > http://savetheinternet.org
> > >
> > > _______________________________________________
> > > Imc-drupal-dev mailing list
> > > Info: https://docs.indymedia.org/view/Devel/ImcDrupalDev
> > > Imc-drupal-dev at lists.indymedia.org
> > > http://lists.indymedia.org/mailman/listinfo/imc-drupal-dev
> > >
> > >
> >
>
>
>
> --
>
>
> Ben West
> westbywest at gmail.com
>  http://savetheinternet.org
> _______________________________________________
> Imc-drupal-dev mailing list
> Info: https://docs.indymedia.org/view/Devel/ImcDrupalDev
> Imc-drupal-dev at lists.indymedia.org
> http://lists.indymedia.org/mailman/listinfo/imc-drupal-dev
>
>


-- 
Rob Heck
352.613.0621
dejitarob at gmail.com
http://dejitarob.wordpress.com
http://tampabay.indymedia.org


More information about the Imc-drupal-dev mailing list