unicode support for field_description field in ir_model_fields
Bug #1231900 reported by
David BEAL (ak)
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Odoo Server (MOVED TO GITHUB) |
Fix Released
|
Medium
|
OpenERP's Framework R&D | |||
| 7.0 |
Fix Released
|
Medium
|
Unassigned | |||
| OpenERP Community Backports (Server) | Status tracked in 7.0 | |||||
| 7.0 |
Fix Released
|
Medium
|
OpenERP Community Backports | |||
Bug Description
field_description field in ir_model_fields class doesn't support unicode chars with write method
How to reproduce the bug :
Goto Settings/
Create any field and save it.
It works, OK
rename field label with some non ascii 128 chars (example : é è ç à ë § £ µ)
It crash because create and write method don't use the same way to record data
Here is my patch :
https:/
Related branches
lp:~akretion-team/openobject-server/openobject-server-fix-ir_model-field_description
- Raphaël Valyi - http://www.akretion.com (community): Approve
- OpenERP Core Team: Pending requested
-
Diff: 43 lines (+5/-5)1 file modifiedopenerp/addons/base/ir/ir_model.py (+5/-5)
lp:~akretion-team/ocb-server/openobject-server-fix-ir_model-field_description
- Holger Brunn (Therp): Approve (code review)
- Stefan Rijnhart (Opener): Needs Fixing
- Pedro Manuel Baeza: Approve
- Raphaël Valyi - http://www.akretion.com: Approve
-
Diff: 12 lines (+1/-1)1 file modifiedopenerp/addons/base/ir/ir_model.py (+1/-1)
| description: | updated |
Revision history for this message
| Raphaël Valyi - http://www.akretion.com (rvalyi) wrote | #1 |
Revision history for this message
| Twinkle Christian(OpenERP) (tch-openerp) wrote | #2 |
| Changed in openobject-server: | |
| assignee: | nobody → OpenERP's Framework R&D (openerp-dev-framework) |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| Stefan Rijnhart (Opener) (stefan-opener) wrote | #3 |
| Changed in openobject-server: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Hehe I confirm the bug, we hit it too like 10 days ago to and made a ugly workaround in to get our use case pass. I'll look at your patch proposal. Thanks for reporting.