Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Module:
Chaos tool - 7.x-1.0-rc1
Description:
When on the panel content section, you're able to click on the pane or regions setting gear to show you the configuration options (styles, visibility rules, etc). If you're not logged in as a super user (uid 1) then the style option doesn't appear in the configuration menu for both pane or regions.
The account that's not able to see the style options, has all permissions granted. Is there something I'm missing?
Thanks,
Droath
Comment | File | Size | Author |
---|---|---|---|
#16 | panels-style-perms-1313642-15.patch | 374 bytes | steveoliver |
#5 | panels-style-perms.1313642-5.patch | 537 bytes | droath |
#4 | panels-style-perms.1313642.patch | 527 bytes | Jon Pugh |
#2 | panels-style-perms.1313642.patch | 920 bytes | Jon Pugh |
Comments
Comment #1
Jon PughMissing 'administer panels styles' in hook_perm... patch on the way...
Comment #2
Jon PughPatch attached.
@droath: to fix your problem you'll have to apply the patch and then give a role the permission "administer panels styles"
Comment #3
merlinofchaos CreditAttribution: merlinofchaos commentedDOH. I really forgot to put the perm in? Man that's sad!
Comment #4
Jon PughRe-rolled on latest dev release
Comment #5
droath CreditAttribution: droath commented@careernerd, Thanks!
I got an error when applying the patch. So I re-rolled patch #4, if anyone else is having problems.
Comment #6
Letharion CreditAttribution: Letharion commentedComment #7
BenK CreditAttribution: BenK commentedJust checking back in.... any progress on this?
Comment #8
Letharion CreditAttribution: Letharion commented@BenK You can clearly see the progress in this issue, so I don't know what you are asking for.
You are welcome to try out the patch and report back how it works for you.
Comment #9
EmanueleQuinto CreditAttribution: EmanueleQuinto commentedPatch works for me.
Comment #10
Letharion CreditAttribution: Letharion commentedComment #11
qylie-1 CreditAttribution: qylie-1 commentedThanks! Worked like a charm!
Comment #12
Letharion CreditAttribution: Letharion commentedhttp://drupalcode.org/project/panels.git/commit/5bdd2f069c91add0d07e9d6e...
Comment #13
Letharion CreditAttribution: Letharion commentedhttp://drupalcode.org/project/panels.git/commit/5bdd2f069c91add0d07e9d6e...
Comment #14
Letharion CreditAttribution: Letharion commentedComment #16
steveoliver CreditAttribution: steveoliver commentedI didn't see a 6.x variant of this issue, so here is a patch for the same issue in D6 (against 6.x-3.9).
Comment #17
merlinofchaos CreditAttribution: merlinofchaos commentedMarking nr to prevent loss
Comment #18
pcorbett CreditAttribution: pcorbett commentedWorks for 6.x-3.10.
Comment #19
merlinofchaos CreditAttribution: merlinofchaos commentedCommitted to D6.
Comment #21
mgerbaultThis problem persist in Drupal 6 version.
Comment #22
merlinofchaos CreditAttribution: merlinofchaos commentedIt was committed here: http://drupalcode.org/project/panels.git/commit/bab933ea5fd682a06eb5fe8d...
Comment #23
EvanDonovan CreditAttribution: EvanDonovan commentedCould a new release of Panels be made that includes this patch? People are missing out on a crucial bit of functionality because they assume the stable release has all the required permissions but it is from before this patch was committed.