Mixes the mass_mailing_id and mass_mailing_campaign_id
between the two models. Introduced by 9fc4ad99, PR #472

This instance was not actually exploitable for
SQL injection as it is not callable directly
via RPC and guarded by other queries when indirectly
called. Still plain awful.

This instance was not actually exploitable for
SQL injection as it is not callable directly
via RPC and guarded by other queries when indirectly
called. Still plain awful.

The installation of a multilang localisation (e.g. Belgium) used to install as well account_accountant (and then account_voucher) for no technical reason and was considered as the full accounting package.

[IMP] website_crm - cherry pick from 29ad0216...

[IMP] website_crm - cherry pick from 29ad0216 - Improve contact_us to fill in all fields from the model crm_lead posted in the form except a blacklist of fields.

Correctly take the 'use parent address' into account in the onchange. Slightly updated the view that was weird with this parameter. opw 609344

When tag <drawString> is misused in an RML report, logs a more explicit
error

Empty URLs for OAuth providers do not crash anymore the login screen

When setting a worklog on a project_issue, the field to_invoice is prefilled with on_change_account_id based on the contract settings. As the field was not present on the list view, the information was lost and every worklog was not written as invoiceable, even if enabled on the contract. opw 609082.

Commit b6a7402f (reverted at f8671cb4) was almost correct, the PageReset should be added at the end of each stories but only if we have one more stories.
The PageReset will force the page count to be reseted at zero which means that last page of report would have been at zero.

[FIX] mass mailing: performance issue on stats #469: use SQL to compute mailing / campaign statistics on mail mail statistics model.

Fix wrong relative import of hr_payroll

In case of invalid format such as 'name email@server' (missing chevrons), the parsing would be failing due to a strict behaviour of getaddresses (returns nameemail@server).
With the patch this format is accepted.
opw 607312

Displaying the pagert in view group does not make sense as it's not updated when changing filter and every group (even if more than 80) is displayed in view group

This happens when you do a plain signup, you
end up as neither an employee nor a portal user,
but should still now when you are logged in.

The website module normally tries to render user-friendly
error pages for any error occurring during the processing
of a website-enabled request.
This happens even for werkzeug's HTTPExceptions that have
their own response, because we want the website layout to
be applied on top of the error page.

One special sort of HTTPException should be preserved
without rewriting: the manually-crafted ones generated
with abort(), and usually wrapping a redirect response,
which bears no alteration.

The switch mode event was triggered even if the view was not actually switched
This leaded to inconsistencies, like adding the view in the breadcrumb history, while the switch did not happen

[FIX] loading: overwrite translation on module update if option --i18n-overwrite is set

When creating hr.analytic.timesheet do not filter the list of fields to accept but set the list of fields to remove.

On database drop or rename, close the existing sql connections

[fIX] l10n_be_coda : do not try to create res.partner.bank without partner_id (required field)

l10n_be_coda : do not try to create res.partner.bank when set no partner in an account.bank.statement.line

[IMP] l10n_fr_hr_payroll: make sure the date format of Fiche de paie report is in french

report_sxw: make sure we have a fallback on en_US if trying to load an format in unknown language

l10n_be_coda : do not try to create res.partner.bank when set no partner in an account.bank.statement.line

This gives JSONRequests a chance to return
a proper JSON-RPC result when an HTTPException
is raised downstream, instead of returning a
plain HTML 404 error.

[FIX] _handle_exception() logic amongst requests and ir_http objects

Changes in website's ir_http#_handle_exception():
* exception is mandatory, can't be None anymore
* we don't touch non website_enabled requests
* we don't touch explicits plain responses from parent
* logic flow is now easier to read (I hope so)
* check for openerp's AccessError and convert to 403 errors

Change in website's ir_http#_dispatch():
* In case of real 404, instead of returning self._handle_exception(), just let parent do the job (so we call super())