Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I try to edit Condition to Rule After Saving Content and get:
Fatal error: Unsupported operand types in /Volumes/sites/all/modules/rules/includes/rules.state.inc on line 620
Comment | File | Size | Author |
---|---|---|---|
#30 | rules_unsupported-operand-types-1567816-30-D7.patch | 1.5 KB | Reg |
#29 | ajax_rules_condition_error.png | 11.82 KB | dynamiz77 |
Comments
Comment #1
marko42 CreditAttribution: marko42 commentedI am getting the same error. I'm also using 7.14.
Comment #2
brandy.brown CreditAttribution: brandy.brown commentedSame problem here. Breaks entire site.
I get it on 2.1 and the -dev versions.
Comment #3
marko42 CreditAttribution: marko42 commentedI brought my module versions up to date and ran update.php. Now the problem has cleared. I don't know why exactly.
Comment #4
_KASH_ CreditAttribution: _KASH_ commentedFatal error: Unsupported operand types in xxxxxx/sites/all/modules/contrib/rules/includes/rules.state.inc on line 620
running 7.x-2.x-dev
Comment #5
emcniece CreditAttribution: emcniece commentedDo you guys have Node Export or UUID installed? Try getting rid of it - that worked for me.
http://drupal.org/node/1423234 has some patches that might be of use, I didn't get a chance to try them out.
Comment #6
timofey CreditAttribution: timofey commentedClearing cache did the trick.
Comment #7
pschuelke CreditAttribution: pschuelke commentedSame error for me. Tried patch suggested in #5; made it worse. Clearing the cache didn't help. I do have Node Export and UUID installed but can't get rid of them.
Comment #8
greg.1.anderson CreditAttribution: greg.1.anderson commentedHaven't really had a chance to look into this deeply; I just did the naive thing, and changed line 620 like this:
Edit: Don't do this! See below.
Comment #9
greg.1.anderson CreditAttribution: greg.1.anderson commentedHm, I don't think #8 is helpful. It took away the errors all right, but the missing information in $site_info is important (!); rules cannot be successfully set up without it. Disabling the uuid module did the trick.
Comment #10
skamble CreditAttribution: skamble commentedI am getting same errors and i used drupal 7.14. I try #6 solutions for clear cache and its work for me.
Comment #11
gomanual CreditAttribution: gomanual commentedRemoving UUID worked for me.
Comment #12
ronigal CreditAttribution: ronigal commentedUpdating module UUID to uuid-7.x-1.x-dev solved the problem.
Comment #13
tengokusame here.... disabling uuid fixed the problem
Comment #14
radiobuzzer CreditAttribution: radiobuzzer commentedSame problem here.
Comment #15
mitchell CreditAttribution: mitchell commentedLooks like this was a bug in previous versions of UUID and/or stale Rules caches.
If there's a UUID bug to track down, please open a new issue there and link to this issue.
Comment #17
jaykainthola CreditAttribution: jaykainthola commented#8 Worked for me.
Thanks
Comment #18
nd987 CreditAttribution: nd987 commentedThe latest dev version of UUID fixes this issue.
Comment #19
emudojo CreditAttribution: emudojo commentedUpdating to the latest dev for uuid solved the problem for me as well, this time using pressflow 7.14
Comment #20
Andy Inman CreditAttribution: Andy Inman commentedSame issue with everything up to date, core 7.21, also fixed by disabling UUID (I din't try the dev version of UUID so can't confirm whether that works or not).
Comment #21
owntheweb CreditAttribution: owntheweb commentedI've run into this error on multiple occasions, when updating modules such as Token, Entity API, Rules and some others (some of those listed are likely not related). I start noticing these errors when attempting to save content that trigger rules, looking at the Rules configuration page in general or when attempting to edit a rule (ajax errors).
The fix for me is usually pretty simple (and I'm posting here to help myself remember when this happens again):
Comment #22
jwjoshuawalker CreditAttribution: jwjoshuawalker commented@owntheweb
Love it :)
I was just going through the same thing today, and about to make a very similar post.
Comment #23
JamesRobertson CreditAttribution: JamesRobertson commentedI followed @owntheweb in post #21. I held my breath - nothing happened. Still the same error. I cried a bit then went into rules.state.inc and replaced
$property_info['properties'] += $site_info['properties'];
with
if(!empty($site_info['properties']))$property_info['properties'] += $site_info['properties'];
I have absolutely no idea what I have done - but at least i can now access my Rules.
I may have, unwittingly, sold my soul to the devil, but, hey, at least my site has started working again.
Comment #24
greg.1.anderson CreditAttribution: greg.1.anderson commented#23 is essentially the same as #8. As I mentioned in #9, this simple modification is destructive to the happy operation of rules, and will hurt you later. I recommend #21.
Comment #25
decibel.places CreditAttribution: decibel.places commentedfollowed #21
had to checkout latest 7.x-1.x branch of uuid from git, a db update was run, cleared cache and
happy now
Comment #26
pbz1912 CreditAttribution: pbz1912 commentedDisabled uuid. It worked. uuid alpha-4 still broken, don't have the option to use dev where I am. Didn't have any actual use of uuid that needed it to stay in for the time being. However, I suspect that may change soon.
Comment #27
kevla CreditAttribution: kevla commented:( I'm having the same issue here. Although I don't have UUID.
Comment #28
dynamiz77 CreditAttribution: dynamiz77 commentedjust like kcmanc87 I don't have UUID module installed and am still getting this error - anybody got a solution? (Have the latest version of Rules Module - 7.x-2.4
Drupal core 7.23
Comment #29
dynamiz77 CreditAttribution: dynamiz77 commentedSorry - Forgot to attach the pic of the error.
Comment #29.0
dynamiz77 CreditAttribution: dynamiz77 commentedcorrection
Comment #30
Reg CreditAttribution: Reg as a volunteer commentedI just came across this issue and I do not have UUID installed. In my case it happens every time I log in.
Looking for other instances of entity_get_property_info('site') I came across this in the entity module:
What the comment suggests to me is that if no modules provide site wide information then the 'properties' array element can be non-existent. This being the case #8 is a correct solution.
If you want to give the function some site wide variables then we can look at the system module and pull the variables from system_site_information_settings() which I have done in the patch.
Comment #31
areynolds CreditAttribution: areynolds commentedSeeing as the entity module adds in the site info in system.info.inc's entity_metadata_system_entity_property_info() call, I don't think the patch in #30 should be necessary.
If this implementation were to be pursued, the naming of the properties should be brought into line with what is defined in the aforementioned function. If applied as currently formatted, this patch will break rules which use most site properties, since the naming defined in this patch is different.
Comment #32
jduhls CreditAttribution: jduhls as a volunteer commentedI've got latest drupal and rules versions. I was able to cause this error using a poorly defined constant in my module:
This was cached somewhere I guess because my site would be stuck at WSOD and logging these errors. I had to clear the cache via the mysql cli (couldn't use
drush cc all
, although I could still usedrush sql-cli
):...then I could
drush cc all
and work on the site again.Comment #33
TR CreditAttribution: TR commentedThis issue was closed in #16. The overwhelming evidence is that is was caused by an old version of the UUID module - that module has since been updated and that solved the problem.
This issue was reopened in #28 for what appears to be an unrelated problem - the image in that post shows an Ajax 500 error, which is common in Drupal and probably not related to Rules except for the fact that it showed up during a Rules operation. No dblog error or web server error was given to show that this was a result of the same issue, and none of the subsequent comments give any indication that they are experiencing the error from the original post.
Because this issue has deviated significantly from the original post, and because the original issue seems to have been fixed, and because there has been no further information for years, I'm closing this as "outdated".
If you are still experiencing a problem, please open a new issue with details about how to reproduce your problem, including any error messages from the dblog and web server, along with the steps you had to take to get the error to show up on a clean site.