By peterx on

http://drupal.org/handbook/modules/story does not point out anything different between stories and regular pages. I though stories might have extra workflow around editing but I have not found anything. I am about to use the E-Publish module in a site where the authors need the help of an editor. If the story node type is not the solution, is there another way to direct pages to an editor?

How do people use stories?

If I had one group contributing pages and another contributing stories then I can limit their activity by letting them edit only their own pages or stories. The page writers would normally be responsible for a specific page such as a page listing delivery times. They could update those pages when the data changes. Stories seem to be limited to the same controls.

I thought stories might let me assign an editor and give only the editor permission to publish. Are stories headed that way?

The workflow for a story is generally writer to editor to writer and back for a while with the editor eventually publishing. In a newspaper the process is one way with the editor changing the spelling, grammar, content, and meaning without asking the author. If the Drupal use of stories was extended to an editing phase then the author would not see the publish option. Instead the author or system would select an editor. Only the editor would see the publish option.

Comments

Richard Archer’s picture

Richard Archer commented

Story and Page are almost the same thing. Pages can have log messages, stories can't. There is no other functional difference in the code.

The reason two different node types exist is so that you can set up different workflow and display options. I think most sites use page for general pages on the site and use story for news articles. Page then has comments and author info disabled, while story allows these extras.

Wai_Wai’s picture

Wai_Wai commented

Indeed, as someone point out at http://drupal.org/node/21947 in the comment section, story and page have no functional differences.

The comment says: "It should probably be noted that now any node-type can contain customized PHP code, so this no longer makes a page special. In fact, it makes page and story the exact same thing."

So you may treat both as:

page-type01, page-type02
or
story-type01, story-type02

Since you get two nodes of the same type, you may have different settings for these 2 nodes. It is up to you to design/create the differences between type01 and type02. ;)

reikiman’s picture

reikiman commented

I was expecting "story" to include support for breaking the story over multiple pages.

e.g. say you've got a long story like this one: http://7gen.com/march-15-2003-protest-rally-in-san-francisco ... what one wants is to split that up into sub-pages. (warning: the page I linked to has an anti-war war theme) (oh, and a picture of a naked man)

- David Herron - http://7gen.com/

+ David Herron - 7gen.com/, The Long Tail Pipe, davidherron.com/drupal-blogging-hints

peterx’s picture

peterx commented

I found the Workflow module which could make stories work the way I want. It looks like it is stuck at 4.5.0. Have you used the workflow module? With Drupal 4.6.0?

The Workflow module, http://drupal.org/project/workflow, is described at follows.

The workflow module allows the creation and assignment of arbitrary workflows to Drupal node types. Workflows are made up of workflow states. For example, a workflow with the states Draft, Review, and Published could be assigned to the Story node type. Transitions between workflow states can have actions assigned to them. In our example, we could assign an action so that when the story moves from the Draft state to the Review state an email is sent out. Another action could be assigned to the transition from Review to Published so that the node's status is set to Published (and becomes visible on your website).

Workflow requires the Actions module: http://drupal.org/project/actions

The actions module allows the configuration of Drupal actions. A Drupal action is a specially written PHP function whose parameters are configured through the web. For example, the Send Email action has parameters Recipient, Subject, and Message. You could fill in MrFoo@example.com for the recipient, Hi for the subject, and Hello, Mr. Foo for the message to create an instance of the Send Email action. This action instance could then be fired by a module at appropriate times when you want Mr. Foo to get an email.

http://petermoulding.com/technology/content_management_systems/drupal/

petermoulding.com/web_architect