I would like images on my site to be available for all the languages. Unfortunately, with multilingual support for image content type disabled Drupal chooses default language (English for instance) for images added. Whereas it needed to make all the contents of content types with multi language support disabled language neutral. So I had to activate multilanguage support for image content type and ask users to chose Language Neutral when adding images. Whic does not make much sense, when all the images by default could be put Language Neutral.

Comments

ar-jan’s picture

ar-jan commented

I second that. I have exactly the same issue with Biblio Module. Users on my site inputting Biblio data can choose language neutral if multilingua is enabled, but I don't want to present them with a choice they shouldn't make.

ar-jan’s picture

ar-jan commented

Does anyone know of a hack to achieve this?

Alan Oliveira’s picture

Alan Oliveira commented

i place images on the node with FCK Editor + ICME and its images' show in all languages on the site i currenty building

Anonymous’s picture

Anonymous (not verified) commented

This is not an i18n issue. The locale module is setting the language in the edit form to the default language if there is no language selector. You could set the variable "language_default" to an empty string or unset node->language in the nodeapi hook, but the only clean way to do it is altering the form_alter hook with the same checks that the locale module is doing, e.g. leaving existing nodes untouched etc.

There should be a selector for the locale module letting the user specify what language nodes without multilingual settings should get, so you should submit this issue to drupal forums or the developer list.

If you have you own module, put this into your_module_form_alter:

  if (!(isset($form['#node']->type) && 
        variable_get('language_content_type_'. $form['#node']->type, 0))
      && !isset($form['#node']->nid)) {
    $form['language'] = array(
      '#type' => 'value',
      '#value' => '',
      );
  }
thepanz’s picture

thepanz commented

Maybe you may want to try preserve_language module that will have this feature soon (I hope).
Give a try to my patch here: #327545: Language for content types without language support must be Neutral

jose reyero’s picture

jose reyero commented
Status: Active » Fixed

Added into i18n module too.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

tobiberlin’s picture

tobiberlin
Primary language German
Location Berlin, Germany
commented
Status: Closed (fixed) » Active

Hi,

I want to re-open this issue... it was mentioned that the language "neutral" setting for content types with multilingual support disabled was added to i18n module. I use this module but the language for these nodes is still the currently active language.

Greez,
Tobias

tobiberlin’s picture

tobiberlin
Primary language German
Location Berlin, Germany
commented
Status: Active » Closed (fixed)

Ok... I am sorry for that. I found out why I was not able to save nodes as "language neutral": The module "Registration Language" offers the very nice possibility to save the language of the user while his registration process. It also offers a setting which enforces to save newly created nodes in the language the user has currently as active. I simply did not realize this setting and was starting to go crazy about the question how to save nodes as language neutral. So sorry for that stupid question!!!!