Daily updates from Odoo
Monday, August 3, 2015
4 changes · master
Enhancements to existing features
Employees can now record timesheets without relying on a predefined “Service” product or a default employee setup, reducing setup errors and avoiding issues when that product is removed. Invoicing still requires a product, and if none is provided the system falls back to the sale journal account, with related accounting and budget calculations adjusted accordingly.
Original PR description
TASK: https://www.odoo.com/web#id=19616&view_type=form&model=project.task&action=327 PAD: https://pad.odoo.com/p/r.aSQyULesdtZ6QttD remove service: - crossvered.budget.line type selection (and update computation of budget) - all lines (default) - only without general account - budgetary position - add account.move.line_id on account.analytic.lines, set by the creator account move line - replace the general_account_id by a related (account.move.line_id.account_id) - Remove the "Service" product - Wizard to invoice product, if no product take the sale journal account_id
Recruitment tracking has been improved to make it easier to understand where applicants come from and to manage related website job links. This helps HR teams better measure hiring channels and reduces confusion from incorrect job URLs.
Original PR description
Task: https://www.odoo.com/web#id=12768&view_type=form&model=project.task&action=327 Pad: https://pad.odoo.com/p/r.1J9a7YRKtwcnYNgL
Resolved issues and error corrections
The update improves how Odoo handles duplicate invoice number conflicts by turning low-level database errors into clear user-facing messages. This helps users understand and resolve the issue instead of seeing a technical crash when posting invoices or using sequences.
Original PR description
Task: https://www.odoo.com/web?#id=13101&view_type=form&model=project.task&menu_id=3942&action=327 Pad: https://pad.odoo.com/p/r.qn2720iJzS0eIeb3
This fix prevents the website editor from failing in Firefox when it encounters stylesheets from another domain. Same-domain styles continue to work normally, while restricted external styles are safely skipped so users can keep editing without disruption.
Original PR description
…cssRules, it is due to Cross domain security policy of firefox, used try catch, so that if there is cross domain css then skip it, it should not break the system, atleast it should work for same domain css, cross domain css should skipped Issue: 644757