The focus() of AbstractFormField should return false if field
is not focusable otherwise it breaks FormView's#autofocus()
Also added checks of existance of the element to focus.
Those errors makes it harder to find other bugs
bzr revid: fme@openerp.com-20130321220636-1pja2ahsdstyl8kz
@include text-to-icon makes the text invisible (and adds an icon), but
some platform apparently don't apply the text's transparency (or
visibility) to its shadow, leading to the invisible text's shadow
still being noticeably visible (an interesting literary idea, an
"invisible" man who still casts a shadow?) as if the text had not been
erased. Furthermore, combined with the 1px font size it made the text
look like some sort of screen smudge or glitch.
Fix by erasing the text-shadow as well as the text.
lp bug: https://launchpad.net/bugs/1158304 fixed
bzr revid: xmo@openerp.com-20130321164741-iakau7g1kfq2mqu4
On click on a filter in the drawer, FilterGroup would just match the
offset of the filter in the group's DOM with an index in the internal
#filters array.
This worked until invisible fields, and then again only for filters
*preceded* by an invisible sibling in the same group: invisible
filters are not rendered in the DOM, so the indexes would get out of
sync.
Fix by using explicit indexes stored in a filter's @data-index and
using that to get the filter object/node.
An alternative fix (but hackier I think): instead of not rendering
invisible filters, render them with display: none. Remains an option
in the future if needed...
lp bug: https://launchpad.net/bugs/1157125 fixed
bzr revid: xmo@openerp.com-20130321155123-211iht7c6zme712e
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
dle@openerp.com