Their changes are not propagated to other processes in a
multi-process setting.
It means that now calling these on auto=False webkit reports
will not have the desired effect. But really they can be updated
to use the new XML parser attribute, and the create/write/unlink
features should be on the base class, not in this module.
bzr revid: vmt@openerp.com-20130322152741-zdmwga2u7uqsv2c3
It was wrong: only the auto=True reports should have been registered
by that method to respect the framework behavior.
And those auto=True reports should not be registered anymore:
the framework will always look them up in the database.
bzr revid: vmt@openerp.com-20130322152356-n66b7igi68pv78ip
This is needed so the uninstall process can simply go through
the installed data by using the ir_model_data entries in reverse
order (when ordered by IDs), so that parents are deleted before
children.
bzr revid: vmt@openerp.com-20130321133202-igea1vxlszfpk6pe
The mailgateway tries to find a partner that is also an user with the email_from.
If none is found, it takes the first partner with matching email.
In message_post, it tries to find the author based on the document's followers.
Indeed it is very likely that an answer comes from a follower of a document.
The whole process is not done inside the mailgateway because document
and followers related stuff belong to message_post, not to the mail gateway.
Tests have been added in mail.
bzr revid: tde@openerp.com-20130321120451-qk524qayq28sw3th
A new module is added that make a bridge between Portal and Project Long Term.
It adds access rights and security rules allowing use project long term
along with portal.
bzr revid: tde@openerp.com-20130321090626-zw4kpuszit4q5q9s
Due to the way cron jobs are executed in multi-process
environments, the cron arbiter holds an exclusive lock
on the cron task row in the database.
During the course of the subscription cron jobs execution
they attempt to alter a record that has a FK towards
the cron task row, effectively deadlocking the whole
cron processing thread.
The fix is rather hackish: remove the explicit FK
constraint from the subscription model towards
ir.cron - this prevent PostgreSQL from requesting
an exclusive lock and triggering a deadlock.
This is only a temporary solution, the subscription
module should be rewritten for the next stable release.
bzr revid: odo@openerp.com-20130320153430-bho6ou8b7ziohcb0
[FIX] mail_followers: notification emails did not have 'references' correctly filled with their parent message message_id,
[FIX] mail_mail: emails sent to partners now use the 'Name <email>' format for email_to, instead of just 'email'
[FIX] mail_compose_message: fixed mass_mail subscribing the author to all documents,
[FIX] mail_compose_message: fixed access rule on mail_compose_message not taking into account the wizard creation in mass_mail_mode (model but no res_id -> could lead to crash),
[TEST] mail: cleaned a bit the tests; mail gateways related tests are now in a dedicated file; tests were added that helped triggering the previous errors
bzr revid: tde@openerp.com-20130320145225-1hhp383wt507p3q3
- the re-raising of exceptions ignored the "legal" exceptions
(the one used to early abort RPC calls and generate pop-ups)
- re-raising the exception was attempting to re-use the original
exception type but it does not always take only one argument
so it was breaking.
lp bug: https://launchpad.net/bugs/1146256 fixed
bzr revid: vmt@openerp.com-20130320132238-qzo3jptww59ndlch
Vo Minh Thu