Closed (cannot reproduce)
Project:
Rules
Version:
7.x-2.6
Component:
Rules Core
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
20 Jan 2014 at 11:05 UTC
Updated:
3 Dec 2023 at 10:16 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedI have updated to the latest Drupal 7.26, and have the same problem.
It also occurs if I save a rule without a condition, then try to edit it again.
I must be doing something wrong, since others are clearly using it OK - does anyone have any suggestions?
With thanks, Tony
Comment #2
Anonymous (not verified) commentedThere is something very odd going on here.
I installed Rules (and Entity API) on a different site I also maintain and got exactly the same result. I then went slavishly through the procedure in the Node One video at http://nodeone.se/sv/node/752 and it worked. After that it has worked fine all the time and I could not reproduce the fault. I went back to the original site, did the same thing, and it is also now working fine.
There is presumably something that is getting set or saved in the first time through which does not default properly, and requires a particular sequence to work (or I tripped over a particular sequence which failed) - but I have no idea what it is.
Tony.
Comment #3
Harry_M commentedI have been experimenting with this problem because I have been getting the same error. I created a redirect rule using several different criteria. If I have it redirect when a user logs in, it works. If I add a role to the user, I get the Internal Server Error message. I am adding the exported test rule:
{ "rules_redirect_test" : {
"LABEL" : "Redirect test",
"PLUGIN" : "reaction rule",
"ACTIVE" : false,
"OWNER" : "rules",
"REQUIRES" : [ "rules" ],
"ON" : { "user_login" : [ ] },
"IF" : [
{ "user_has_role" : { "account" : [ "account" ], "roles" : { "value" : { "4" : "4" } } } }
],
"DO" : [ { "redirect" : { "url" : "pm-properties" } } ]
}
}
It works until the "user_has_role" is added. Hope this helps someone figure out the problem.
Comment #4
tr commentedFeel free to reopen if you can provide exact steps to reproduce this error on a clean site.