Closed (outdated)
Project:
Nodequeue
Version:
7.x-3.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
11 May 2012 at 17:02 UTC
Updated:
26 Nov 2016 at 01:55 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
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 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?