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

This reverts commit 20e19fdf.

Already fixed by @fwi-odoo in 82b83ac7

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.

Previous implementation was not robust as css style was able to change
the image height.
Also refactore the method to be more efficient.

Fix an issue causing a wrong icon alignment on save.

* Remove the ability to change bg-color (colours are applied to
children elements)
* Fix a layout issue in theme_resto

* Trig default ".btn.btn-link" rather than custom ".o_mail_link" (not
used anymore)
* Define variations when a button is inside bg-beta or bg-delta

Remove the word "Table" so that the name fits in one line

- ability to edit copyrights (change year, etc.) without removing ©
- 2016 in copyrights, not 2014

* Rename it to "Promo Code"
* Several text changes
* Add a CTA

* Move social links out of tables so that they will not trigger at
td data-selectors
* Use o_mail_no_resize class to specify that the td container is not
resizable (otherwise oe_handles will overlap the icons)
* Adapt email templates

Refactore width-x snippet option and create another option to handle
cloning and removing td elements properly.

* on_focus: the handle to resize are now hidden when the td/th is alone
on its row

* on_clone: when cloning a td element which is alone on its row, it is
instead cloned in a new row. If not, empty td are added on the whole
column to maintain table integrity.

* on_remove: handle removing td in complex table

This key causes problems down the line (since account.asset.asset
have a type field as well) caused by context propagation.

The key is not required anyway, since out_invoice is the default
type.

website_portal_sale adds support for sale orders in the front-end. It is therefore
in that module that we have to set the buttons in notification emails. Not in
ecommerce app.

There is now a single method easier to inherit to add specific behavior
for the display of access button as well as actions buttons. All addons
using this mechanism are updated accordingly.

mail/view controller is a generic controller that redirects the user to a
given view, depending on the record and the user. Users may be redirected
to the backend form view, or to a website view. This is done notably by
calling get_access_action method that gives the action to perform (act_window
or url).

Previously this method was called using SUPERUSER. However it was therefore
impossible to know who the user was. This method is now called using the
current user. Various overrides of get_access_action have been updated to
add some logic and access rights check directly in the method allowing
more fine-grain behavior of the access action.

 * Assign controller now effectively redirects to mail/assign instead of
   mail/assign
 * Follow and Unfollow button now uses the helper that generated the link

If render_template get list and not id, a dict is returned.
Force the param to be a int, allow to don't use the multimode from render_template.

Avoid to get message like:
 <p>{1: u'\n        </p><p>Congratulation, you have received the badge <strong>Autobiographer</strong> !\n        </p>\n\n'}
 <p>{2: u'\n        </p><p>Congratulation, you have received the badge <strong>Autobiographer</strong> !\n        </p>\n\n'}
 <p>{3: u'\n        </p><p>Congratulation, you have received the badge <strong>Student</strong> !\n        </p>\n\n'}
 <p>{4: u'\n        </p><p>Congratulation, you have received the badge <strong>Supporter</strong> !\n        </p>\n\n'}

Fix 'Key error' dues to prematured access {key: post[key] for key in optional...
Replace street2 by company name

Registry.init_models now expect a list of model names instead of the
models themself.

Fix missing fields and inherited fields
in the commit 9f604239

There's no real difference between the 2 access rights

and use its id instead

 * Display alias options when editing the project email tab
 * Reorganize project details
 * Reoganize email details
 * Display options when creating project (timesheets, forecast, ...)