Use IPE features to allow Panelizer to edit default or overridden panel for an entity

On the top, I think this is a great addition to Panelizer and solves a problem that many site administers have in understanding what happens when they use the IPE. I chatted with a few UI folks around this and wanted to propose that we switch around a bit how the button placement works:

Change One: Remove Top Level Buttons

The concern here is that these buttons might not be totally appropriate for the main IPE bar. Here are some reasons:

• Drupal Jargon - The idea of a "Panelizer state" is pretty Drupal l jargoning and will likely confuse users (especially of Drupal products) who don't quite know what that is.
• Frequency - The options to see what the Panelizer state is and the ability to revert are not super frequent options. It might be better to put them somewhere less prominent than on every page.
• Consistency - These options are going to switch around a lot depending on how the backend is setup (Page Manager vs Panelizer, Custom vs Default) which makes sense to developers but will confuse end users (especially of Panopoly) who just want everything to be a Panel.

Change Two: Move Options Under Customize

We can move these options (when appropriate) under the save bar so that they only appear when they are able to be used. Some reasons:

• Consistency - This keeps the IPE experience one where you hit "Customize" to change the page for every page (although we might want to change that language to "Change this Page" instead of Customize.
• Actionable - These options are now exposed where they are most actionable. You can do your work in the IPE and then decide how to save it (customize or default) or cancel it (revert or cancel).

Re Feasibility - I am happy to help dig into the code to see if it might be possible to do this on the save/cancel side if you point me in the right direction. I think that having this done at this step will clean up the UI a lot.

Re "Panopoly Page" - This is actually just the name of the content type. I think it would be nice to include which template/default is being saved.

This is a big UX improvement; I'm a friend of anything that saves me from explaining to site builders that default Panelizer displays are created in Config > Content Editing > Panelizer.

If #5 is possible i think that would be a nice improvement.

The only thing that i think might be worth considering is appropriately permissioning these two new buttons so we can control their exposure. I think the panels/ipe experience has done a really good job providing the barebones and simplest set of config options that are most relevant to everyday end users and light site builders. Furthermore, the IPE experience is a significant improvement over the base Drupal paradigm so it would be a shame to fall prey to the same problem that has plagued Drupal aka too many "Intimidating" buttons that scare many users away.

I spent about an hour playing around with this and I think things are looking pretty good. There are a couple issues I was able to find though.

• After creating a new user role with limited permissions, I was still able to edit and save both entity-specific and default layouts for content types which I did not have the required permissions for. I can provide a full list of permissions the user role had if needed.
• I wonder if using the word "layout" in the IPE buttons would be an improvement. My specific concern is around the "Save as custom" button. The button text seems a bit confusing, I wonder if "save as custom layout" and "save as content page default layout" is an improvement.

Actually marking this back to needs review -- as it would be great to get someone else to verify the permissions issue.

I also did some review and think this is a great improvement and really solid addition to the Panelizer/Panels IPE magic. Just for completeness, I updated the Panels patch to add in the appropriate icons and marking RTBC.

In terms of the the language, I think the shorter pattern makes sense. The concept of "custom" and "default" make sense to a lot of users and this text can be changed on the theme layer if there is such a need.

In terms of the permissions, I assume the permissions patch will only allow the "Save as default" option to folks with that permission.

I have been playing around with this more and was wondering if it might make sense to implement a JS "confirmation" for reverting to default or saving as default. Those are pretty powerful operations and might deserve a slightly higher level of confirmation. It is pretty easy to accidentally hit "Save as default" instead of "Save as Custom".

Re-rolled the panelizer patch against the latest -dev and added confirmation dialogs for the 'save as default' and 'revert to default' buttons. (Wording could perhaps use some work, I'm not sure how general it needs to be.) Thanks for the patch, this is very useful functionality.

it's in there as an onclick attribute of each form element - apologies if this isn't the best way to do it, I was just looking for a quick way to add the functionality and keep this issue moving :)

duly noted! Happy to re-roll, can you give a hint as to your preferred method? (even just to say "figure out how it's done for the cancel button and do it that way" is enough)

@acrollet: what you want is proper event binding added via jQuery. See the javascript behaviors documentation at http://drupal.org/node/756722#behaviors

Sorry if I should be creating a new issue for this.

Editing the default panelizer state from within IPE is not working for me. I am using the following versions of modules:

panelizer 7.x-3.0+0-dev
panels 7.x-3.3+33-dev
ctools 7.x-1.2+31-dev

If I override a particular node I can save as custom and revert to the default through IPE just fine but when I try to save as default it just saves it the same as it was prior to making any changes. Thanks.

I am confirming the issue for #27. I am using the same set of modules:

• panelizer 7.x-3.0+0-dev
• panels 7.x-3.3+33-dev
• ctools 7.x-1.2+31-dev

When I attempt to save the panel as the default I get the confirmation screen several times. If I click "OK" the panel does is not updated and the default panel is also not updated.

No, I am not using entitycache. I was actually able to reproduce it on a clean install.

This appears to fix the issue on a clean install using the default view mode.

I am still having some issues on a different site with a different view mode but I will do more testing tomorrow to see if it is just me. Thanks!

Ok, so it seems to work great on a clean install. The other site I am testing is a new site built with a custom install profile and my content types and panelizer defaults are all packaged up as features with demo content. When I try to save as default through ipe it appears to work at first but if I leave the node and come back it reverts to the defaults stored in the feature.

If I go into /admin/config/content/panelizer and save the panelizer settings for that particular content type without making any changes it will then work through the ipe. Any ideas?

Not sure if this is the right place to report this, but I'm noticing that I get a looping prompt when I place new content in a panel using IPE and try to save for default. Using ctools, panels, panelizer development versions. This prevents saving entirely. It works just fine for default when rearranging content panes, though I havent tested with other panelizer templates yet.

The issue I was having in #34 seems to be resolved now with the latest dev versions of ctools and panels and panelizer 7.x-3.1. Not sure which commit solved this issue but it works now.

@rerooting - I think your issue in #36 might be solved with the patch #1982654: Repeatially asked to confirm when trying to save a default for a node type

Closing this issue on the following grounds:

• feature request has been implemented.
• a potential solution to a follow up issue has been a identified in another closed issue.
• no feedback from the bug reporter (@rerooting)
• no further activity on this issue for 6 months.

Please open a new bug or support issue if you are still having problems with this.