Wednesday, July 8, 2015
4 changes
New functionality added to Odoo
Website editors can now add a ready-made FAQ section where answers expand and collapse. This makes it easier to present common customer questions in a compact, polished format without custom development.
Enhancements to existing features
The U.S. check printing layout has been adjusted so top-positioned checks align correctly with QuickBooks-style forms. This improves printed check accuracy by refining margins, stub headings, payee placement, and amount positioning.
Original PR description
Check(Top) report is changed to make it compatible with Quickbooks Check(Top) layout.
Resolved issues and error corrections
This update replaces broken Bootstrap icons with the correct Font Awesome icons in several visible areas of Odoo. Users will see the intended icons again in the About dialog, chatter follow controls, and account reconciliation, reducing confusion and improving interface clarity.
Original PR description
…css/scss file accordingly
**Description:**
bootstrap glyphicon icons are broken and showing wrong icons
on following places,
1) "About Odoo" dialog (screenshot : https://goo.gl/LgMNwf )
2) Follow/unfollow button in chatter (task chatter screenshot : https://goo.gl/k66Dis )
3) Account Reconciliation (screenshot : https://goo.gl/cqfUpw )
please check [Issue here.](https://www.odoo.com/web#id=643481&view_type=form&model=project.issue&menu_id=4120&action=609)This fixes a data import issue that prevented Pentaho Kettle from creating new records in Odoo when it sent a placeholder ID value of zero. Businesses using Pentaho Kettle for data loading can now continue imports without errors caused by new-record identifiers.
Original PR description
Pentaho Kettle ships with "output steps" to lodd data into OpenERP/Odoo. A `.id` data column is always sent, but sisnce XMLRPC does not support `None` values, for the new records a zero is sent. This doesn't work with v8 since the server looks up for the zero `id` record, doesn't find it, and returns an error, making the OpenERP Output unusable. v7 initially featured the same problem and it was fixed.