Download & Extend
Panels » Issues

Ability to lock regions from IPE completely

Posted by emattias on October 24, 2012 at 8:47am
Project:Panels
Version:7.x-3.x-dev
Component:In-Place Editor (IPE)
Category:feature request
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

We want to be able to make only a few regions "IPE enabled". We managed to do this by using our own intermediate pipeline that overrides render_region and render_pane methods and runs the panels_renderer_standard or panels_renderer_ipe equivalent depending on if we want it to be IPE enabled or not.

It works great except that we don't have a way to configure if we want the region to be IPE enabled or not. I'm thinking that copying the locking functionality of panes to regions would be the way to go. I might do a patch for that. If that is a bad idea, please let me know..

Login or register to post comments

Comments

#1

Posted by emattias on October 24, 2012 at 8:48am
Status:needs work» active

#2

Posted by merlinofchaos on November 1, 2012 at 6:06pm

Panels already supports locking regions. Do you need more than it currently allows?

#3

Posted by Letharion on November 4, 2012 at 3:15pm
Status:active» postponed (maintainer needs more info)

#4

Posted by emattias on November 16, 2012 at 10:13am
Status:postponed (maintainer needs more info)» needs work

What do you mean by locking regions? Is it possible to do this(and if so, could you please hint to how):

When an editor clicks "Customize page":

  • Only the non-locked regions get the IPE toolbar at the top of the region.
  • You can only add or move content into the non-lock regions.
  • The locked regions appear exactly the same in "Customize page" mode as the standard renderer outputs it.

My thinking is to have a "Locking" dropdown header when you press the cogwheel for the region. Like you have for the cogwheel menu for panes.

#5

Posted by emattias on November 16, 2012 at 10:14am
Status:needs work» active

#6

Posted by emattias on December 14, 2012 at 6:36pm

Panels already supports locking regions. Do you need more than it currently allows?

Do you mean locking panes in a region? Because that's not what we need.

We need to be able to lock the region from IPE completly. So on the same panel when you press "Customize page", some regions get the IPE toolbar and you can add/remove/re-order panes and other regions render like they did before pressing "Customize page". So the locked regions look and behave like they aren't "IPE enabled".

Semantic/UX question: Should it be called that you "lock" the region or that you select the renderer for that region? (Like you select style, etc.)

#7

Posted by emattias on January 31, 2013 at 4:07pm

We don't have time to create a patch for this atm, so I created a Panels Selective IPE Sandbox that provides a new pipeline which will only "IPE Enable" specified regions (which can be set through a db variable).

It's has no extra ui that is talked about in this issue, but it does make it possible to have only part of the page be IPE editable.

nobody click here