Closed (won't fix)
Project:
Panels
Version:
6.x-3.x-dev
Component:
In-Place Editor (IPE)
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Jul 2010 at 21:37 UTC
Updated:
23 Oct 2011 at 13:22 UTC
How to replicate:
Set up some content
Go into IPE mode
Delete the content (UX note: the fade feels slow here compared to everything else)
Click save
Reload page (or visit the normal panels content admin screen): the deleted items are still there!
Comments
Comment #1
joshk commentedUpdate: the same is true for attempts to add new panes via the IPE.
However, updating an existing pane appears to work.
Comment #2
joshk commentedUpdate: it also doesn't save if I move a pane from one region to another.
Comment #3
joshk commentedI'm calling it "critical" because this is pretty central to the IPE being useful.
Comment #4
sdboyer commentedI was having problems like this a couple days ago, but committed some fixes related to string transformation that I thought took care of it. This sounds like basic save failures, though, which is a little worrisome. I'll poke at it.
Comment #5
merlinofchaos commentedSam's tweak, indeed, failed to notice deleted panes so was sending the panes back. I went ahead and reverted the tweak, and sped up the fade out for deletion.
Comment #6
joshk commentedconfirmed; fixed with latest CVS checkout
Comment #7
pvasener commentedI confirm that the problem is fixed for new panel nodes. However, if I try to add or delete a pane with IPE on a node created before the update, the problem persists.
Comment #8
pvasener commentedAfter further testing, the bug persists only on a few panel nodes that I created a long time ago with Panels 2 / Drupal 5. I recreated these few panels with Panels 3 / D6 and they are now ok with IPE editing. Not sure my bug report worth investigating...
Comment #9
Letharion commentedIn an effort to clean up the many hundreds of open issues in the Panels queue, I'm going over all bug reports. If they haven't been updated in over a full year,
I'm going to assume that they no longar affect any one, and close it. I realise that some issues will be closed, that should remain open.
If this is the case, and you still have an interest in this issue, please just re-open it, setting the appropriate status, and providing exports and detailed instructions for reproducing the error.