Reviewed & tested by the community
Project:
Entity Rules
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Feb 2014 at 11:35 UTC
Updated:
4 Mar 2019 at 14:02 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
vlooivlerke commentedThen i got these errors when i installed the entityforms_notifications module
Comment #2
todinov commentedI have the same issue.
After some debugging I found this line (line 498):
foreach ($enabled_types as $entity_type => $entity_type_info) {where enabled_types comes from (line 488):
$enabled_types = variable_get('entity_rules_types', explode(',' , ENTITY_RULES_DEFAULT_TYPES));To the best of my knowledge the entity_rules_types variable doesn't have any meaningful key values, so I changed the first row to:
foreach ($enabled_types as $entity_type) {For the moment this seems to have fixed the issue, however I'd appreciate if someone more involved in the module development can confirm if my sollution is correct.
Comment #3
alexweber commentedI got a similar error when trying to export entity_rules stuff to features. The components aren't listed properly via the UI although it's possible to export it by specifying the component name directly in the command line and it gets added to features.inc and works pretty much... although it does consistently throw the notices and warnings mentioned above.
Comment #4
vlooivlerke commentedHi, I changed line 569 from
to
this took the warning away.
The above patch suggestion caused another set of errors on my install
I have no idea what I have done and if this is a fix.
Comment #5
El Bandito commentedMe too.
Comment #6
maximilianmikus commentedComment #7
alexweber commentedComment #8
vlooivlerke commentedthis patch took the error message away for me
thanks
Comment #9
nicolas bouteille commented+1
Comment #10
Stan.Ezersky commented#4 and #6 work, thanks!
Comment #11
Rory commentedRTBC +1
Comment #12
mariacha1 commentedThis issue occurs if you have enabled the module but not yet gone to the settings page at admin/config/content/entityformIt has to do with the fact that the default value for the constant "ENTITY_RULES_DEFAULT_TYPES" is this:So keys there are 0, 1, 2but the "entity_rules_types" variable is stored in this manner:So the keys there are "user", "node" and so on.The problem is not solved by #6, but should be solved by saving your settings form and possibly clearing your cache.A better solution is still needed.Wow! Not sure what I was looking at. Sorry for this post. I'll put it back to RTBC.
Comment #13
mariacha1 commentedIgnore previous comment.
Comment #14
ciss commented$enabled_types contains a list of strings and has not been flipped. This should actually read:
The error has already been present before the patch, and we should take care of it as well.
Comment #15
ciss commentedComment #16
brightboldPatch in #15 eliminated the error for me, thanks.
Comment #17
Aldo F commentedPatch in #15 eliminated the error for me too, thanks. ;)
Comment #18
ciss commentedComment #19
gmclelland commentedPatch in #15 worked for me. Thanks everyone
Comment #20
Nodz commentedPatch in #15 works for me too.
Comment #21
anouPatch #15 ok for me too. Thanks
Comment #22
Syntapse commentedpatch #15 cleared the error on my site.
Comment #23
alfonsobarreiro commentedPatch #15 ok for me too. Thanks!
Comment #24
caldenjacobs commentedCan we get #15 committed?
Comment #25
nattyweb commentedPatch #15 worked for me with D7.51 and 7.x-1.0-alpha4+7-dev. It would be great if this is committed!
Comment #26
jimmy8646 commentedpatch #15 work for me Thanks :)
Comment #27
Syntapse commentedis this committed? thanks.
Comment #28
brightbold@laurencefass — when a patch is committed you'll see a note in the comments with the commit ID, and the status of the issue will be changed to Fixed. Since this one still has a status of RTBC and there's no commit notice, then you know it hasn't been committed yet.
Comment #29
proweb.ua commented#15 work