Not sure if this is a Contextual links issue, or IPE, or Panels or Panelizer...
Anyway to replicate the problem:
1. Klick the IPE edit button on an Panelized page.
2. Click save.
3. The Contextual link on any item will have the "destination" query param set to panels/ajax/ipe/save_form/panelizer:node:23:page_manager
The whole url looks like:
http://mysite.local/en/information#overlay=sv/node/31/edit%3Fdestination...
What happens is that after you save that content you will end up on panels/ajax/ipe/save_form/panelizer:node:23:page_manager that will print json data to the browser.
Comments
Comment #1
gmclelland commentedThis might be related to this issue - see #1621014: Contextual links and other JavaScript behaviors on panes don't work after clicking "Cancel" in IPE?
Comment #2
gmclelland commentedI can confirm this is still an issue and the #1621014: Contextual links and other JavaScript behaviors on panes don't work after clicking "Cancel" in IPE is completely separate issue.
Comment #3
Raumfisch commentedI can also confirm the described error as well as #1621014 is still present. Is there any progress in in this issue?
Comment #4
roam2345 commentedThis is effecting us as well.
For us its polls, when we add a poll to the page and then click on the vote widget we get redirected to a page (panels/ajax/ipe/save_form/panelizer%3Anode%3A3%3Afull) full of json,
Comment #5
adamsro commentedSo when the panel is saved and re-rendered on
panels_renderer_ipe.class.php:288it makes a call to drupal_get_destination in contextual.module which uses $_GET['q'] as the destination, in this case the ajax callback instead of the page url.As a temporary hack I've added
$_GET['destination'] = '';abovepanels_renderer_ipe.class.php:288which will redirect to the home page, but at least saves the panel contents correctly.To do it right I think we'll need to print the pages url somewhere around the ipe buttons and send it with the ajax call. I might work on a patch for this soon.
Comment #6
Angry Dan commentedSee attached patch.
The simplest way I could see to fix this was to just set a destination on the original links, then everything follows through nicely from there. No hacks needed.
Comment #7
adamsro commentedWorks, gj. I'm a bit disappointed I missed that.
Comment #8
Angry Dan commentedThis is working for adamsro and I've had it in production since I wrote the patch, so I'm saying RTBC, unless anyone wants to object?
Comment #9
Vegan4Life commentedThe patch in #6 works perfectly for me as well. Thanks a lot! I've been having this issue for months.
Comment #10
damienmckennaTagging this issue.
Comment #11
japerryLooks good to me. Committed.