Friday, February 22, 2019
3 changes · master
Enhancements to existing features
On smaller screens, onboarding bars now use horizontal scrolling instead of taking up a tall vertical area. This gives users more room to see the main app content sooner, especially in apps like Invoicing and Website.
Original PR description
- improve onboarding bars design on mobile: Use horizontal scroll task: 1929048 Description of the issue/feature this PR addresses: Replace the vertical scroll on the onboarding bars by a horizontal scroll to gain space on small devices Current behavior before PR: The design of the onboarding widget on the application like Invoicing or Website is taking a lot of space on mobile. Desired behavior after PR is merged: Replace the vertical scroll on the onboarding bars by a horizontal scroll to gain space on small devices Task: https://www.odoo.com/web#id=1929048&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.604964ed2b5912583e9d8f63429dec47 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds documentation explaining how to connect Odoo to incoming mail servers such as Postfix or Exim using the mail gateway script. It helps administrators route incoming emails into Odoo more reliably by providing clearer setup instructions.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This fix keeps child contact company assignments aligned with their parent company when the parent has a specific company, preventing access errors in multi-company setups. Parent contacts without a company can still have child contacts assigned to different companies, preserving valid shared-contact workflows.
Original PR description
Let the database be in multi-company with unshared contact catalog. Let F be a filter "('partner_id', 'not ilike', 'string')" on invoices. If there is a contact which parent belongs to another…
Let the database be in multi-company with unshared contact catalog.
Let F be a filter "('partner_id', 'not ilike', 'string')" on invoices.
If there is a contact which parent belongs to another company,
then this parent cannot be read.
Thus the name_get on partner can create an access error.
As a result applying the filter F would fail and return no results.
It generally doesn't make much sense to have a contact company X, which belongs
to the Odoo Company OC1, while its child contacts are in another Odoo company,
since many fields are directly computed from the parent.
However it is useful to have X belongs to no company, while it has child
contacts X>Yi belonging to company OCi.
In the first case it can create access errors interrupting the normal flow of
operations, while the latter should not.
To forbid the first case while allowing the second, we synchronize company_id,
but add a special case to ignore it if it set to False.
Note that PR#30997 should be used in case the name_get causes an error for
another reason that is deemed a legitimate use-case.
opw 1933862
Description of the issue/feature this PR addresses:
Current behavior before PR:
Desired behavior after PR is merged:
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr