Hi everybody,
I have a panel page which shows a view and a couple of custom content boxes. I'd like my editors to be able to:
- use the IPE
- disable drag&drop
- only edit custom content boxes but not access settings/edit of views.

I am willing to develop a plugin/module to provide per-pane access permission, but I'd need some indications from more experienced developers.

Thank you very much,
Francesco

Comments

merlinofchaos’s picture

You would most likely need to make a clone of the IPE that strips out the functionality you don't want. The important bits will be making sure your new IPE has its own pipeline and doesn't enable the drag & drop javascript will still doing everything else.

Controlling which kinds of content are editable could be tricky, but if you're willing to hardcode it, you can remove the Edit links in the theme function -- I think you get the entire $pane there so you can look at $pane->type and $pane->subtype to see if it's something you want to discard.

merlinofchaos’s picture

Also see http://drupal.org/node/921048 -- some of the advice there is relevant here.

flevour’s picture

I am impressed the issue you mentioned was opened just yesterday, this community rocks and your quick answers are incredibly helpful. Thanks.

Controlling which kinds of content are editable could be tricky, but if you're willing to hardcode it, you can remove the Edit links in the theme function -- I think you get the entire $pane there so you can look at $pane->type and $pane->subtype to see if it's something you want to discard.

I was wondering if there was a way to hook into all pane configuration forms to add a role access configuration form, but I infer it might not as easy as it seems.
Another possible approach could be adding a per-variant access tab (sitting there below "Summary", "General", .. "Context" etc) which gives options to restrict access by role to currently configured panes.

I am just elaborating to see if it's possible to make an effort that:
1. might be shareable and re-usable by the community
2. at the same time does play nice with current options; in a certain way I don't like the idea of sharing something mutually exclusive to IPE or the other core renderer(s).

Letharion’s picture

Status: Active » Fixed

Merlin has since this discussion written a blogpost http://www.angrydonuts.com/panels-ipe-the-future with some similar thoughts in it. With that, I'm closing this as fixed. It can be re-opened if someone tries to implement this and has questions/patches etc.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.