Multilanguage variables not working

[pkej]

Prosepoint doesn't work with i18n menu translations and variable translations as per this page http://drupal.org/node/313272.

I have made this work with drupal6.6 and the same modules under garland.

Unfortunately this is a dealbreaker, so I'll just modify a normal 6.6 site for my project.

[bengtan (bengtan)]

Hi,

Sorry, I don't quite understand.

I know what http://drupal.org/node/313272 says, but not how it is an issue for you. Are you saying if you edit settings.php to create multilingual variables, it doesn't work for ProsePoint?

Or if it's something else, can you give me a specific example?

If it's a bug or misconfiguration in ProsePoint, I can certainly try to get it fixed.

[pkej (paul-k-egell-johnsen)]

I have a settings.php file with mulitilingual variables. In prosepoint and drupal 6.6 you can see that the fields gets the text <b>multilingual variable</b> appended in the interface.

However, when I try to for example change the site name to reflect different languages, the name will always be the latest name I changed it to, regardless of which language I have selected.

So, if I go to http://localhost/blog/en/admin/settings/site-information and change the name to Blog and save the page, then go to http://localhost/blog/no/admin/settings/site-information and change the name to Blogg, the name will be Blogg when I go back to http://localhost/blog/en/admin/settings/site-information.

The different names are not saved properly.

I tried with menus, anonymous user, etc.

[bengtan (bengtan)]

Hi,

I've tried to do as you've described, and ProsePoint behaves the same as Drupal 6.6, which is a different result from what you're reporting.

What I've did for Drupal 6.6:

Install Drupal 6.6.
Add module i18n 6.x-1.0beta6 (no other modules are involved).
Make site_name a multilingual variable by inserting in settings.php:

$conf['i18n_variables'] = array(
  // Site name, slogan, mission, etc..
  'site_name',
);

Add a foreign language (nb)
Add a path prefix 'en' for the default language (English)

Visit .../en/admin/settings/site-information and .../nb/admin/settings/site-information. Confirm that *This is a multilingual variable.* appears for 'Name:' on both pages.

Set 'Name:' in both pages to different values. Refresh both pages in browser. 'Name:' is working fine and has different values for both pages.

Then I did the same for ProsePoint and got the same results: Name works as a multilingual variable.

Obviously, ProsePoint installs many more modules than Drupal 6.6, but i18n is the only 'non-ProsePoint-core' module I added.

And I used the latest (development) version of ProsePoint which is slightly changed from ProsePoint 0.10, but there is no multilingual-related code in ProsePoint so the ProsePoint version should not matter.

So ...

I can't reproduce your issue. If I can't reproduce it, I can't fix it.

Is there anything you've done on your site which I haven't done in my steps listed above?

[pkej (paul-k-egell-johnsen)]

It works here as well.

I didn't follow the install instructions exactly. I took a few shortcuts. When I did it step by step, and then added the i18n variables after the prosepoint site was working, I got things to work.

Thank you very much for your time and patience.

Now the only problem is that I get all images of all languages listed, instead of just those which are translated. Good when the images haven't been translated (yet), but when the site has a lot of images, it would probably be better to have an option to filter the list by the current language. The Captions are language dependent, you know.

KUDOS, though, for creating an image insert popup which works with CCK image fields, thus the translation engine can let the images keep the same image file on the harddisk, so no space is wasted. Marvellous.

[bengtan (bengtan)]

Hi,

Good to hear. Now we have a common baseline to work from.

I've used i18n on a Drupal 5.x site before, but not on a 6.x site, so I'm not aware what the current status is but ...

I assume you've made the content type ifimage a multilingual type. The caption field is just the usual node body field, but with a ..._form_alter hook to make it a single-line textfield rather than a text area. The CCK imagefield ... I don't know whether it respects i18n or not. Perhaps you can confirm for me?

ProsePoint 0.11 and onwards has an image gallery feature, and the image insert picker also lets you filter images by gallery. If you know how to configure the images_list view, you could try adding a language filter to the image picker.

> Now the only problem is that I get all images of all languages listed,

If you tell me how or if you solve this problem for yourself, I'd consider merging it into ProsePoint (as much as practical, given ProsePoint doesn't enable i18n out of the box).

Also, I'm going to change this bug to invalid, since the original issue is resolved.

Depending on how this discussion continues, you might like to file a new bug or question, or something.

[pkej (paul-k-egell-johnsen)]

Thank you, I did what you say, and exposed the filter, and voilá it is the best solution ever for Drupal! I had already made the prosepoint image type to a multilanguage type, and set "Synchronize Translations" to synchronize CCK fields Image.

This works great. I'm going to move a few sites to Prosepoint because of how well it supports multilanguage editing.

I'm going to install the "imagefield import" module now to import a small site (faster than creating an sql export/import).