Could someone explain the differences in Nodequeue 3 branch from Nodequeue 2 branch? Why is there a branch 3, what's in it different than Nodequeue 2, and what's the goal for Nodequeue 3.

I find no information about it. Thank you.

I reported an issue in http://drupal.org/node/1876502 which solved itself when I used Nodequeue 3 instead of Nodequeue 2, however I'm not clear at all on why it did and would rather use Nodequeue 2 which is a beta, if I could.

Comments

amateescu’s picture

Status: Active » Fixed

Well.. the 7.x-3.x is supposed to bring exportability support to nodequeues (with ctools), but apart from that there are no differences. My guess is that the export patch touched the code that you had a problem with.

Status: Fixed » Closed (fixed)

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

s.daniel’s picture

Status: Closed (fixed) » Active

Nodequeue 3 is listed as "Not supported!" in admin/reports/updates which I think is not like it used to be a few weeks ago. Is there a particular reason for this. e.g. Do you plan to discontinue the development of 3.x?

cpsarros’s picture

+1

Jay Almers’s picture

Priority: Normal » Major

+1 to this as well. I am encountering an error with the latest (Jan 2013) dev release that I am unable to actually trace. It appears to be tied to Revisions.

When I edit a node, and I do not create a new Revision -- I get a "Connection Reset" page and a Segmentation Fault on my server.

When I edit a node, and I do create a new Revision -- everything works as it should.

If I disable the Nodequeue module, I do not experience any errors at all. If I re-enable the module, the errors above come back.

Like I said, I am really unable to trace and troubleshoot the error outside of what is described above because the connection is resetting on my server and the log output only shows the segfault.

Output from Apache Error Log:

[Wed Mar 06 10:08:05 2013] [notice] child pid 13634 exit signal Segmentation fault (11)
[Wed Mar 06 10:08:11 2013] [notice] child pid 13564 exit signal Segmentation fault (11)
[Wed Mar 06 10:08:16 2013] [notice] child pid 13347 exit signal Segmentation fault (11)
[Wed Mar 06 10:08:18 2013] [notice] child pid 29462 exit signal Segmentation fault (11)
[Wed Mar 06 10:09:50 2013] [notice] child pid 13537 exit signal Segmentation fault (11)
[Wed Mar 06 10:10:55 2013] [notice] child pid 14021 exit signal Segmentation fault (11)
[Wed Mar 06 10:10:57 2013] [notice] child pid 14023 exit signal Segmentation fault (11)
[Wed Mar 06 10:14:30 2013] [notice] child pid 14039 exit signal Segmentation fault (11)
[Wed Mar 06 10:21:22 2013] [notice] child pid 13951 exit signal Segmentation fault (11)
[Wed Mar 06 10:21:25 2013] [notice] child pid 13241 exit signal Segmentation fault (11)

sebcorbin’s picture

Status: Active » Closed (fixed)

If you happen to still have the error, please open another issue. As for the original subject, I'll add an alpha release soon.