Note: the same bug was present in 7.x-1.25+dev-9 (I tried to update to 1.26 but it didn't solve it, instead it made it worse).
Basically I cannot load any VBO view in a Rule component.
Before upgrading to 1.26 I could, but I was always receiving an error and notices:
Error: "An illegal choice has been detected, contact site admin.."
Status: basically the ones that admin gets when a view with a map display has some rows without geolocation data.
This was slowing down the Rules interface very much on every save, and I wasn't even sure the rule would work.
As I said, I saw the available update so I did it before testing the Rule, hoping it would fix the bug, and now I get a bad gateway error every time I try to add an Action to "Load a list of objects (or ids) from a VBO View" (so I cannot even go on working on my rule..).
Please note: The VBO views I am trying to add are brand new, with only Master display or a Block display, with Unformatted list format, and without any location related field.
If I now visit the page of the rule I was working on before the update I also recieve a 502 Bad Gateway error from ngix.
If I disable this module, the rules correctly load the VBO lists from any View without Bad gateway error.
If I make the Rule with this module disabled, and then I re-enable and access the rule page (already configured) I still get the gateway error.
What could it be?
Comment | File | Size | Author |
---|---|---|---|
#2 | Screen Shot 2014-11-22 at 01.59.03.png | 1.02 MB | kopeboy |
Screen Shot 2014-11-22 at 01.49.00.png | 661.71 KB | kopeboy |
Comments
Comment #1
kopeboy CreditAttribution: kopeboy commentedComment #2
kopeboy CreditAttribution: kopeboy commentedComment #3
kopeboy CreditAttribution: kopeboy commentedComment #4
kopeboy CreditAttribution: kopeboy commentedComment #5
kopeboy CreditAttribution: kopeboy commentedComment #6
RdeBoerNo idea, kopeboy.
Sorry.