There was a mixup in the ogone response parameters that prevented error message to be stored successfully; this commit fixes that.
This commit only fix the s2s code in saas-6, the form payment code has been fixed in 8.0 and will be forward-ported (commit e7085a8bd7)
The commit 312b85e added a reloading of the chatter messages after
closing the mail composer. But e.g in Messaging > Inbox a simple reload
isn't enough. For now this commit restrict the reload to chatter logs
(e.g the chatter of a quotation).
related to PR #7596
1fb33a8 added pivot mode to the project.issue action (since it was split from
the graph view) but forgot to add it in the action called from project.project
kanban (act_project_project_2_project_issue_all).
In order to fix Python bug https://bugs.python.org/issue16041
a maximum line length was introduced in poplib when reading
email contents from the POP3 server.
That limit is set to prevent DoS attacks via malicious POP3
servers.
The default limit (2048) seems to be too low for emails
commonly found on the internet, retrieved via POP3 from
popular mail services such as GMail, Hotmail, etc.
(The POP3 servers might send back the lines verbatim
without splitting them up)
This is discussed in follow-up Python bug
https://bugs.python.org/issue23906.
Workaround implemented by forcing a higher default limit
to accomodate POP3 responses with lines up to 64KB.
When searching records with a many2one multi-path domain
e.g. [('employee_id.user_id', '=', uid)] on `hr.holidays`,
inactive records were ignored
e.g. if the employee of the leave request is disabled.
For instance, this was not possible to search
holidays of a disabled employee, while you would
want to see holidays of an employee who
is no longer working in the company.
This leads to a huge change of behavior,
and this is why we decided to not apply
this fix within a stable release, such
as 7.0 or 8.0, as companies in production
might rely on the current behavior for
their business, and changing this suddenly is
not accepted.
This must not be applied for one2many fields: Disabled
records of a one2many fields must be considered
as deleted. A search with a multi-path domain
on a one2many must exlude inactive records.
opw-644718
Once the document module installed,
It was mandatory for a user to have the
Knowledge User group in order
to edit/unlink an attachment, even
if this attachment wasn't using
the document directory feature
opw-644712
Fixes#7599
Comments in .po(t) files for translations of type "code" (e.g. field labels)
specify the path to the file containing the translation. This path should be
OS-independent to get the same result whatever the plateform the instance is
running on.
Closes#7561
4adb4b8d15
corrected the fact the quotation email
wasn't sent if you did not come back
from the payment provider
(when you closed your browser after
the payment but before coming back
to Odoo).
Before the above revision, the quotation
email was sent for payment methods
not redirecting to payment providers,
like transfers. It was no longer the case
with the above revision.
This revision re-introduces this behavior:
If there is a feedback from a transaction,
but the transaction isn't confirmed,
we send the quotation email without confirming
the sale order, like it was the case before
opw-644670
Always reload the message after the mail composer message is closed.
Since there is several unrelated model it would probably messy to go
from the mail thread to the mail composer popup to see if a new message
is posted (or get it and add it in the chatter like done in the simple
message editor).
With this change, anytime the mail composer modal is closed the mail
thread messages are reloaded.
closes#7596
opw-644406
Jeremy Kersten