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.
Since I updated panelizer to the dev then beta I have added a content type and panelized it. However for this new content type I get "Access Denied You are not authorized to access this page" when I try to go to the settings, context, layout, and content pages. However I can still access these pages for the older content types.
Panelizer - 7.x-3.2-beta1
Panels - 7.x-3.5
Chaos tools - 7.x-1.6
Comment | File | Size | Author |
---|---|---|---|
#13 | panelizer-n2421321-13.patch | 4.56 KB | DamienMcKenna |
Comments
Comment #1
DamienMcKennaDid you run the database updates? Some of the menu paths changed.
Comment #2
tisteegz CreditAttribution: tisteegz commentedI managed to get it to work and can replicate the issue. I had run all the updates so I tested again to see if I could replicate.
I removed panelizer from the content type which wasn't working (making sure to delete all associated variables) and re-enabled it from the actual content type edit page instead of admin/structure/panelizer and it seemed to work. So to see if I could replicate I went to admin/structure/panelizer and enabled panelizer on basic pages and I get the same issue of not being able to access the pages. I can now access the pages for the original content type which was not working so I don't think it is a path issues.
So essentially when I enable panelizer from admin/structure/panelizer it doesn't work and when I enable it from admin/structure/types/manage/[content_type] is seems to work fine.
Comment #3
DamienMcKenna@tisteegz: Thank you for tracking that down, it'll help track this down.
Comment #4
DamienMcKenna@tisteegz: When you set this up, what options did you enable? Specifically, did you select the "Provide default display" option?
Comment #5
tisteegz CreditAttribution: tisteegz commentedI enabled PANELIZE and PROVIDE INITIAL DISPLAY. :)
Comment #6
bryancasler CreditAttribution: bryancasler commentedCan confirm the issue. So far the only show stopper problem with the beta I've run into is this one. DamienMcKenna are there any additional details I can provide that would help troubleshoot this?
Comment #7
DamienMcKennaUgh, I can confirm this happens.
Bumping it to 'major'.
Comment #8
DamienMcKennaCan you please try the latest -dev release?
Comment #9
DamienMcKennaI'm unable to reproduce this using the current -dev release.
Comment #10
bryancasler CreditAttribution: bryancasler commentedI installed the dev release, ran update.php, flushed site cache, then rebuilt permissions. Dev release fixed it! But 'possibly' surfaced a new problem or discovered an old one. This could be a case of an inaccurate error message.
After updating I went to the configuration page (admin/structure/panelizer) linked to from the Modules list. I have two Panelized node types. "Page" and "Blog".
"Page" links worked! Every single one loaded instead of giving me the "Access denied..." error.
"Blog" links did not, I was still getting "Access denied..." errors.
To fix the blog links I went to "admin/structure/types/manage/blog" and scrolled down to the "Panelizer" tab. From there I checked the "Update existing entities to use this display" for each view mode and hit the "Save content type" button. That fixed it! Now everything is working as expected.
Will report back any other issues, but as of this moment I'm a happy camper.
Comment #11
DamienMcKennaLets leave this one open, because there are still some problems somewhere.
I suspect that some settings were borken somewhere and it's having subtle problems.
What might be useful is, if you're seeing any problems with this please post a your Panelizer variables for that entity bundle, that should help identify what's misbehaving.
Comment #12
bryancasler CreditAttribution: bryancasler commentedWill do!
Comment #13
DamienMcKennaI think this should solve it. The problem seemed to be that the 'selection' variable was being set to 0 to indicate the first item in the selection. I've changed a few things to avoid this - the variable is now only set if there's an actual value, otherwise it uses the default. It also includes an update script to fix existing values.
Comment #15
DamienMcKennaCommitted. Please re-open if the issue continues.
Comment #16
gmclelland CreditAttribution: gmclelland commentedSorry, I think I need to reopen this.
Try Panelizer 3.x-dev on http://simplytest.me/project/panelizer/7.x-3.x
- Goto admin/structure/panelizer
- Check the following for Basic page - Full page override
-- Panelized
-- Provide Initial Display
-- Allow Panel Choice
-- Save
-- Under "Basic page" click the "list" link
-- Access Denied
Hope that helps
Comment #17
gmclelland CreditAttribution: gmclelland commentedSorry, I'm switching this back to "Fixed". I believe another issue #2470257: Bad redirect and/or bad menu_local_action introduced the problem I reported.