"Packing arguments" error when rule triggered
| Project: | Rules |
| Version: | 6.x-1.x-dev |
| Component: | Rules Engine |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I am trying to set up a rule so that when a node of content type X is saved, a schedule is set up so that two weeks later (or 5 minutes for testing) the node is unpublished. This required a new ruleset, to which I sent the arguments "Content" and "Date" (not sure if Date was necessary), which unpublished the node in question. Then I created a rule that made sure the content type was X and scheduled the ruleset for "+5 minutes." Below is the result I get when saving the node of type X:
An error occured during rule evaluation. This is the evaluation log:
* 0 ms Content is going to be saved has been invoked.
* 7.249 ms Included MODULE.rules.inc files.
* 8.102 ms Executing the rule Email Suggestion on rule set Content is going to be saved
* 8.234 ms Condition saved content is Suggestion evaluated to FALSE.
* 8.306 ms Executing the rule Unpublish a node after two weeks on rule set Content is going to be saved
* 8.41 ms Condition saved content is Housing Classified Ad evaluated to TRUE.
* 8.652 ms Action execution: Schedule Unpublish content
* 8.74 ms Packing arguments for scheduling the rule set rules_label2 failed.
* 8.787 ms Evaluation of Content is going to be saved has been finished.
I have searched and have not found a solution to this problem. Could it have been my including the "Date" argument even though I did not use it, or is there something else?
#1
I'm still not sure why this error occurred, but I think it was because I had selected "Content is about to be saved" as the trigger, rather than "After saving new content." If the content is not there, it cannot be schedule to be unpublished in the future, I imagine because it does not have a node id yet.
Things are working much better now.
#2
Changing to "closed."
#3
Can anyone confirm that a "Content is about to be saved" trigger cannot schedule rule sets based on data from the node being created, more specifically the node id?
I don't know how, but I created a rule that was triggered by "Content is about to be saved" and this rule scheduled a rule set that did some term attribution to the node a couple days in the future. The rule also passed the "saved content" variable as parameter (but not any date, as it is not in fact needed). It worked perfectly -- you could even see the nid of the created node on the scheduled rule set identifier (I used "set-myterm-[node:nid]").
Today I created some new rules to implement new features and tests and now my scheduling trigger is spitting the dreaded "Packing arguments for scheduling failed" error.
I tried to disable the news rules to no avail. The old rule are still giving error and stopped to schedule the rule set. :-(
Does anybody has a suggestion of how to make the module log (via print_r() or the like) why, what, and where argument packing failed, so I could try to debug what's going on?
*sigh*
#4
Content is about to be saved + scheduling:
yep, that can't work when you add a new node. Use the content is new condition to only schedule nodes with id or use the event: After new content has being created.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.