Daily updates from Odoo
Tuesday, September 16, 2014
7 changes · master
New functionality added to Odoo
A new generic “Miscellaneous” product has been added for use in Point of Sale and product records. This gives businesses a ready-made item for ad hoc sales or charges that do not fit an existing product category.
Original PR description
- Task: https://www.odoo.com/web/#id=9109&view_type=form&model=project.task&action=333&active_id=131 - Pad: https://pad.odoo.com/p/r.YBclg3RUX64e7UYL
Enhancements to existing features
The “Add an item” prompt in many-to-many fields is now shown in bold, matching the visual style already used elsewhere in Odoo. This creates a more consistent and polished form experience for users.
Original PR description
Purpose : 'Add an item' text in many2many widget should be bold to maintain a standard aesthetic in odoo. It is happened because class for one2many is added in base.css twise. so replace one of them with class for many2many. See the task. Task : https://www.odoo.com/web#id=9024&view_type=form&model=project.task&menu_id=3942&action=327
The manufacturing configuration no longer shows the manufacturer module option. This reduces clutter in settings and helps users focus on relevant manufacturing choices.
Original PR description
IMP #918: Remove module_product_manufacturer in addons/mrp/res_config.py
Landed cost valuation adjustments are now shown as read-only, removing the option to manually add lines. This keeps the screen aligned with the intended process, where adjustment values are generated automatically from pickings, reducing accidental manual changes.
Original PR description
Purpose : In WMS > Landed Costs : No need of " Add an item " in Valuation Adjustments, because all values of valuation adjustments generate automatically from pickings. So, valuation_adjustment_line field should be readonly. Task : https://www.odoo.com/web#id=9363&view_type=form&model=project.task&menu_id=3942&action=327
Resolved issues and error corrections
Module updates now keep database rules in place unless their original definition has actually changed. This prevents needless constraint drops and rebuilds, making updates safer and reducing avoidable database work.
Original PR description
When a module is updated, the sql constraints were checked against postgres `pg_get_constraintdef()` method to see if they have diverged from the one defined in python code. However this check was failing as the syntax returned by `pg_get_constraintdef()` (e.g. `CHECK ((credit * debit) = 0::numeric)`) differs from the one returned by `unify_cons_text` method (e.g. `check(debit*credit = 0)`) so the constraints were always dropped and recomputed. This adds a definition column on ir.model.constraint (storing original definition) to detect changes. This will also update the field `date_update` when the definition changes.
The online shop product page layout was adjusted so the search box uses the available page width more consistently. This helps prevent the search area from appearing too narrow, improving the shopping experience for visitors.
Original PR description
<b>Specification:</b> Bootstrap CSS class to fix this issue.
website_sale module » views » templetes.xml (id="product" template)
» Exisiting <code><div class="row">..</div></code>
» Add col-md-12 and center-block class
<b>Task:</b> https://www.odoo.com/web#id=9654&view_type=form&model=project.task&menu_id=3942&action=327
<b>Pad:</b> https://pad.odoo.com/p/r.bofwElvy1bAQy3spFeatures or functions removed from Odoo
The pull request removes Odoo's bundled pyPdf code from the reporting area. This reduces outdated internal code and dependency maintenance, with little expected business impact unless custom reporting relied directly on that bundled library.
Original PR description
Hello, I have remove openerp/report/pyPdf... More details: Task link :- https://openerp.my.openerp.com/web#id=9120&view_type=form&model=project.task&menu_id=3942&action=327 Pad link :- https://pad.odoo.com/p/r.83pH7GnykB0Zlwm8 Thanks, Sunil Sharma (ssh-odoo)