as pointed out in http://drupal.org/node/90436#comment-165208, there's no way for regular project maintainers (as opposed to folks with 'administer content' permissions) to unpublish their own release nodes. this would be desirable (though not urgent).

i don't think this can be done solely via settings. i believe i'd have to add some special case code, like adding the "publish" checkbox on the release edit form if folks don't have full permissions and see it already...

Comments

drewish’s picture

drewish commented

+1 to this ;)

heine’s picture

heine commented

It would be nice (note: nice, not essential) that even admins can set nodes to not autopublish. My current workflow is to create a release node and immediately publish a prepared security announcement. It would be nice to have some slack (and an opportunity to test the tarball for example).

RobRoy’s picture

RobRoy commented

FYI, I just created super small module at http://drupal.org/project/override_node_options which allows users to override the default publishing options for nodes they can edit without giving them the 'administer nodes' permission. Maybe this could help out in the meantime. For D6 maybe we could flush out the perms a bit more like this.

mikey_p’s picture

mikey_p commented
Version: 4.7.x-1.x-dev » 5.x-1.x-dev

I don't know the d.o setup and perms well enough, but are you basically saying:

if (!user_access('administer nodes')) {
  if (user_access('unpublish own release') && ($node->uid == $user->uid)) {
    // form goodness goes here
  }
}

maybe I'm missing something, but this seems to be all that's needed. Are there additional conditions you want to check for? The only thing I could think of, was do not unpublish nodes when there is only one release node per project, but I can think of reasons why that's not a good idea either (support requests.."why can't I delete my release?").

The only other thing I can think of is what to do with the unpublished node. Will the project owner have to ask an admin to re-publish it? What will happen if the user tries to create a new release node to replace the unpublished one...will d.o become flooded with unpublished release nodes? Do we want to give project owners a way to see their unpublished release nodes, and let them publish them at will?

Sorry for so many questions, just trying to think through some of the implications here.

mikey_p’s picture

mikey_p commented

With new abilities to choose 'supported,' 'recommended,' etc. is this still a needed feature? If not, perhaps close this out.

aclight’s picture

aclight commented

It's still only possible to set supported, recommended, etc. on a per branch (or per major version) basis. So there could still be the use case for users being able to unpublish individual release nodes. But it's probably even less urgent than it was before.

drumm’s picture

drumm
he/him
Location NY, US
commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Releases should never be unpublished. The other ways of marking support are preferred, and we should not try to make releases disappear in any way.