After upgrade to 6.x-2.3, I can't create new nodequeues. Here's the thing. When I added a new nodequeue, nid or I don't know how you call it was set to zero. In the URL, I get admin/content/nodequeue/0/view. This new nodequeue doesn't work (nodes cannot be added to it). Interestingly, when I tried to add a consequent nodequeue, it was not created, and here's the error message I received:


    * user warning: Duplicate entry '0' for key 1 query: INSERT INTO nodequeue_queue (title, subqueue_title, size, link, link_remove, owner, show_in_links, show_in_tab, show_in_ui, i18n, reverse, reference) VALUES ('vazna', '', 4, '', '', 'nodequeue', 0, 1, 1, 1, 0, '0') in /public_html/sites/all/modules/nodequeue/nodequeue.module on line 2090.
    * user warning: Duplicate entry '0' for key 1 query: INSERT INTO nodequeue_subqueue (qid, reference, title) VALUES (143257, '143257', 'vazna') in /public_html/sites/all/modules/nodequeue/nodequeue.module on line 2167.

I suspect this was also the case with the 2.2 version, but the upgrade hasn't solved the problem for me.

Comments

ezra-g’s picture

Status: Active » Postponed (maintainer needs more info)

This seems unrelated to changes in the past two versions and sounds more like database corruption. Can you paste the output from your nodequeue_queue and nodequeue_subqueue tables? Also, what database are you using?

andrus_k’s picture

Yes, I guess it was a database corruption. Clean reinstall of the module has helped.

ezra-g’s picture

Status: Postponed (maintainer needs more info) » Fixed

Interesting. If you have any ideas how your database became corrupted, I'd be interested to hear them. Sometimes custom javascript results in bogus values getting inserted into nodequeue_nodes, but I haven't heard of this happening for nodequeue_queue or nodequeue_subqueue.

Thanks for the quick update.

Status: Fixed » Closed (fixed)

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