Payment transactions referenceis have a unique constraint which was problematic when a payment was cancelled from the acquirer's page.
To stick the to DRY principle, I factorized a method that checks for existing references and happens a numerical suffix if necessary.
This was already implemented in website_payment but was moved to payment and used in website_sale.
The message used in 'valid_inheritance' was not very helpful when the
inheritance validity was not passed.
You only knew that some view was not OK without knowing which one.
We now use the 'raise_view_error' method, which can already display all
the meaningful info (view_id, parent_id, view name, ...)
When a SO is linked to the analytic account: ensure the SO is validated and warn user if not
When there is no SO: simply register the line on the AA; registering expense lines on analytic accounts must not require the use of a sale order
Since the new translation process for views, their arch is translated upon
reading the views, before applying inheritance. Remove the useless translation
that was done after this process.
Enable the prefetching of several fields while evaluating an onchange. Special
care is taken to not prefetch computed fields or fields already in cache. The
latter is necessary to avoid "cleaning up" dirty fields by accident.
The translations inside the i18n/ folder are the translations published on
Transifex. It will contains the translatable "general" terms (menus, error
messages, actions...).
The account, taxes, journal names are made translatable thanks to the
l10n_multlang module but it should only be translated in the `spoken_languages`
values (nl_BE for l10n_be). These translations are present in i18n_extra folder
which is not published on Transifex.
Regenerate the translations correctly and populate the nl_BE.po file with
previous translations.
The hightlight element when a tip is clicked was placed over a white
rectangle. This induced a problem if the element was itself white.
Also the dimension of the helper were badly computed.
+ remove specific tip style in kanban view
Embedded the template core in a 'root widget tag' to make the selector 'this.$('.o_mail_chatter_compose_message_suggested_partners input:checked')' works.
When creating a document a message is posted (ex: 'document created') and the track field users are auto added as follower and notified with the last posted message (like the just create message). So the author was notify of the creation of its own document.
The problem did not appears using form view, beacause when the mail.message were reloaded, the thread was mark as read, so the partner (author/creator) was directly removed from the needaction_partner_ids field. The issue happen when loading the demo data, generating many needaction for the admin user (creator of most of the document).
This bugfix remove the current partner from the new follower to subscribe and to notify with the last posted message, as done when a message is posted (in _notify method of mail.message).
Damien Bouvy