Closed (won't fix)
Project:
Simplenews
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Jan 2009 at 21:58 UTC
Updated:
19 Jan 2009 at 03:47 UTC
on a multilingual site two newsletters are defined in taxonomy: one english, one for the other language.
go to the foreign lang site.
add a new newsletter, select the foreign language newsletter from the taxonomy dropdown selector.
Leave default "don't send now" radio button selected;
Save node.
Go to Edit the newly created newsletter.
Change the "don't send now" to "Send newsletter" radio button.
Click "Save and send".
ERROR Message results:
"You should select a newsletter term before you can send this newsletter issue."
When you go to select the term, befuddled as to why it "lost" the selected newsletter, the foreign term NO LONGER APPEARS IN THE LIST! When you were editing the node to change it to "Send newsletter", the term selection gets saved as the empty selection, cause it wasn't populated in the list of select options. :/
Originally tested on rc3, and d6 dev but this has been around since before as well. To me, this renders my multilingual implementation unusable and thus a critical error for the rc3.
Comments
Comment #1
jwilson3re-reading my post, it wasnt very clear on two key points
--- bold added on new words for clarity.
Comment #2
sutharsan commentedIt is a pitty you have not reported this issue before, it may have been less critical and for me more easy to investigate since it was fresh by then.
You need to describe your multilingual set-up (or give me access to a test server) so I can reproduce the situation. Describe i18n setup of both vocab, node and general.
Comment #3
jwilson3Sorry im a busy dude. ;) got a LOT going on.
I saw some potential errors show up with multilingual, not specifically THIS one, a while ago but other projects came up before i got a chance to do more investigating and i had no idea at that time things were headed towards release candidate mode... sorry.
I'll work on gathering the node/lang/setup info for you.
Comment #4
jwilson3• General
Home › Administer › Site configuration › Multilingual system
?q=admin/settings/i18n
Content selection mode: Only current language.
Home › Administer › Site configuration › Languages
?q=admin/settings/language
English default weight:0
Czech weight:1
• Node
Home › Administer › Content management › Newsletter issue
?q=admin/content/node-type/simplenews
(uses all the defaults as created by simplenews)
Identification
Type: simplenews
Workflow settings
Default options:
Published (yes)
Promoted (yes)
Multilingual support:
Disabled (this is disabled here because taxonomy multilanguage is enabled)
Attachments: Enabled
Extended language support: Normal
• Vocab
Home › Administer › Content management › Taxonomy › Edit vocabulary
?q=admin/content/taxonomy/edit/vocabulary/4 (simplenews)
Vocab name: Newsletter
Multilingual Options
Translation mode: Per language terms. Different terms will be allowed for each language and they can be translated.
Content Types
Newsletter issue
Settings
Multiple select (disabled)
Reqired (disabled)
Home › Administer › Content management › Taxonomy › Terms in Newsletter
?q=admin/content/taxonomy/4
List tab
Newsletter (English)
Novinky (Czech)
Translations tab
- No translations defined for this vocabular
Comment #5
sutharsan commentedI have reproduced the error. However the error also occurs when you create a node type 'story'. I turned out to be an i18n thing, not simplenews related. See #270655: Make content types with Multilingual support disabled Language Neutral by default. Use the latest dev release of i18n module and your issue is fixed.
Comment #6
jwilson3you mean use latest nightly dev snapshot, right? the latest release (6.x-1.0-beta6) doesnt work, as its what i've got installed right now.