Closed (fixed)
Project:
Entity Translation
Version:
7.x-1.x-dev
Component:
Base system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Jan 2014 at 16:47 UTC
Updated:
14 Oct 2014 at 17:22 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
atin81 commentedSame error here using dev version, and same error on beta3 version but on line 187
Comment #2
plachDoes this happen on a clean installation? If not please post the steps to replicate the error.
Comment #3
atin81 commentedIn my case the problem was originated by not having enabled the comment module. After enable comment module I could install this one with out problem.
Comment #4
Jānis Bebrītis commentedI stumbled access the same issue, fixed it by enabling comment module *before* enabling entity_translation.
my fix was creating array key when it doesn't exist, works fine, probably fixes other entities aswell, possibly related to #2001668: Location breaks entity translation
My fix
Comment #5
Jānis Bebrītis commentedComment #6
socialnicheguru commentedis there anyway to print which module does not have an entity bundle defined to watchdog?
Comment #7
plachIt's weird that the comment module is causing troubles: there's a check about it being installed (see
entity_translation_entity_info())Comment #8
plachComment #9
Jānis Bebrītis commentedit was comments, i did print_r and it broke on it.
Comment #10
atin81 commentedSame here, I did several testing to find that the problem was originated by comments module.
Comment #11
guillaumev commentedHad the same issue and the patch in #5 fixed it.
Comment #12
dkingofpa commentedPatch in #5 fixed the issue for me. I just updated it to follow drupal coding conventions.
Comment #13
basillic commented#12 works for me.
An alternative coding style would be:
$entity_info[$entity_type]['entity keys']['translations'] = 'translations';Comment #14
Helrunar commentedPatch in #12 works for me
Comment #16
plachCommitted and pushed, thanks.