When creating new panelizer layout for a teaser mode (or other views modes) on either the Space or Section content types, the taxonomy selector defined in the buttons module fails.
Steps to reproduce:
Create Panelizer layout for Space node type using teaser mode
1) Go to panelizer config at admin/config/content/panelizer
2) Navigate down to the "Space" content type and check off the boxes under "teaser" to create a new teaser layout for spaces.
3) Click "list" and create your default layout for teaser and save.
Now go to administer the "space" type taxonomy vocab
4) Add a new term
5) Now select the term's layout.
You'll see there's only one layout option available (Default), and others have disappeared.
Patch to follow.
Comment | File | Size | Author |
---|---|---|---|
#1 | openatrium.code_.2072159-1.patch | 3.12 KB | CMS Dude |
Comments
Comment #1
CMS Dude CreditAttribution: CMS Dude commentedCreated a patch for the modifications that solve the issue in my environment.
Needs review.
Comment #2
mpotter CreditAttribution: mpotter commentedRemoving the "if (isset($form['field_oa_node_types']))..." lines is a problem. Those lines are needed to prevent errors/warnings when the fields do not exist on the form. So not sure why you got rid of those.
Comment #2.0
mpotter CreditAttribution: mpotter commentedUpdated issue summary.
Comment #3
Argus CreditAttribution: Argus commentedAny progress?
Comment #4
Argus CreditAttribution: Argus commentedPostponing because of inactivity.
Comment #5
mpotter CreditAttribution: mpotter commentedOK, I looked into this a bit more. I was able to reproduce the original problem. However, the patch included a bunch of other stuff that doesn't seem related (as mentioned in #2). Also, oa_buttons has been refactored and some of the code now lives in oa_core.
I was able to take a piece of the patch and apply it to oa_core and fix the original problem. This was committed in b0c20bd. You can re-open this issue if there is still a problem. If you other changes in the patch were meant to fix other issues, please open new issue tickets for them.