workflow

Hi, I'm just starting out with OA2 and was wondering if it's possible to create a multi-stage workflow using the standard Drupal workflow module? I've tried installing the workflow module and using it to set up a review process for a new node type, but the workflow options don't seem to be visible when editing a node. Is this expected behaviour when using the workflow module with OA2?

Hi there,

I would like some advice on how to best go about achieving a dev-stage-pro workflow using BOA across multiple servers.

I currently have 3 VPS', (2 with Linode, and another with a local provider). I also have a HP Proliant, at home, that i'm wanting to repurpose as a dev server and throw into the mix.

I was hoping to get Irish drupalers impressions on the various workflow modules available for drupal 7 both their good, bad and ugly sides.

I'd be particularly interested to hear if its possible to set "target processing times" for transitioning from 1 state to another to (gently) remind the necessary user there is content that requires their attention and avoid a backlog building up in the pipeline/workflow, all the better if I could configure different target times for different transitions.

For those using things like linkit, or ckeditor_link (these modules allow you to have links to internal pages within your body), is there any module that tracks these inline links?

What I'm getting at, is that if the inline links are tracked, then we can do something about it, before the linked node is unpublished or deleted, i.e. display a warning, or ask the user to remove the link and rewrite the content of the referring page.

Hopefully this is just my inexperience.. I had TAC and Workbench installed, Since workbench handled the state changes but didn't handle if a user could see the content, I decided to see what other options there were.

I have now installed workflow, TAC and rules. I am using TAC to control if content is seen by roles. I have created three workflow states. Draft, Needs Review, Published.

I have created rules so that if a node changes from published to needs review, then an action of un-publishing that node should be performed. But when I perform this action nothing is happens.

Have you ever wished core would track the date/time a node was published, instead of just when it was created and modified? Well, now is your chance! There is a patch in the issue queue, but it needs review and time is running out before feature freeze. Please get involved.

http://drupal.org/node/1838918

We at Aller Media in Norway are implementing Drupal7 on some of our high traffic sites and we have the need for an advanced frontpage node administration module.

We have this functionality in our legacy CMS we developed in-house, and we plan to port this functionality to Drupal. I have researched quite a bit on this topic and have not found such existing functionality in Drupal. Although it could be hacked together with existing modules like Nodequeue/Draggable views, Scheduler, Views, Blocks and the Dashboard, it still does not satisfy the requirements.

Here is our requirement:

This is a proposal for a module that can accomplish a more advanced node ordering for frontpage.

Features

• Birds eye view of all nodes currently on frontpage, and all nodes in different workflow statuses.
• Drag and drop nodes onto the frontpage queue to any position to publish that node to that position.
• Real-time statistic numbers for each node to compare how well they are doing on the frontpage.
• Drag and drop to change positions of nodes in the queue.

I'm wondering if anyone's aware of a module that lets you set up, much like how the alternative 404 & 403 feature works in core (set in Site configuration), the display of an alternative page if a page is accessed which may exist, but which might not be published.

This would of course only apply to those users that didn't have the "view unpublished content" permission set.

What's the best method to display a listing of content items filtered by workflow state?