Daily updates from Odoo
Sunday, December 21, 2014
10 changes
Resolved issues and error corrections
This fixes how product price surcharges are applied so they align with the product's unit of measure. Businesses should see more accurate pricelist calculations when products use different units, reducing pricing errors for sales and purchasing.
This update makes a small correction to the project's README documentation. It helps keep public project information accurate and easier to follow, with no expected impact on product behavior.
This fixes an issue where switching between views could leave empty page containers visible when no controller was attached. Users should see cleaner, more consistent screens without stray blank areas caused by styling.
Original PR description
The view manager upon switch won't properly hide the empty `div` container for other views when they don't already have a controller. CSS might then show these div quite easily. It seems pretty obvious that they should be hidden properly even if empty.
This update addresses reported issue #988 with fixes spanning messaging, website interactions, recruitment, accounting, stock, portal access, events, blogs, and mass mailing. It should improve reliability for users working with communications and public-facing website features while reducing errors in related business workflows.
Original PR description
About Issue #988
This update corrects the alignment of the Weight field on the stock move form. It makes the form display more consistently, reducing visual confusion for users working with delivery or inventory details.
Original PR description
Hello, Fixed the Issue #541 (#541) In stock move form set the group alignment on "Weight " field. Thanks.
Odoo now prevents users from deleting accounting accounts that are still referenced by tax settings. This helps avoid broken tax configurations and reduces the risk of accounting errors caused by removing accounts that are still needed.
This fixes a missing field on sales order lines related to bill of materials options. It ensures sales users can see and use the expected product properties when working with manufacturing-related sales orders.
Original PR description
I guess the `property_ids` field has been left behind when moving the filed from `sale_stock` to `sale_mrp`.
A missing internal translation helper and service import were added to the common server service. This prevents errors in the about information workflow and keeps the server service loading reliably.
Original PR description
Add missing 'openerp.tools.translate._' function for the 'exp_about()' method and add relative import for the 'openerp.service.security' module.
Incoming emails are now matched to contacts using a stricter email comparison. This helps prevent messages from being linked to the wrong customer when similar email addresses exist.
Original PR description
The current operator is ilike but it add wildcards around right criteria so we can have false positive. eg. I' have an email in my customer base like a_mail@provider.com If I get a mail from mail@provider.com as ilike operator uses wildcards a_mail@provider.com can potentially be matched and retrun a faulty match.
Manufacturing orders created from procurement now calculate their required components only once instead of repeating the same step during confirmation. This reduces unnecessary processing and helps improve performance while still respecting the procurement order's bill of materials properties.
Original PR description
I assume that the reason to call `action_compute` method in `procurement.make_mo` is to pass in the `properties` parameters , and thus the BOM of the generated MO will be selected according to the BOM Properties on the related procurement order. However, the action_compute will be called the second time by the workflow when the MO is confirmed. The double call of the `action_compute` method caused performance issue <s>and those unnecessary unlink product_lines process.</s> This fix take care of the bom properties match inside action_compute, and thus remove the needs to call `action_compute` in `procurement.make_mo`.