In #2784981: Remove confusing legacy permissions from Panels Node, legacy permissions for administering panel nodes were removed, but the patch didn't remove one of the usages of a removed permission "create panel-nodes". The coming patch resolves this.

This may even be critical since without this patch only user 1 can create new panel nodes.

CommentFileSizeAuthor
#8 panels-fix-node-create-perms-2786285-8.patch902 bytesbkosborne
#4 panels-fix-node-create-perms-2786285-4.patch508 bytesbkosborne
#2 panels-fix-node-create-perms-2786285-2.patch512 bytesbkosborne
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

bkosborne created an issue. See original summary.

bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
CreditAttribution: bkosborne commented
Status: Active » Needs review
FileSize
panels-fix-node-create-perms-2786285-2.patch512 bytes
bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
CreditAttribution: bkosborne commented
Related issues: +#2784981: Remove confusing legacy permissions from Panels Node
bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
CreditAttribution: bkosborne commented
FileSize
panels-fix-node-create-perms-2786285-4.patch508 bytes

Typo.... although I also don't see where this permission "create panel content" is defined. I am going off the mapping in the panel_node.install file. Will dig deeper...

japerry’s picture

japerry
Location KVUO
CreditAttribution: japerry commented
Priority: Major » Critical
Parent issue: » #2786071: Plan for Panels 7.x-3.7 release
bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
CreditAttribution: bkosborne commented
Status: Needs review » Needs work

The patch that broke this mapped the old permissions to new ones, but I can't find the new ones defined anywhere in code?

bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
CreditAttribution: bkosborne commented
Status: Needs work » Needs review

Ok, I understand. The new ones are dynamically defined. This patch should work fine.

bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
CreditAttribution: bkosborne commented
FileSize
panels-fix-node-create-perms-2786285-8.patch902 bytes

Actually this is better, since it accounts for the admin permission as well.

bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
CreditAttribution: bkosborne commented

And as mentioned here, any features that had the legacy permissions featureized will throw warnings that no modules define those permissions. I think the warnings are harmless and the feature just needs to be updated to remove those permission assignments.

  • japerry committed aade982 on 7.x-3.x authored by bkosborne 
    Issue #2786285 by bkosborne: Access denied 403 when trying to add panel...
japerry’s picture

japerry
Location KVUO
CreditAttribution: japerry commented
Status: Needs review » Fixed

Yah I think #8 is correct. That was a small but critical error. Fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

aaron.ferris’s picture

aaron.ferris CreditAttribution: aaron.ferris commented

I've just come across this issue after updating to Panels 3.6 a week or so ago, I was seeing some problems with older user accounts still not being able to add new panels after patching. New user accounts with the relevant permission was fine.

The solution was to rebuild permissions, in case anyone else notices the same.

vijaycs85’s picture

vijaycs85
Location London, UK
CreditAttribution: vijaycs85 as a volunteer commented

Thanks for fixing it. We just hit this issue. Thanks @aaron.ferris for work around in #13.