Posted by andrewlevine on September 14, 2009 at 3:37pm
| Project: | Internationalization |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Ran into a bug where, by accident, I set the language of a vocabulary even though it was using the I18N_TAXONOMY_LOCALIZE mode. On vocabulary creation this isn't a problem and I went ahead and added my terms and everything was fine. Later when I updated the vocabulary to add it to a new content type, all of the vocabulary's terms were incorrectly set to the language I had set the vocabulary to on creation.
This behavior doesn't make sense for any mode besides I18N_TAXONOMY_LANGUAGE and the included patch stops this from happening.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| i18n_dontsetlang.patch | 1.68 KB | Ignored: Check issue status. | None | None |
Comments
#1
Agree, that's just because I'm a lazy guy and the form doesn't have prover validation.
I you want to implement the form validation, and/or add some js...
#2
Jose, attached is the patch using form validation and Javascript
#3
Forgot to mention, this patch applies to 6.x-1.x-dev with a fuzz factor (I wrote it against a non-dev version), but I've tested it on dev and it works fine.
#4
Great patch. Just added some more validation for the left case (no language selected).
Thank you!
#5
Automatically closed -- issue fixed for 2 weeks with no activity.