Just updated on cvs a new feature : optional support for different contents types.
It is an extension of the already present forum support.

You need the last localizer.module and localizernode.module from the cvs

Comments

Wuk’s picture

Wuk commented

What does it mean to disable support for content type?

The thing is that after I disable support for some content type eg. forum/page, I can see locale dropdown list with possibility to choose language or any.

IMO I should not be able to choose language, but language should be set to "Any" without me knowing that there is possibility to choose language.

huayen’s picture

huayen commented

You need the last localizer.module and localizernode.module from the cvs

So, we need to patch these two files again?

huayen’s picture

huayen commented

BTW, another question about using patch files.

I patched the files under shell command. My question is: if I uninstall localizer module, will those patched files be rollback to original status? Or I have to keep an original copy before I install localizer module? Thanks.

Roberto Gerola’s picture

Roberto Gerola commented

>What does it mean to disable support for content type?
You can decide for each content type if the rewriting rules of localzier should be applied
or not.
For example, you would like to have forum only in one language and see all the posts
regardless of the selected language.

Roberto Gerola’s picture

Roberto Gerola commented

> So, we need to patch these two files again?
If you have already pached them it isn't necessary.

>will those patched files be rollback to original status?
The patches are written to work also if localizer is removed.
If localizer is not used, the "patched behavior" is simply not executed.

Roberto Gerola’s picture

Roberto Gerola commented

>IMO I should not be able to choose language, but language should be set to "Any"
>without me knowing that there is possibility to choose language.

You are right.
I'll fix also this.

Thanks

Roberto Gerola’s picture

Roberto Gerola commented

Now the languages list appears in the edit form only for selected contents types.

Wuk’s picture

Wuk commented

Thank you for everything you have done.

I have another request, I have content type with disabled localizer support for it.
The "Translations" link still appears in node body/header, and when I click on that link I get SQL errors.
Could you, please, remove it (and also when someone tries to enter it through address bar "...node/x/localizernode).

Roberto Gerola’s picture

Roberto Gerola commented

Yes, I see that I have missed to hide it.
I'll fix it. Thanks.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Active » Fixed

Seems like this is fixed in the latest development snapshot.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)