Friday, January 16, 2015
3 changes
Enhancements to existing features
After signing in, portal users are now directed to the customer-facing website while regular internal users go to the backend. This makes the login experience clearer and reduces confusion by taking each user type directly to the area they are expected to use.
Original PR description
...login (and regulars users to the backend) on login
Odoo now uses clearer categories for common business errors, such as access issues, missing records, and validation problems. This should make user-facing error messages easier to understand while helping administrators focus on issues that truly need attention.
Original PR description
Unify and refactor exception handling in framework and addons. ## Unified exceptions The generic `except_osv` is now deprecated, and replaced by more specialized exception subtypes: - `UserError`…
Unify and refactor exception handling in framework and addons. ## Unified exceptions The generic `except_osv` is now deprecated, and replaced by more specialized exception subtypes: - `UserError` (renamed from Warning, as it conflicts with the built-in `Warning`) raised when a non-technical error occurs during a business operation. It could be a missing information in the data provided by the user, or a misconfiguration. - `AccessError`: raised when any operation is denied because the user conducting it does not have the required access rights. - `AccessDenied`: raised when an operation that requires authenticated access is attempted via an unauthenticated request. - `MissingError`: raised when an operation is attempted on a record that does not exist. - `ValidationError`: raised when an operation violates a SQL or Python constraint. - All other exceptions are internal errors due to a system problem or bug, and raised untouched to the client-side, which should display a traceback. All exceptions take a single message argument. The `test_exceptions` module has been updated to showcase both new and old (deprecated) exceptions. ## Error messages A great many old `except_osv` had a useless title with "Error!" or "Warning", those have been removed, as this is handled by the client-side widget that displays the messages. ## Error logging This commit introduces a more consistent policy for logging errors and warnings: - All messages that do not require administrator attention should be logged at INFO level or lower. This includes all errors that are notified to the user in a friendly manner, even for access right problems or validation errors during business operations. - All messages that indicate a likely misconfiguration or malicious use by the users should be logged at WARNING level, as they typically require administrator attention. - All other unhandled internal errors cannot typically be handled by the user and should be logged at ERROR or higher level, as they require immediate administrator attention. --- With the previous pull-request: https://github.com/odoo/odoo/pull/3991
This update replaces older custom icons with Font Awesome icons across several Odoo screens, including kanban views, messaging, HR, CRM, calendar, events, and accounting reconciliation. Users should see more consistent and modern icons throughout the interface without changes to business workflows.
Original PR description
Task : https://www.odoo.com/web#id=11341&view_type=form&model=project.task&action=333&active_id=248 PAD : https://pad.odoo.com/p/r.z1Un2P1BZ2xDtjY7