Drupal version: 6.3
Nodequeue Module version: 6.x-2.0-rc1

Trigger has been set on Action: "Add to Nodequeue", which was supposed to invoke that action, when new Story node was added. Trigger it seems worked fine, but on adding new Story to the queue the following error message appeared:

# warning: Invalid argument supplied for foreach() in ..\modules\nodequeue\nodequeue.module on line 1624.
# warning: Invalid argument supplied for foreach() in ..\modules\nodequeue\nodequeue.module on line 1652.

Story records were successfully created, but not added to the queue.

I tried to add the same stories to the queue manually and it worked ok.

CommentFileSizeAuthor
#1 nodequeue-actions.patch1.39 KBjody lynn

Comments

jody lynn’s picture

jody lynn
she/her
Primary language English
commented
Status: Active » Needs review
StatusFileSize
new nodequeue-actions.patch1.39 KB

The upgrade missed some form api changes.

jody lynn’s picture

jody lynn
she/her
Primary language English
commented
Title: When trying to add record to the nodequeue using actions and triggers error message pops up. » Nodequeue & Triggers - FAPI error
dmitry70’s picture

dmitry70 commented

I verified the patch and it works. Thanks a lot. Not sure, what is the workflow for the issues, shall I mark it as fixed?

jody lynn’s picture

jody lynn
she/her
Primary language English
commented
Status: Needs review » Reviewed & tested by the community

Now it's set to reviewed & tested. It gets marked as fixed by a module maintainer if they commit the patch.

ezra-g’s picture

ezra-g commented
Status: Reviewed & tested by the community » Fixed

Committed -- catch it in the next release. Thanks!

rismondo’s picture

rismondo commented
Version: 6.x-2.0-rc1 » 7.x-2.x-dev
Status: Fixed » Needs work

I just tried the latest 6.x-2.x-dev (Aug 14) with this patch already included, but I am still getting this error message. When I try to add a node to a queue from an action in response to a workflow transition, this exact error message still shows up after upgrading rc1 to dev, even after emptying cache. Using Drupal 6.4.

rismondo’s picture

rismondo commented
Status: Needs work » Fixed

I started from scratch with a new Drupal install and the dev version, no error shows up any longer. Apparently upgrading from rc1 to a post-patch version might still cause these errors to show up (at least that is what seemingly happened in my case).

ezra-g’s picture

ezra-g commented

Hmm. Did you empty the cache via command line in the database or did you use the clear cache button?

rismondo’s picture

rismondo commented

Just the clear cache button. I suppose that wasn't enough :)

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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