I have attached a screenshot, I tried in garland and a couple other themes.

Members fund testing for the Drupal project. Drupal Association Learn more


merlinofchaos’s picture

Assigned: Unassigned » sdboyer

Ok, going to have Sam look at this, that's his javascript.

Do you have jquery eyecandy or jquery update or any of those modules?

sdboyer’s picture

Yeah, my first guess is that you've got jquery update and/or a version of jquery ui running that's not compatible with the new dnd js - we require jqui 1.6.

Also, while the screenshot illustrates an outcome, it doesn't actually illustrate what actions you take to create that outcome. If you could describe that, preferably with a screen capture video but alternately with words, it would be helpful.

smoothify’s picture

Title: Drag and drop creates a bunch of duplicate boxes, doesn't let me drag the content around » Drag and drop doesn't work with JQuery 1.7 +

I'm taking the liberty of renaming the this issue, as I get very similar behaviour on fresh out of the box drupal site. The site was on a multi site environment, so my jquery_ui module was using jquery 1.7.

The behaviour shown in the screen shot occurs once you try to drag a pane over to another region. It just offsets slightly and then sticks and you can't move it anywhere after.

Switching to jquery 1.6 fixes this problem and works as expected.

smoothify’s picture

Title: Drag and drop doesn't work with JQuery 1.7 + » Drag and drop doesn't work with JQuery UI 1.7 +

Correcting title...

sdboyer’s picture

Status: Active » Closed (works as designed)

Sorry, if it's a jq/jqui version issue, there's really nothing I can do about it. Simple fact is that there are incompatibilities between 1.6 and 1.7, and the jquery_ui module for D6 (which ipe depends on) recommends 1.6, and that's all you can run without running jquery_update. I've gotta keep it simple...which means D6 will be on 1.6 forevermore. Once we port to D7, though, we'll have the new hotness.

aidanlis’s picture

Status: Closed (works as designed) » Active

Wait what ... yes, there are incompatibilities, but it's trivial to get it working with both versions. If we can get Drupal running [1] we can certainly get Panels.

[1] #1067290: Fix jQuery 1.7 for Drupal 6

Let's leave this open and I'll try and get some time to provide patches?

Letharion’s picture

Version: 6.x-3.7 » 6.x-3.x-dev
Assigned: sdboyer » Unassigned
Status: Active » Closed (works as designed)

I'm willing to accept that we can re-open issues like this, and I will ping sdboyer about it if necessary, but this issue has been closed for well over a year. Please only re-open it if you already have an actual patch to attach. I'm not gonna keep every issue open that "may recieve a patch at some point".

For now I'm reseting this to closed, but feel free to re-open when there is an actual patch, or suggestion for sdboyer to have an opinion on.

jvieille’s picture

Status: Closed (works as designed) » Active

I don't think it is appropriate to denied such issue the status of "active" just because no patch is provided for solving it.

Even if the issue was not very active, upgrading JQuery becomes more and more necessary, and it is quite a shame that a so smart module lags behind on that matter.

I am using a large bunch of modules that all were made compatible with the latest Jquery but Panels...

So the issue has to remain open, even if no solution is readily available.

Thanks for the maintaining this exceptional module.
Merry Xmas!

Letharion’s picture

@jvieille The problem with that approach is that it makes it harder for the maintainers to find and work on the issues that actually are being worked on. I agree that it's a problem that a "smart module lags behind", but that's valid for all the other issues as well.

Work in this issue will happen when there's a developer with this issue, not when the issue has been open for a certain amount of time. I'm not going to close it again and try starting a war over it, but I want to make the argument that this detracts from development, not the other way around.

klonos’s picture

...you can always set issues to "postponed" if there hasn't been any action recently but no solution either. That would help in filtering issues.

JohnAlbin’s picture

Status: Active » Postponed

Until there's a patch for it…

rbayliss’s picture

I don't know whether it's better to create a new issue for this or not, but it could very well be related, so I'm gonna post it here and feel free to slap me. Panels standard display editor also chokes on draggable panes with jQuery 1.7 (not jQuery UI 1.7, jQuery 1.7). The reason is a funky call to the offset method as follows:

offset = $(this.dropzones[i].obj).offset({padding:true});

For whatever reason, passing the object into the offset method returns a jQuery object under jQuery 1.7, meaning everything falls apart when you try and check the coordinates later. I can't find documentation on passing this kind of parameter to offset(), so I suspect that it may be a removed feature or straight up bug. Removing the {padding: true} object makes drag and drop work as normal. Patch attached.

Just to reiterate: This fixes a bug in the 6.x-3.x panels standard display editor that only occurs under jQuery 1.7.

rbayliss’s picture

Status: Postponed » Needs review
smoothify’s picture

Title: Drag and drop doesn't work with JQuery UI 1.7 + » Drag and drop doesn't work with JQuery UI 1.4 - 1.7 +
Status: Needs review » Reviewed & tested by the community

I can confirm this patch works for me, when using jquery update with jQuery versions 1.4, 1.5 or 1.7.

pebosi’s picture

Patch #12 is working for me too.

DamienMcKenna’s picture

japerry’s picture

Status: Reviewed & tested by the community » Fixed

Well at some point, IPE requires jquery_update anyway. but its still like 1.3.. Anywho this patch works, and I added jquery_update as a dependency for IPE because it won't work without it.


  • japerry committed 78070a5 on
    Issue #866178 by rbayliss, drupalninja99, japerry: Drag and drop doesn't...

Status: Fixed » Closed (fixed)

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