In some cases (for example, some popup dialogs with a form view), the
one2many field is destroyed but the async code still tries to append
a view manager to itself. The result is that the start method of the
view manager is run, resulting in at least an useless fieldviewget.
calendar : When you create an event (for example from a job interview), you should be set as an attendee.
crm : Lead/opportunity : Bounce should be read only
hr_recruitment : 'Create Employee' should be an action button, instead of a link in the form
website_sale : SO report typo invoicing address instead of invoice address
website : remove Unpublish on the dropdown
website_sale : if accessory product is a non published product : do not show it on the ecommerce (avoid 403 error)
- remove unnecessary copy() method from project/res_partner.py
- remove old methods on project.project
- progress is not used anymore on project.project
- use clickable statusbar for project states
- remove _resolve_project_id_from_context
- rename project.category becomes project.tag to be more explicit
- remove old methods on tasks
- issues: remove option fetchmail_issue
Cache for browse record are not optimal, should be id.
Don't need to cache the partner according to chs, browse will cached itself.
Be sure to restore previous sale order only if the sale order are always
in draft mode, else checkout will force redirect to /shop anyway.
The controller /shop[/category][/page] can now take a parameter in get ppg (eg: ?ppg=10)
to change the number of product displayed by page.
Should be a parameter in a table key/value like ir_config_parameter but nobody want to do it.
Now we display the price_reduce from the sale order line
and not the unit price.
If a discount has been added to the quotation, the user had
in the front end not the real price for the line, but the
discounted total which one is the total of the sale order.
So we need to display the final unit price (= reduce_price) to
be consistent with the total price displayed.
Pricelist has been already applied in the sale order, so not needed.
If we refresh with the price computed by pricelist (gup), in
the case of a discount setted on the quotation order, the gup price
will override the real price from sale order by a price.
to message_add_suggested_recipient; signature has been updated when migrating to the
new API, removing an argument that is now contained in self. However all addons were
not updated accordingly.
- bank statement import: misplaced parenthesis
- payment: show the 'Post' button no matter the payment method
- payment: fixed some attrs in payment form view
Géry Debongnie