Closed (cannot reproduce)
Project:
Rules
Version:
7.x-2.x-dev
Component:
Rules Core
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Apr 2012 at 08:29 UTC
Updated:
2 Jul 2021 at 15:54 UTC
Jump to comment: Most recent
Comments
Comment #1
mitchell commentedPlease provide more information to reproduce this error.
Comment #2
somimi commentedSame here. Installed Rules 7.x-2.2 on my site, and cannot add any conditions to my ruleset. Everything I've tried brings up that same error, from "Content is of type" to "User has role(s)".
The site also uses the UUID module, so I attempted to use that patch found here: http://drupal.org/node/1423234. But while I'm now able to set certain conditions (Content and User-related ones seem to be okay), others still seem screwed up - most notably, the Entity conditions. I also have no tokens available.
So, in short, Rules is completely unusable to me right now.
Comment #3
somimi commentedSo without Rules being functional for me right now, are there any other alternatives for, say, sending emails to a site administrator when content is created on the site? I tested Notifications briefly, but it only seems to trigger actions for published nodes, and I need the ability to trigger emails when unpublished nodes are saved.
Comment #4
pessimizer commentedThis is probably your error - with UUID: http://drupal.org/node/1794724
That module is wreaking untold havoc over a dozen issue queues.
Comment #5
breaklaw commentedThat's what it was for me. Uninstalled UUID and the issue went away.
Comment #6
kacash commentedI don't have UUID installed, and I am getting ajax errors when adding some actions.
Add a new action > Add an item to a list > site:current user:roles throws this PHP error:
Adding conditions almost always errors out. Add a new condition > Data comparison > site throws this:
Commenting out line 901 allows it to save.
The same code and database runs with no errors on my local development machine.
I've tried rules versions 7.x-2.3, 2.5, and 2.x-dev, with the same result.
Comment #7
tr commentedNo further information provided.
Feel free to reopen if you can provide exact steps to reproduce this error on a clean site.
Comment #8
frank00511 commentedIssue for me too.