Publish Session nodes when status is changed to accepted [#2281425]

Problem

When a Session node is create it is unpublished by default. Users with the necessary permissions can then change the status of the session based on whether the session has been declined, accepted, featured, etc. Sessions which have been marked as "accepted" or "featured" don't display in any of the views unless their publish state is also updated to "published".

Proposed Solution

It would be great if Session nodes were published automatically when their status is changed to "accepted" or "featured". This could be accomplished with a rule.

Comment	File	Size	Author
#9	cod_support-publish_accepted_sessions-2281425-8.patch	2.48 KB	mrconnerton
#9
#8	cod_support-publish_accepted_sessions-2281425-7.patch	2.47 KB	mrconnerton
#8
#2	cod_support-publish_accepted_sessions-2281425-2.patch	1.89 KB	genjohnson
#2

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

genjohnson CreditAttribution: genjohnson commented 6 June 2014 at 16:26

Patch coming.

Comment #2

genjohnson CreditAttribution: genjohnson commented 6 June 2014 at 16:38

File	Size
cod_support-publish_accepted_sessions-2281425-2.patch	1.89 KB

Here's a patch. A sessions which have been marked as "accepted" or "featured" should be published when the node is saved.

Comment #3

fullerja CreditAttribution: fullerja commented 6 June 2014 at 17:14

Status:

Active

» Reviewed & tested by the community

Works on both the Accepted and the Featured choices.

Comment #4

japerry

KVUO

CreditAttribution: japerry commented 8 June 2014 at 05:46

Status:

Reviewed & tested by the community

» Needs review

Jason was talking about perhaps keeping the publish rule in code so people cannot alter the feature. I'm okay with making this a rule, but I'd like some opinions on if this functionality should be alterable or not.

Comment #5

genjohnson CreditAttribution: genjohnson commented 9 June 2014 at 18:19

I can't think of a use case where I would want accepted sessions to be unpublished, so I'm ok with this functionality not being alterable.

Comment #6

mrconnerton CreditAttribution: mrconnerton commented 17 January 2015 at 19:02

Status:

Needs review

» Reviewed & tested by the community

I think we need to keep this flexible as a rule. I've done one conference for a non-profit higher ed group that wanted to be able to moderate the sessions, but nothing was actually published until a few months later. In this case they would want the ability to disable this rule.

I vote we put this back to RTBC and once it is commited we add a documentation page about it.