The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I get this error when importing configurations on site install.
So it seems the permission "administer panelized node article content" is problematic. I inspect its export code and also compare it to "permission.administer_panelizer" which was able to export just fine. Here they are side-by-side:
They are virtually identical in their properties and dependencies. I'm not sure where to begin to debug this. For now I'm commenting out the "faulty" permissions.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 1866966.panelizer_configuration.7.patch | 2.91 KB | dagmar |
| #6 | 1866966.6.patch | 1.49 KB | GDrupal |
| #3 | 1866966.3.patch | 1.47 KB | GDrupal |
| #2 | 1866966.2.patch | 1.93 KB | GDrupal |
| Screen Shot 2012-12-14 at 10.32.24 AM.png | 30.37 KB | helior |
Comments
Comment #1
dagmarI think this is similar to what happen with the node permissions. The panel should be a dependency of the permission, this means, the panels must exist before try to create the permission for that panel.
Working on this.
Comment #2
GDrupal commentedRelated to this issue there is a problem in the order which permissions are processed. Permissions have to be imported at last since could depend on other component to create them. Let fix this and see how it goes.
Comment #3
GDrupal commentedThe last patch does not change anything so lets try first to add some feedback when we try to update a non existing permission.
Comment #5
dagmarComment #6
GDrupal commentedComment #7
GDrupal commentedLast patch committed This avoid the process to abort give the user some feedback but we still need to fix the issue itself.
Comment #8
dagmarSo, I think this should fix the issue. Now all permission related to panelizer include the panelizer as a dependency.
Comment #9
dagmarCommitted and Pushed to 7.x-2.x.