Closed (fixed)
Project:
Nodequeue
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Apr 2013 at 11:59 UTC
Updated:
12 Jan 2015 at 15:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
havran commentedThis patch work for me.
Comment #2
yched commentednodequeue.js looks quite outdated (the links behavior should be attached using Drupal.behaviors, use jquery once() insetad of manual *-processed classes, there are a couple unused vars...)
But the patch here does work as a quickfix.
Comment #3
fizk commentedWhat are the steps to reproduce this?
Comment #4
fizk commentedComment #5
yched commented@fizk:
On node/[nid], in the "links" section of the node template, nodequeue adds links to add/remove the node from the queue.
Those links are supposed to be ajax links (add/remove the node in an Ajax request without redirecting the whole page) - see the supporting code in nodequeue.js.
But that JS code is outdated and doesn't actually work, so the links act as "regular links" and redirect the browser.
The fix is quite simple, see the patch.
That's a fairly big UX regression, those ajax links on nodes are a major interaction point fro adding content to the queues.
Comment #6
yched commentedBack to RTBC
Comment #8
fizk commentedExcellent. Committed, thanks!