Closed (works as designed)
Project:
Field collection
Version:
7.x-1.0-beta9
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
19 Oct 2015 at 22:36 UTC
Updated:
15 Jun 2018 at 22:42 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
tusharbodke commentedHi,
Can I have complete message for "Notice: Undefined index:" problem. Want to know for which variable & line above issue is reported.
Thanks
Comment #3
youlikeit commentedHi
I get the same message
Notice: Undefined index: paragraphs_item in field_collection_host_entity_types() (line 143 of...www/sites/all/modules/field_collection/field_collection.tokens.inc).
Comment #4
tusharbodke commentedHi,
Please find attached patch to resolve reported issue.
let me know if anything.
Thanks
Comment #6
tusharbodke commentedComment #7
tusharbodke commentedComment #9
tusharbodke commentedComment #10
joshuautley commented#9 worked. Thank you.
Comment #11
tusharbodke commentedHi joshuautley,
Really nice to hear that.
Thanks
Comment #12
genjohnson commentedThe patch in #9 is working for me, too.
Comment #13
jmuzz commentedThe comment for the changed line of code states that the check being added is not necessary. It's hard to disagree with that. It would mean that the field collection field belongs to a host entity type that doesn't exist.
Can anybody describe a legitimate use case where this might happen or provide steps to reproduce the error from a clean installation? If so, perhaps the change can be committed with the comment removed.
Modules shouldn't necessarily attempt to support sites that have corrupted data by silently skipping steps. Consider that the error message may be the correct behaviour.
Comment #14
jmuzz commentedComment #15
frazras commentedYou can manually go into the database and remove the entries from the table for the problem field
Comment #16
nathan tsai commentedAs @frazras said, you can go to the `field_config` table in your D7 database and delete the instances of it.