Closed (fixed)
Project:
Blocker
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
26 Mar 2013 at 19:26 UTC
Updated:
22 Nov 2014 at 13:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
simon georges commentedPatch provided.
This patch is part of the #1day1patch initiative.
Comment #2
randallknutson commentedFor the blocker_ui permissions I'm good with this approach but I'm thinking we could either tie the permissions into node edit permissions or mirror those. The idea is that an end user with permission to edit a node should have the ability to change the blocks on that page as well but not other nodes.
Comment #3
simon georges commentedEither tying them to the node or adding them (something like (user_access("edit not") && user_access("manage blocks")) is totally fine by me, as long as it's possible to give access to content editors that shouldn't alter the site configuration.
Comment #4
randallknutson commentedUpdated in ed6cf64
I tied it to the node permissions for now. I'm open to making this more extensive and customizable but this is better than the high level admin that was there.
I'll leave this open to discuss even better options moving forward.
Comment #5
KroKroDile commentedHi,
Here a patch updated (the code has changed).
KroKroDile
Comment #6
KroKroDile commentedBetter with clean code
Comment #7
simon georges commentedChanging status back to "Needs review", to have maintainer feedback.
Comment #7.0
simon georges commentedFix grammar.
Comment #8
kyletaylored commentedThis worked for me. +1
Comment #9
kyletaylored commentedTested and works well.
Comment #10
kyletaylored commentedFixed