Fixing calendar view errors, opw 609989

Also fixes some weird inheritance bugs in upper versions

At rev 84e9a67c a check to avoid the creation of ir.model.relation for custom modules was added. The condition is not correct as based on the string instead of the field name. We do not have access to column name at this level but the the m2m relation table do start with x_ for custom fields (see __init__ method).

[FIX] mail: misc bug fixing
- avoid deleting the Whole Company mail group if still present, because it is required for some module installation. In 7.0 installing some modules may crash if this group is not present.
- fixed an issue when computing possible recipients in the Chatter
- small fix in html2plaintext about blank lines

There's a big risk of mistake with the fast-create
feature and they don't need it

(Rebase of PR #1073)

(Partial backport of commit 1f861569)

Closes #800.

orm: do not try to create ir.model.relation for custom m2m as self._module is either empty (for custom models), either the one of the last inheriting module (which is wrong). The field should be removed manually and should not be impacted by the uninstallation of modules. The removal of the relation table can be done when removing manually the custom field (see rev 6af3193d).

ir.model: when removing a model, drop the table with the CASCADE instruction. This will remove left constraints from remaining m2m tables.
This means that dropping a table (either manually removing a custom model or uninstalling a module) will not drop the relation table for a custom m2m field. This is not ideal but better than the previous behaviour (which was to fail the DROP TABLE instruction and keep the table with a few columns and unconsistent data).

When droping a column, remove also the relation table in case of custom m2m field.
The relation table needs to be dropped otherwise an unremovable constraint to the targetted table is kept (and anyway is not needed anymore).

skip the inactivate employee in leaves summary

lp bug: https://launchpad.net/bugs/940439 fixed

bzr revid: fme@openerp.com-20140508075025-yszqmzie1z4n7l4j

When the cron for autovacuum runs, the osv_memory objects are deleted. The portal.wizard.user object has a required field (wizard_id) linked to another osv_memory object (portal.user) which causes a traceback when the cron tries to delete portal.user object before the portal.wizard.user. opw 609918

Add context to search method

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