-- What are the steps required to reproduce the bug?
1) Create module with form
2) set, for example
$form['#attributes']['accept-charset'] = 'Windows-1251'
3) Form will have two "accept-charset" (with UTF-8 and with custom value)
-- What behavior were you expecting?
One accept-charset with custom value.
Patch sets UTF-8 as default accept-charset and we can override it from modules. I need this to send form to payment service and it accepts only Windows Cyrillic encoding. Patch was made from D6.14
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | accept_charset-624086-d6-9.patch | 910 bytes | albert volkman |
| #5 | accept-charset.patch | 1.09 KB | limikael |
| #2 | accept-charset.patch | 1.09 KB | limikael |
| accept-charset.patch | 918 bytes | dmitriy.trt |
Comments
Comment #1
lyricnz commentedPatch should be made from drupal root directory - see http://drupal.org/patch/create
The "if" clause should use braces around the conditional clause:
http://drupal.org/coding-standards
Does the same issue exist in D7? If so, it should be fixed there first, and back-ported. If not, the patch should probably be updated for 6.x-dev.
Comment #2
limikael commentedSince I would really like to see this issue fixed I created a new patch with curly braces and from the root directory.
The patch was made from CVS on Apr 8, 2010.
Please have a look.
Comment #4
limikael commentedThis issue is still present in D7, changing version.
Comment #5
limikael commentedResubmitting patch for D7
Comment #6
casey commentedLooks good.
Comment #7
dries commentedCommitted to CVS HEAD. Thanks.
Comment #8
moshe weitzman commentedComment #9
albert volkman commentedD6 backport.