Notice: Undefined index: en in _nodeconnect_field_attach_form()

@jucallme

This seems like a caching issue of some sort. as that value of en is getting passed in maybe there is some content that is still marked as being english?

Here is the error message:

Notice: Undefined index: en in _nodeconnect_field_attach_form() (line 14 of /home/penbgcom/public_html/npack/sites/all/modules/nodeconnect/nodeconnect.form.inc).
Warning: Invalid argument supplied for foreach() in _nodeconnect_field_attach_form() (line 14 of /home/penbgcom/public_html/npack/sites/all/modules/nodeconnect/nodeconnect.form.inc).

This occurs when I create a new node with nodeconnect and then reopen it to edit. The module is working but the message is there. I don't have i18n module and the the Multilingual support is disabled for this node type.

bump, i have the same issue with the latest dev version on a multilanguage site

I ran into this on a site I was working on. In our case we used Features for some content types. When a new field is added to a content type on a multilingual site, the exported feature code shows:
'translatable' => '0',
in the *_field.inc file. This causes the $language of the field to be "und" instead of "en" (or whatever your default language is). When nodeconnect tries to loop through the form using
foreach ($form[$field_name][$language] as $key => $field) ...
it fails because this field doesn't have a correct language entry.

In our case, editing the feature *_field.inc file and changing 'translatable' to 1 like this:
'translatable' => '1',
and then clearing the Drupal cache fixes the problem.

I'm not sure if this is really something for NodeConnect to fix or not. If you have a field in your content type with the wrong language, that will probably cause issues elsewhere on your site.

If you turned on Content translation, that probably got the language fields in your content type updated to "en" and then when you turned it off, the language of the fields might have been changed to "und". You would then need to somehow set your site's language back to "und" to fix this error.

In any case, my advice for anybody with this error is to go to the content type for the type of node you are editing and Export it and look at the export to see what the values of the translatable property are. If you are not using Features, I'm not exactly sure how to fix it other than some raw database editing, but somebody else might have a solution.

I have the same Problem:

Configuration:
- default language is GERMAN
- Content Translation DISABLED because it's a non multilanguage site. don't need to translate fields.
- Module Locale activated for Suface Translation from english to german
- Module Nodeconnect 7.x-1.x-dev installed

The nodereference field i use with nodeconnect has the field language = 'und' because it's not translatable.

Now i did the following steps:
Step 1:
- I create a new node: Error does not appear because $langcode (from _nodeconnect_field_attach_form()) is set to 'und'
- could create reference node with nodeconnect, no problems.

Step 2:
- open up again the same node: Error appears because $langcode is se to "de"

Is there a possiblity to fix this somehow or create a workaround?

thnx in advance

so I am not sure if this could effect it but on line 28

'#language' => 'und',

This seems wrong and we should be using what comes in from the function call.

Attached is a patch for this (I am going to commit it any way as this is a bug) can you all see if this is some how causing the issue?

Didn't work for me.
Setting
$language ='und';
on line 15 removed the error for me,
although this is just a dirty hack

1) instead of 'und' the constant LANGUAGE_NONE should be used
2) its not taking field specific languages into account.. some fields can be 'und', others can be localised.

I'm not sure if I should fix it in that function or in the function calling it (or elsewhere?)..
But here's a quick patch anyway
(patch created at Coworks)

This patch works fine for me.
Many thanks rv0.

Ok this is clearly the right way and if it fixes the problem even better!
will commit

Thanks for the patch, (and the typo fix)

commit 7d0ea3bf0a1e38c9601c6de25aaabd435ee810aa
Date: Tue Sep 13 11:26:30 2011 -0400

Issue #1194454 by rv0 at Coworks : Notice: Undefined index: en in _nodeconnect_field_attach_form()