Closed (fixed)
Project:
Rules
Version:
7.x-2.6
Component:
Rules Core
Priority:
Major
Category:
Bug report
Assigned:
Reporter:
Created:
4 Oct 2013 at 19:44 UTC
Updated:
2 Dec 2020 at 10:05 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
ey commentedI am also getting the same errors.
Comment #2
newtoid+1
This issue persists, I rolled back to version 2.3 and it cleared.
Comment #3
wipeout_dude commentedSeems there aren't too many having the issue with rules 2.5 so maybe it relates to another module..
So currently on my site I have enabled..
Conditional Rules 7.x-1.0-beta2
Rules 7.x-2.3
Rules Link 7.x-1.0-beta4
Rules Scheduler 7.x-2.3
Rules UI 7.x-2.3
Which are common to all of us?
Comment #4
jraviotta commentedSame error for me too. Following...
Comment #5
wipeout_dude commentedAnyone solved this or have any ideas?
Comment #6
markusa commented+1 After upgrade to version 2.5 my "node of of type" conditions fail and report this error
Comment #7
markusa commentedI found resolution for this issue in my case.
I had several rules which had a condition checking for the type of a node....I switched to checking for "Entity is of bundle" and the rule started to work....Not sure if checking node type is broken in Rules 2.5 or if its just not available anymore...
Comment #8
noslokire commentedInteresting, I am going to give this swap to bundle is of type a try and see if the issues persist.
*Update - No dice, was hoping this was the silver bullet but the issues described above persist.
Comment #9
jraviotta commentedI get the same problem for all rules using condition "Content is of type". When I delete that condition and substitute "entity is of bundle" the rule passes again.
However, I still get the error when using the condition "content is published."
Comment #10
fagoWhich environment are you guys using? For me the condition works just fine.
Comment #11
ey commentedI was using PHP 5.4 at the time I have confirmed the issue.
I am currently trying to build a new setup with multiple PHP versions (5.5 and 5.3). I didn't have the time to test it on my new development setup. As soon as I install everything, I'll report it back.
Comment #12
wipeout_dude commentedOk, so here is an odd one..
I setup a dev VM and copied the live site to it.. I used drush to upgrade rules and got the output below..
To my surprise there was no error showing on the rules configuration page.. So I took a snapshot of the live server, upgraded rules and got the same output.. Went to the rules configuration page and the error was there..
Both servers are running PHP 5.4.21..
The difference is that the dev server is running generic Apache + Mod_PHP while the live server is running nginx + PHP-FPM..
Anyone else showing the issue running either nginx or PHP-FPM (likely to be both if using nginx)??
I have rolled back the live server because I don't have time this evening to edit every rule (over 50 of them) to "Bundle is of type" or to change the main event trigger to be a specific content type eg. "After updating existing content" to "After updating existing content of type basic page".. I haven't done much testing but it seems that either of these changes solves the problem.. I am guessing updating the event trigger to be content type specific is probably the more correct way to do it??
Comment #13
_paul_meta commentedI'm experiencing this issue too .. its broken all my content creation rules !
Currently using 7.2.6 but I also saw this issue with 7.2.5
Any rule with condition "Content is of type" shows this error on the rules page - "Error: Missing required module 0."
Also seeing this error when clearing site caches .. Notice: Undefined property: stdClass::$plugin in RulesEntityController->save() (line 160 of /home/...../sites/all/modules/rules/includes/rules.core.inc).
I tried rolling back to 7.2.3 but found more errors, clearing the site cache failed with a PDO database error.
So I'm back with 7.2.6 .. and hoping for a fix. Anyone else in this situation ?
I'm on an apache server, running php 5.3
Thanks,
Paul
Comment #14
_paul_meta commentedComment #15
andrés chandía commentedSame Issue round here, I solved following #9 posted by jraviotta
Im on:
Drupal 7.24
PHP 5.5.3-1ubuntu2
Web server Apache/2.4.6 (Ubuntu)
DataBase system MySQL,
DataBase system version 5.5.34-0ubuntu0.13.10.1
Comment #16
andrés chandía commentedWeird thing, I have 2 drupal sites on the same server, sharing the modules location, at the other one I don't have this problem, so seems to be related to enabled modules, but I can not say which module could be the responsible, at the working site I have next modules disabled, those are enabled at the non working site:
Aggregator
Localization client (I would suspect of this one)
OpenID
Pretty Calendar
Comment #17
wipeout_dude commentedIn addition to my post #12 another difference between my live and dev site is..
Modules enabled on live site but disabled on dev site
Google Analytics
Secure Pages
Modules disabled on live site but enabled on dev site
Maillog
Anyone using or not using these on server with the error?
Comment #18
poniesSame as #9. Content is published is still Missing required module 0.
Drupal 7.21
PHP 5.3.3
Apache/2.2.15 (Unix)
Comment #19
tien.xuan.vo commentedI debugged and find out one solution in my case:
Drupal 7.24
Rules 2.6 with fluxservice
The problem is fluxservice return rule action info with the key 'module' is set to 'false'. So that we need to check 'not empty' insteads of 'isset'.
Comment #20
jhedstromPatch in #19 resolves this error.
Comment #21
fagoThanks, committed.
Comment #23
aludescher commentedRerolled patch #19 for 7.x-2.5 - useful when updating from lower versions.