There was no bug but now the behaviors are more consistent :
- Demo data now declare a black invisible filter instead of nothing.
This allows user to see the effect of filter intensity option
(otherwise it had no visible effect since there was no filter color).
- If the filter intensity is set to "None" (invisible filter) and that
a filter color option is highlighted or chosen, a "Low" filter
intensity is automatically highlighted or chosen so that the user see
the filter color he is chosing (instead of having to choose the filter
intensity first).
- Hide the "Size" option on the blog list page since it has not visible
effect there.
- Some code "performance" improvements in option selection.
rounding field of product_uom now has sql constraint > 0. If set at 0 it rounds
any quantity to 0, which is never a desired result.
Allowing 0 made it so that some users that did not understand the rounding, set
it to 0 and complained that their quantities were messed up.
Also added translations to the error message.
This fix renames filters in purchase from Invoiced (resp. Not Invoiced)
to Received Bills (resp. Waiting Bills) to be consistent with the states
of the Purchase Orders (i.e. 'Waiting Bills'). The erroneous tooltip of
the Bills Received was also corrected.
In procurement form view display a Purchases stat button that redirects to
the purchase order. It opens the PO form view. Note that Purchase Order field
in Extra Information is left untouched. It is just a shortcut to ease
usability.
It is already defined as a payment method (subtype=inbound) and that's what we want. No need of adding 'electronic' in 'payment_type' selection (that crashes if we select that, btw) and 'payment_method_id_code' is a duplicate of 'payment_method_code'.
'Project > Reports' menu show 'Tasks Analysis'. But
if you install project_issue, or rating_project, some
children menus are added, making 'Tasks Analysis'
invisible.
Trying here to set the same order for issues, ratings,
forecast as in other menus, labels and kanban card.
That bug was introduced when removing the invoice workflow, where a call to action_invoice_cancel() has been used instead of action_invoice_reopen() which does slightly different things, as you can imagine.
This fix prevents from giving the reason of the refund to the draft invoice created if you select the 'modify' option when refunding an invoice, which now keeps the description of the original invoice.
Commit 3c98c78fc7 added the feature to be proposed redirection
after a click on a menu link in edit mode. This however applied to main
direct link in the menu and not sub-ones in sub-dropdowns. This commit
fixes this.
As the <strong/> tag which surrounds the "Use this tag" sentence also
contained a <a/> whose href is a computed one (t-att-href), the strong
was not able to be edited.
Because 0% taxes will appear in the account.invoice.tax object of the invoice and the account, if null, will be the expense one which is confusing.
Because 44000 is use as everyone as payable account, so removed duplicated 'Fournisseur' account
Adding the attributes leave all the old variants available.
While not completely intuitive, this behaviour is not inherently
wrong. However, on the first attribute addition, it leaves a variant
with 0 attributes that can cause problems in the ecommerce. This commit
make it so that this empty variant is archived.
This allows people to create modules under the 'Odoo Proprietary
License' version 1.0 rather than having to rely on the rather vague
'Other Priorietary' license.
The text of the license can be found at:
https://www.odoo.com/loempia/static/examples/LICENSE
This should already have been in Odoo 9 but was mistakenly left out.
* mail/view controller does not call get_access_action and other methods as
superuser. This allows to customize the returned action
* reimplement methods to generate recipients groups when sending notification
emails. It is now simpler to inherit and customize
* update various addons using it
The content to translate is yellow and the translated content is green
in page translation mode. When the user starts translating a paragraph
it stayed yellow, making it difficult to see the remaining content to
translate when translating a big page.
This commit colors the dirty text in a paler green so that the user can
see the distinction.
The default image inside undropped snippet had to be switched everytime
a theme is selected, even on first theme choice as the switch_theme
method only switch images of snippet already dropped in the page.
qsm-odoo