Closed (fixed)
Project:
Rules
Version:
6.x-1.x-dev
Component:
Rules Engine
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
7 Feb 2011 at 13:42 UTC
Updated:
2 Jan 2014 at 19:06 UTC
Jump to comment: Most recent
Comments
Comment #1
mitchell commentedPlease provide the versions of Drupal and Rules you are using, a list of other modules installed, and the sequence of events you went through in setting up your system. If you can provide any other informatinon that would help pinpoint when these errors began, then it would be possible to help you solve it.
Comment #2
parasolx commentedOps, sorry cause i forgot to attach all those important information.
Drupal: 6.20
Rules 6.x-1.x-dev (2011-Jan-27)
Here are the list of modules which are activate in my system.
[edited by author. since it would exposed what modules my used]
First I used stable version, 1.4 and this problem happen. So, i decide to uninstall it, remove folder and replace with 1.x dev. but still have same problem.
Comment #3
fagoDo you have that problem too with Drupal only and Rules? If not, please try enabling modules step by step. I know that's a lot of work, but it's the only way to identify the source of the problem.
Comment #4
parasolx commentedso far i never tested it with only Drupal+Rules. but i think its work well because like before its work with current site. after upgrading to 1.4 then suddenly i realize it turn blank.
by the way, it may takes some time to do that and i will do it soon. but can you suggest what modules "probably" conflict with rules. so i can start to focus on that part first.
Comment #5
parasolx commentedHey there,
Today I just suddenly check Rules. And what happen that its work already. What I could remember is just a few days ago I have remove a couple of modules that does not suite with my needs.
1. flag
2. pingthis
3. uniqueness
there is no installed of new modules until right now. and probably the conflict comes either from uniquness or flag modules. because both are using javascript injecting. there is no fixing right for now, but if someone out there facing this problem before, kindly to check either you have installed these module in your site.
thank you.
Comment #7
grasmash commentedI have this same error. It seems to occur only when these two conditions are true:
1) LoginTobaggan's 403 redirect option is enabled
2) I have a rule that uses 'execute php code' (no matter what the code is).
I'm looking further into this.
EDIT: My issue was caused by a bug in LoginTobaggan. See here:
http://drupal.org/node/897540#comment-4743546