Fatal error: Unsupported operand types in rules.module on line 227

I'm seeing the same error. Code is:

return $export + parent::exportChildren();

I'm surprised more people haven't chimed in with the same issue. Not sure what the fix is.

[UPDATE] Actually... mine was in rules.plugins.inc. I updated to the latest dev and cleared the cache a bunch of times and it is gone. I think it was just the cache clearing that fixed it but perhaps try the latest dev.

Patch attached.

Not yet throurougly checked, but it removes the error so.

I had the same error on -dev then went back to 2.6 and same thing. Deleted rules, cleared cache download -dev again and it's back to working, kinda similar to #1. After that the error didn't happen again even after drush dis rules -y and drush pmu rules -y and drush en rules -y again.

Here's the callstack if that helps:

Fatal error: Unsupported operand types in /sites/all/modules/contrib/rules/rules.module on line 227

Call Stack:
    0.0005     263784   1. {main}() ~/drush/drush.php:0
    0.0263    2511288   2. drush_main() ~/drush/drush.php:16
    0.2173    7878208   3. _drush_bootstrap_and_dispatch() ~/drush/drush.php:61
    0.3559    7883392   4. drush_bootstrap_to_phase() ~/drush/drush.php:87
    0.3559    7883464   5. drush_bootstrap_max() ~/drush/includes/bootstrap.inc:291
    0.3952   10007904   6. drush_bootstrap() ~/drush/includes/bootstrap.inc:345
    0.3978   10009192   7. _drush_bootstrap_drupal_full() ~/drush/includes/bootstrap.inc:185
    0.3978   10026344   8. drupal_bootstrap() ~/drush/includes/bootstrap.inc:938
    0.4334   13621520   9. _drupal_bootstrap_full() /includes/bootstrap.inc:2260
    0.7378   39797704  10. module_invoke_all() /includes/common.inc:5158
    0.7469   39926248  11. call_user_func_array() /includes/module.inc:895
    0.7469   39926448  12. rules_init() /includes/module.inc:895
    0.7475   39965376  13. rules_invoke_event() /sites/all/modules/contrib/rules/rules.module:12
    0.7476   39965832  14. rules_get_cache() /sites/all/modules/contrib/rules/rules.module:969
    0.7602   41675776  15. RulesEventSet::rebuildEventCache() /sites/all/modules/contrib/rules/rules.module:333
    0.7602   41675920  16. rules_fetch_data() /sites/all/modules/contrib/rules/includes/rules.plugins.inc:761

Tried 7.x-2.5, 7.x-2.6 and 7.x-2.x-dev all failed with this error:

-bash-$ drush cc all
PHP Fatal error:  Unsupported operand types in drupal/sites/all/modules/contrib/rules/rules.module on line 227
Drush command terminated abnormally due to an unrecoverable error.                                                                                                    [error]
Error: Unsupported operand types in drupal/sites/all/modules/contrib/rules/rules.module, line 227

Really need rules to be working. Is there anything I can do to get more helpful errors for you?

Edit: This is a fatal error, should we up the priority of this to major?

I applied this patch, but now I am getting

PHP Fatal error:  Class name must be a valid object or a string in /var/www/includes/common.inc on line 7837

Fun Fun.

The code in question is:

/**
 * Get the entity controller class for an entity type.
 */
function entity_get_controller($entity_type) {
  $controllers = &drupal_static(__FUNCTION__, array());
  if (!isset($controllers[$entity_type])) {
    $type_info = entity_get_info($entity_type);
    $class = $type_info['controller class'];
    $controllers[$entity_type] = new $class($entity_type); // #7837
  }
  return $controllers[$entity_type];
}

The value of $entity_type when the error occurs is: rules_config

An potentialy useful note: This only occurs on my local copy of the website. It works fine on dev, staging, and live.

I don't have a solution yet, but rebuilding the registry is a workaround: https://drupal.org/project/registry_rebuild

drush dl registry_rebuild
drush rr

#10 works for me! But I need download registry_rebuild manually.
Follow this blog to do it.

I am having the same issue. I am converting a D6 site to D7.26.

