Undefined index: und in the function _classified_list_nodes()

Can not reproduce. Can you detail how to reproduce this, starting from a fresh D7 install ?

Looking at the code, this could mean that your body field was never created: was it a fresh install or an attempt to upgrade from a site previously holding another version ?

I have just committed a detection for a missing body field when configuring the module. If you used the latest dev rolled today or a current git checkout, this check is included and it will prevent validating configuration when the body field is missing. This will let you know more easily if this is the problem or not.

Same problem with the latest dev build (Aug 26). This is not an upgraded D6 site.

Notice : Undefined index: und dans _classified_list_nodes() (ligne 386 dans /home/public_html/sites/all/modules/ed_classified/classified.module).

Same question as #1: Can you detail how to reproduce this, starting from a fresh D7 install ? I haven't been able to reproduce the problem. It could mean that your body field

- either was not created
- or was created with a language set

But in 6.x-3.0/7.x-3.0 the module only supports language-neutral content. Can you paste the result of dsm(node_load(your_ad_nid));, and confirm you are not using locale, content_translation, i18n or any multilingual mechanism. This being said, I have also set up D7 with content translation, and also with entity translation (translatable fields) and it took a very specific configuration to reproduce the problem:

- content translation enabled
- multiple languages enabled
- ad content type is marked as translatable, but is not input in language-neutral form.

Non-language-neutral content is not going to be supported for 6.x-3.0/7.x-3.0. If this is the situation in which you are, this type of of features is roadmapped for 6.x-3.1/7.x-3.1. Is this your situation ?

Yes, my site is in French. Is there a temporary hack I could use till 7.x-3.1 is released?

If the site is only in french you could declare the content as language neutral instead of declaring it to be french (disable multilingual on the content type admin page): that way any module also assuming language neutral content would still work normally too, and since the content language is independent from the interface language, it should not prevent everything from appearing in french normally.

Otherwise you could probably hack the module and replace every appearance of LANGUAGE_NONE by 'fr' (quotes needed).

I would say it's the opposite : when multilingual is disabled for the content type, the ads are created with the default language (french) generating the errors messages. If I enable multilingual and leave the default (language neutral) when creating the ad then the errors don't show.

That is consistent with what I said: if multilingual is disabled, new ads created after disabling multilingual will be language-neutral and not cause problems.

But Drupal will not remove the language on nodes already tagged with a specific language: these must be deleted or the language removed in the DB.

Then we have the workaround you found : enable multilingual and leave the default (language neutral) when creating the ad.

There will not be further multilingual support in the first actual 7.3 release anyway, especially since that workaround exists. Probably for the next version.