Opened 17 years ago
Closed 17 years ago
#4403 closed (fixed)
[unicode] Form._html_output() crashed if errors_on_separate_row is True and form has errors
| Reported by: | Owned by: | Malcolm Tredinnick | |
|---|---|---|---|
| Component: | Forms | Version: | other branch |
| Severity: | Keywords: | unicode | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Subj. Use form.as_p() if you want to see this bug.
Attachments (1)
Change History (6)
by , 17 years ago
| Attachment: | unicode-newforms-path.diff added |
|---|
comment:1 by , 17 years ago
comment:2 by , 17 years ago
| Owner: | changed from to |
|---|---|
| Summary: | unicode: Form._html_output() crashed if errors_on_separate_row is True and form has errors → [unicode] Form._html_output() crashed if errors_on_separate_row is True and form has errors |
comment:3 by , 17 years ago
| Keywords: | unicode-branch added |
|---|
comment:4 by , 17 years ago
| Keywords: | unicode-branch removed |
|---|
Removing the unicode-branch keyword because I'm using that for bugs on trunk that are fixed on the branch. We know this ticket is for the unicode branch because of the [unicode] prefix in the summary.
comment:5 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Thanks for the report.
That patch isn't the right solution because the force_unicode() call is needed for python 2.3. It does highlight that there's a bug further down when I don't call force_unicode() on bf_errors in the normal processing path, though.
The proper fix is to add a
__unicode__method to ErrorList, I suspect. I'll fix that shortly.