not working - strange behavior

Thanks for the report... I'm checking your examples pages and thinking! ...

I checked your pages - for me *everything* is appearing in English. I doubt if Language Sections is the problem - something more basic maybe.

One point, the module is an "Input Filter" - with these, the order of execution can be important. I suggest you make Language Sections one of the first filters in the chain of filters.

The module is in use on my live site - www.axlan.com - and is working perfectly there. I don't think that your problem is a bug in Language Sections, though it's a possibility.

Let me know more information and I'll try to help more.

edited - not relevant

edited - not relevant.

Ok, I think I have finally found the cause - it's a caching problem.

If you want a quick fix, I think this will work: Edit the language_sections.module file and find these lines:

case 'no cache':
return false;

... change the second line to:

return true;

It seems that Drupal does not cache filtered text on a per-language basis as I thought. This means, apparently, you see a cached version of the text when you switch languages, so the wrong version. It's just coincidence that when I tested it on my site, this problem didn't occur, probably because some other input filter in the format-set was already preventing caching.

This also means that for performance reasons it would be better not to enable language_sections on a page unless its actually needed - by preventing caching, these pages may load more slowly. Just create one "standard text" input filter set and one "multi-language" input filter set.

This is something of a limitation in Drupal caching - if the caching were done on a per-language basis, this would not be a problem. I will look for a better solution rather than disabling caching for the text, but I don't think there will be one other than a patch to the caching logic in the core, which would probably not be a good idea.

Let me know if you implement the patch and if it works for you. I think it will.

Hi hatsch, thanks for offer of beer, always appreciated :)

The strange thing is, I cannot duplicate this caching problem on my live nor test site. I guess it's something to do with my combination of modules compared with yours.

Anyway, I've uploaded a new dev version in which you can configure the "cache" setting - it's defaults to "no cache" for safety.
The .module is here:
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/language_se...
.. the gz package will be available when drupal.org updates the listing.

About the teasers -- I hadn't tested it with teasers - I usually only use full node display. Are you saying it's a problem or just a quirk?

FYI, I'm working on another language module to simplify things in CCK and Views. Solves some problems, e.g. if you are defining CCK fields you can define field titles for 2 languages instead of having to use the string translations, which is not so easy to manage. Also in Views, field headings are easier to set up. I'll upload a beta release soon.