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.
The load function for a nodequeue has changed. Nodequeue-7.x-3.x-dev supports machine-names.
Comment | File | Size | Author |
---|---|---|---|
#17 | features_extra-nodequeue_3.x_dev_support-1845752-17.patch | 2.7 KB | dan.munn |
features_extra_fe_nodequeue_dev.patch | 1.81 KB | jasperknops | |
Comments
Comment #1
annikaC CreditAttribution: annikaC commentedI've adapted this to work with Features Extra latest dev too.
Comment #2
pfrenssenNodequeue 3.x is at the moment in early development. It is not even mentioned on the project page yet, and the recommended version is still 2.x. I'm going to postpone this until 3.x gains traction.
The patch would break existing implementations too, it should work with both versions of Nodequeue.
Comment #3
pfrenssenMarked #1895034: fe_nodequeue not compatible with the 7.x-3.x-dev release of nodequeue as a duplicate of this issue.
Comment #4
pfrenssenThere seems to be interest in this. I'm putting it back to active. We do need an update to the patch so that it is compatible with both Nodequeue 7.x-2.x and 7.x-3.x.
Comment #5
moonray CreditAttribution: moonray commentedProbably the easiest is something like:
Better would be some sort of nodequeue API version check.
Comment #6
pfrenssenYeah indeed. It remains to be seen when this will become relevant. There is no mention of Nodequeue 3.x at all on their project page, and the development seems to have stalled (there have only been 4 commits in the past 12 months). It will probably be quite some time before Nodequeue 3.x is ready.
Comment #7
moonray CreditAttribution: moonray commentedWe're using nodequeue 3 due to some requirements that weren't in 2. There are probably others out there that use it as well.
It seems like a simple fix, so why wait to include a solution?
Comment #8
jasperknops CreditAttribution: jasperknops commentedThe backwards compatible approach of moonray in #5 seems like the beste solution to me.
Comment #9
pfrenssenPatches are always welcome!
Comment #10
moonray CreditAttribution: moonray commentedAttached patch makes features_extra compatible with nodequeue 3.
Comment #12
pfrenssenRelated issue: #2050119: PDOException: Unknown column 'qid' in 'field list': SELECT qid, name FROM {nodequeue_queue} fe_nodequeue error.
It reports a PDO exception caused by changes to the database schema in Nodequeue 7.x-3.x.
Comment #13
pfrenssenComment #14
dan.munn CreditAttribution: dan.munn commentedHave gone the route of the former patch, also included queue creation support under new nodequeue which looks for new attribute set.
Comment #16
dan.munn CreditAttribution: dan.munn commentedTake 2 - have removed the subqueues attribute from the exported data within the test as this is now always unset as per the changes in patch.
Comment #17
dan.munn CreditAttribution: dan.munn commentedSorry, in error forgot to flag status as needs review (not trying to spam the thread).
Comment #18
elvis2 CreditAttribution: elvis2 commented#17 worked for me. I ran into this error when doing a "drush fd featurename" from the command line. Your patch got rid my issue.
Thanks!
Comment #19
Robin_K CreditAttribution: Robin_K commented#17 worked for me too, I was getting errors when trying to create a new feature with nodequeues, patch seemed to have fixed it.
Comment #20
santhony CreditAttribution: santhony commenteddeleted.
Comment #21
rolfmeijer CreditAttribution: rolfmeijer commentedCleaning up the files list.
Comment #22
moonray CreditAttribution: moonray at Chapter Three commented#17 works for me. This patch is really a long time coming.
Comment #23
pfrenssenPostponing on having a stable release for Nodequeue 3.x.