Steps to reproduce:
1. Create new content type. Save it.
2. I've exported content type to Features (probably not relevant).
3. Edit again and enable two checkboxes at /admin/structure/types/manage/%: 'Panelize' and 'Full page override'. Save it.
4. Additional Panelizer tab is available, so I'm going to: Administration » Structure » Content types » MyContentType » Panelizer » Full page override
5. The page is not found: The requested page "/admin/structure/types/manage/%/panelizer/page_manager" could not be found.
Workaround is to enable: 'Provide an initial display named "Default"' at /admin/structure/types/manage/%, then then 'Full page override' is available as expected.
Disabling the option, goes off again and at /admin/structure/types/manage/%/panelizer/page_manager/content it gives: Access denied (You are not authorized to access this page.) which is pretty weird, as I'm logged-in as admin.
This was reproduced on two different environments.
Comment | File | Size | Author |
---|---|---|---|
#9 | panelizer-n2546906-9.patch | 14.74 KB | DamienMcKenna |
|
Comments
Comment #2
DamienMcKennaComment #3
DamienMcKennaThe logic that controls whether this page is available is too closely tied to whether there's an existing display, it should be tied to what the configuration options are.
Comment #4
DamienMcKennaSo the problem is that the access is determined by panelizer_default_settings_page(), which returns MENU_NOT_FOUND if no page is suitable for the given path, instead it'd be better to return a simple message.
Comment #5
DamienMcKennaA slightly better message.
Comment #6
DamienMcKennaThis fixes the subpages so they give the same message if no default display is available, rather than throwing 403 errors.
Comment #7
DamienMcKennaTests!
Comment #9
DamienMcKennaReverted changes to the node_revisions test file.
Comment #11
DamienMcKennaCommitted.