Somehow in the migration to the new api, it was decided that the
acquirers would be browser as sudo only for token access. This caused
portal users to have a crash when trying to view their quotation since
some fields from acquirers are set the specific groups for security.
This commit reintroduces the old behaviour, which was to browse as
SUPERUSER in all cases for the rendering of the buttons.
`customer_email_data` can be undefined.
It must therefore be checked before testing
its length
e.g. use the /helpdesk command with an anonymous visitor
of the livechat
opw-690301
Change color #a24689 to #875A7B
Commit https://github.com/odoo/enterprise/commit/8ac1c19fac7615fecd51e670f798d13158a4e53c
changed the odoo interface violet by changing the main LESS variable
but forgot there was many direct occurences in XML/HTML/... (for
example for the mobile browser color).
Even if it's community the odoo interface violet is used at many places
(module description, XML demo data, ...).
A customer can confirm a quotation only once `website_quote` is
installed. Without it, this isn't possible, and by default
this is not installed with the installation of the `sale` module.
Courtesy of fgi@odoo.com.
Commit 48a1eaf792 adapt the welcome
message on website so that it fits the page height. But this does
only worked for large screens as the height was forced to main
height... which is smaller than the default welcome message height
on small screen. The fix only had to use min-height instead of height.
Commit 5f98040430 in saas-12 changed
some "saved" event to "save" event but forgot to adapt new features
which depend on this in 10.0 after forward port.
The blog_cover JS code is only available on blog pages. So the option
can only be activated on blog pages (which was not the case if the
snippet latest post was used on a random page).
Animation preview on images did not work as the web_editor stopped
every potential animation when an image entered edition. As the
behavior does not seem useful as there is no infinite animation which
is possible with standard odoo (and even if it was the case, it would
not be too strange that the animation continues), the feature is
removed with this commit.
Since commit 8ac1c19fac7615fecd51e670f798d13158a4e53c the odoo brand primary color
changed, which also changed the color of tips. The problem
was that they lose a lot of contrast in the appswitcher.
In saas-12 and up, upstream_dependencies returns:
- when called from old API : a list of ir.module.module ids
- when called from new API : a recordset of ir.module.module
From 9.0 to saas-11, when called from new API it would also returns a
list of ids which can bring needless inconsistencies.
With this commit when called from new API a recordset is returned.
opw-690015
Neither the super-user nor the sudo() mode should need
to use read_group() on any of the private user fields.
So we can simplify the code and remove this special case.
The same is not true for read(), though.
Also restrict XML data attribute evaluation context
even for real module data files. This will prevent
accidentally depending on context parameters that
would not be available inside base_import_module.
Move code related to redirection in its own class method. This way all
controllers perform their own actions and checks before calling the
redirection itself. Moreover it is necessary for some controllers to be
able to call the redirection independently outside of the mail/view
controller scope.
This commit also fixes some links generated for mail notification email
buttons. Assign and (un)follow buttons now effectively use the link helper
when generating the associated URL instead of manually crafting it.
Custom routes for notification buttons used in HR and CRM are added.
Indeed in order to be able to fine-tune the behavior called by those
buttons, using dedicated controllers is simpler than trying to use
a generic one. As there are few custom buttons in notification emails
using dedicated controllers does not lead to a code overhead.
Also restrict XML data attribute evaluation context
even for real module data files. This will prevent
accidentally depending on context parameters that
would not be available inside base_import_module.
Since the library nestedSortable was updated to the release 2.1a,
at the below revision:
https://github.com/odoo/odoo/commit/aa19d9edd02756d87056a44340e36568b3183e21
It was no longer possible, in the front-end, to move the menus:
Re-sequence them, put one below another, ...
Indeed, in that piece of code, `.item_id` was never
set with the new release, while it was the case with the former one.
We replace with `.id`, which looks like to have the same behavior.
As the finished move or the one after might automatically split into its components,
it is not a good idea to select a Phantom BoM for a production order, so
this is for the moment, the best way to avoid it.
It is good to have this check, otherwise
it risks taking whatever lot or creating
a piece without lot if you would by accident
say you did so many quantities but no lot was given.
Damien Bouvy