I started with a clean D7.26 core, ran the updater to get the D7 db, then started adding D7 modules. After I added Rules, I got a WSOD and the error in Rules @ line 227.

I applied the patch from #2 which made no apparent difference. I tried the solution #10 and again no difference. I've had to disable Rules in order to move forward, but at some point, I'm gonna need it back.

Any suggestions?

Neither the patch in #2 nor rebuilding the registry worked for me. However, the issue stopped occurring after I increased php memory limit (from 64M to 128M in my case). I haven't tried to debug the root cause (or even to confirm that memory is the actual problem), but I have been able to reproduce and then resolve the problem by adjusting memory_limit up/down. Worth a shot...

I was having this same problem and this worked for me from Stack Exchange:

• Try going to http://yoursite.com/update.php and execute the form submit.
• If this does not work, you must:
• disable rules by SQL command:
• UPDATE system SET status = 0 WHERE system.name = 'rules';
• Execute drush cc all
• Active drush again:
• Drush en rules -y

The patch in #2 wasn't applying clean in our drush make process - find attached one that does.

#15 patch works.

thanks

yes...it works...thx :)

I had this issue on my local instance only after cloning a Dev database to my local.

The following solution worked for me:
Manually clear all sql cache tables (cache and all the cache_* tables)

Note:
You have to do it manually to your sql database as drush commands will keep throwing errors when they try to bootstrap the site. You may be able to do direct drush sql command line commands to truncate the tables as well but I didn't try that.

My local is working just fine now after doing that :)

Applied the patch after this issue killed a website completely.
It didn't solve my problem, patch applied but I got another error and the site still WSOD'd.

patch -p1 < rules-fix-unsupported-operand-types-2161847-2.patch
patching file rules.module
Hunk #1 succeeded at 230 (offset 7 lines).
drush cc all
PHP Fatal error:  Call to undefined function entity_load_multiple_by_name() in /var/aegir/platforms/xxxx/sites/all/modules/rules/rules.module on line 828
Drush command terminated abnormally due to an unrecoverable error.   [error]
Error: Call to undefined function entity_load_multiple_by_name() in
/var/aegir/platforms/xxx/sites/all/modules/rules/rules.module,
line 828

I tried manually truncating all my cache_ tables and the cache table itself (#2324587: Rules might be triggered too early in the bootstrap. To no avail.

Had to restore a backup.

Ups, just seen that i created a dup over there at #2344579: WSOD: PHP Fatal error: Unsupported operand types in rules.module on line 234.
I think my patch there makes more sense.

I'm also facing the followup issue in #20.
Which more people experienced but no solution there: #2324587: Rules might be triggered too early in the bootstrap

I'm not really sure, but my gut feeling is that this issue is essentially the same as #2324587: Rules might be triggered too early in the bootstrap.
As over there here too the backtraces indicate that rules does an event cache rebuild too early in the bootstrap process, which leads to whitescreens that are hard to reproduce. So setting critical too, and we might want to close the other issue.

Here's how to reproduce the bug:
drush vset language_default notaserializedlanguageobject
That hit me and threw gazillions of notices in early bootstrap so surely triggering this bug.

Patch #22 solved the issue for me. Now the module can be enabled/disabled without drush errors.

I think it's too soon to mark this as reviewed and tested as we still have the # 20 issue (for some - on multilingual? - scenarios).

I think we should
* get the patch in - it fixes a coding bug and can be proven it can't harm
* attract fagos attention by setting this rtbc
* decide what to do with the underlying issue - imho "rules is not safe for early bootstrap events"

This is getting really bad. Simply enabling the css_injector module wsod's a site. After the patch from #22 the site still remains dead and produces the error as described in #2324587: Rules might be triggered too early in the bootstrap.

I've been trying latest dev releases of entity api and rules. Deleting cache tables, it all doesn't help. The only option seems to be to restore a backup and uninstall rules as it's a hazard atm.

Thanks, I committed the fix from #22. Let's collaborate in #2324587: Rules might be triggered too early in the bootstrap on how to make things less error-prone.

https://www.drupal.org/node/2161847#comment-9179137 worked for me! Thank you!