Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello, on 7.x.3.x-dev I cant get "add to queue" link to appear on node page.
I idetified the problem to be in the nodequeue_load_subqueues_by_reference which return an empty $subqueues value
The $query which runs in that function doesnt return a result.
The 7.x-2.0-beta1 doesnt have this problem. But I guess this is a result of #1160068: Drop all use of $qid
Any help on this ?
Comment | File | Size | Author |
---|---|---|---|
#3 | nodequeue_1572622.patch | 870 bytes | Bill Choy |
Comments
Comment #1
rcross CreditAttribution: rcross commentedimportant, but probably not a critical issue.
Can you provide what steps to take to replicate the problem on a fresh install?
Comment #2
svendecabooterI upgraded from 2.0-beta1 to 3.x and had the same problem.
In the database table nodequeue_types the "reference" field contained value "1" for all my fields. I replaced the value "1" with the name of the nodequeue, and everything worked again. Probably an oversight in the update script?
Haven't delved into the code to figure out what goes wrong, but just thought i'd add my observations for other people experiencing this behaviour.
Comment #3
Bill Choy CreditAttribution: Bill Choy commentedI had the same issue with the reference column in the nodequeue_subqueue table, when switching to 7.x-3.x-dev.
Newly created nodequeues had a machine_name in the reference column and the legecy queues has a sequence number (which will it difficult to export nodequeues as a feature).
Here is the missing update patch to modify the nodequeue_subqueue table.
Comment #4
dafederNot all my subqueues with numeric values in "reference" were the same as the sqid. I just set all the references to be the same value as name and it worked.
Comment #5
jenlamptonSince the 3.x branch is no longer under active development I'm going to mark this as postponed. If it's also an issue in 2.x we should set back to active.
Comment #6
jenlamptonmaybe this is a better status?