In reviewing the changes between 1.6-1.7 I didn't realize there was an Any locale setting for the parent node. This is highly useful for me since my site is going to have a fair amount translated, but some content doesn't need to be translated. As a result I if I create content as my default locale (which is the default in the drop down), it will not show under any other language unless global views is set to true. I don't want global views because we are not trying to create different content for different locales. We want all the same content translated or in English.
So I think it is beneficial for users to have the locale set to Any by default. This way they don't have to work about setting to Any when they go to create content visible for all locales.
So here is a patch that makes it an option.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | localizer_4.patch | 2.07 KB | sun |
| #3 | localizer_default_content_1.patch | 1.32 KB | pearcec |
| #2 | localizer_default_content_0.patch | 1.37 KB | pearcec |
| localizer_default_content.patch | 14.6 KB | pearcec |
Comments
Comment #1
Roberto Gerola commentedHi.
It this patch correct ?
It seems to me that it removes a lot of code.
>So I think it is beneficial for users to have the locale set to Any by default.
Yes, I agree with you.
Thanks.
Comment #2
pearcec commentedYea I blew it. Here is the fixed version.
Comment #3
pearcec commentedThis patch is better. What I had before override everything. Which didn't work if you were editing an existing translation.
Comment #4
sunUpdated patch against latest HEAD.
Comment #5
sunCommitted to 5.x.
Comment #6
(not verified) commented