Closed (fixed)
Project:
Nodequeue
Version:
5.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Aug 2007 at 23:59 UTC
Updated:
3 Nov 2011 at 23:39 UTC
I get the following javascript error in the Firefox JS console when trying to move a node down (using the down-arrow button) the order of a queue, using the queue overview interface:
Error: uncaught exception: [Exception... "Node cannot be inserted at the specified point in the hierarchy" code: "3" nsresult: "0x80530003 (NS_ERROR_DOM_HIERARCHY_REQUEST_ERR)" location: "http://reamp.idcwebdev.com/misc/jquery.js Line: 2"]
The node row is consequently not moved as expected (nothing happens).
This is on Drupal 5.2 using an infinite nodequeue, clean install of 5.x.2.x-dev.
Comments
Comment #1
merlinofchaos commentedWhat version of Firefox are you running?
Comment #2
greenmachine commented2.0.0.6. I also tested (same FF version) on another computer, in case I was having some environment issues, and got the same problem (up works, but not down, and no save button appears).
It seems to work properly in IE6, though.
Comment #3
merlinofchaos commentedInteresting and strange. I'm using Firefox 2.0.0.6 and I can't replicate this. I sat punching things up and down in a queue and can't get a js error to happen at all. Clearly there's something going on in your setup that's not with mine but I'm not sure what the problem might be.
Is it possible to get access to your site so I can look at it and see if I see that problem there?
Comment #4
dwwI wonder if this is caused by the same bogus PHP headers that were giving me grief over at http://drupal.org/node/182715.
@greenmachine: Please try my latest patch from there and see if that solves your JS-related problems. http://drupal.org/files/issues/nodequeue_js_header.patch_2.txt
Comment #5
dwwHrm, weird, I can't reproduce this with FF 1.5 or Safari 2.0.0.4 on a test site, even with the bogus PHP headers being set.
Comment #6
merlinofchaos commentedClosing -- no new info from poster in 3 months.
Comment #7
hermes_costell commentedFor anyone else encountering this issue I recommend double checking your jquery status. Try upgrading jquery_update, etc. For me the issue was that jquery_update was screwy...