I am getting an error for every row in my CSV import.

To test this, I created a new content type with translation ability.

I also created a new feed to simply import a id and name.

I keep getting the following errors....

Notice: Undefined property: stdClass::$language in EntityTranslationNodeHandler->getLanguage() : ON LINE 25 of translation.handler.node.inc

This is isolated only for node items and does not occur with another entity type.

Comments

rtdean93’s picture

rtdean93 commented

This also only occurs when both Entity Translation and Multilingual content are both enabled. Essentially, it renders my translate tab unworkable.

I'm using the latest dev of Entity Translation and i18n - 7.x-1.3

If I disable, Content Multi-language - the error goes away, but I have other nodes that need this translation ability.

mustername’s picture

mustername commented
Component: Code » Base system

I encountered this problem in D7.14 with ET-1.0-alpha1, i18n-1.5 and administration language-dev in a content type for which i did not have content translation switched on. It seems that the message is the only thing that happens, the created nodes looked like they were supposed to, right language, right path language.
The error message disappears if i turn the admin_language off, but i do need the three modules.
Why does the ET module interact with language neutral nodes? the "Don't flag translation as outdated" option is always shown, even with multilingual support off?!

mustername’s picture

mustername commented

I used a backup where I disabled administration language module but the problem still persist.
At some point I could not add any new entities.
when using ET 1.0-alpha1 the Notice message is:

Notice: Undefined index: class in entity_translation_get_handler() (line 494 ...entity_translation.module)

I could not add comments or edit the nodes, or even create new entities, as i always received the 'white screen', even for content types with disabled translation, I had to completely disable the ET module.

after upgrading to the dev version i get now:

Notice: Undefined index: base path in EntityTranslationDefaultHandler->__construct() (line 193 ...entity_translation/includes/translation.handler.inc)
Notice: Undefined index: path wildcard in EntityTranslationDefaultHandler->getPathInstance() (line 499 of ...entity_translation/includes/translation.handler.inc)

but can add comments and nodes...

mustername’s picture

mustername commented

just updated to the new alpha2, same error as in the dev.
I think line 193 in includes/translation.handler.inc should be

$this->basePath = isset($info['base path']) ? $this->getPathInstance($info['base path']) : FALSE;

as in my case, the entity_translation value is a string, EntityTranslationDefaultHandler, not an array.

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented

Nope, the base path cannot be false. It seems your entity info is corrupt.

Possibly related: #1631958: Undefined index: base path in EntityTranslationDefaultHandler.

mustername’s picture

mustername commented

well the 'false' base path sounded like a bad duct tape approach, so thank you for the replay and the proper solution. I was looking in the i18n_translation array, as the node array it did not have an 'EntityTranslationDefaultHandler' entry.
It also makes sense now, why the error occurred with content types which did not have ET enabled, as I was using the title field module, also a great module.

Anyway the error disappeared now. Thanks for your great work.

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented
Status: Active » Closed (cannot reproduce)

Feel free to reopen if this pops up again.