If I make a user with these permissions:

add items to deployment plan
deploy items

then the node's tab lets me add my new node to the plan. Then after adding it I go to an access denied page.
Also, I don't see where I can go to actually deploy the things I have the permission to deploy!

Comments

joachim’s picture

joachim commented

Also, if I go directly to node_operations/deploy_now/NID, I can't see the log result after having deployed.

gdd’s picture

gdd
he/him
Primary language English
Location Portland, OR
commented

I will look into these issues, the permissions were definitely only put together in a basic way and I admit to not testing them very hard (there are other problems I've encountered as well.) If you have any suggestions I'd love to hear them.

joachim’s picture

joachim commented

My use case is that I'd like a non-admin user to create or update a node, and then deploy it to the relevant sites (see #622022: Add Views Bulk Operation support for node selection for more on what I'm trying to do).

So I've got round this partially with a quick hack of hook_link, adding a link to node_operations/deploy_now/NID.
This would be more consistent as a link in the Deploy tab, say 'deploy this node immediately'. hook_link was just quicker to set up for my current test setup :)

As for deployment plan, the problem is that admin/build/deploy is aimed at admins. Selectively removing the edit and delete links would be a real pain and it's not how Drupal admin pages are meant to work!
Maybe something like nodequeue does it -- which I can't remember offhand, but that has a separation between admins who may delete a queue and change its settings, and users who may only change its contents.