Without hidding view.$container, when coming back to Kanban or List
views, it was no more possible to click anywhere on those views.
Fixes the bug introduced by rev c465605049
Use uuid4 instead of uuid1 to get 128 bits of entropy.
Rename database.uuid.private to the more meaningful database.secret as it
explains the usage instead of the technical details to generate it. And we
might switch to a longer string with more entropy in the future.
This string can be used to sign cookies or token with
sign(src) -> (src, hash(src + secret))
check(msg) -> msg[1] == hash(msg[0] + secret)
The sidebar in view pivot was not hidden when switching from view pivot
to another view. Thus, the sidebar content of view pivot was still in a
dropdown of the sidebar of the new view (when this new view has a
sidebar as well).
Also changed the way of switching between views: we now first hide the
current view before creating and displaying the new one. This prevents
weird rendering in the header as well.
Moreover, the task of hidding/showing the view's buttons is left to the
view instead of the ViewManager.
User drops something on the keyboard > Inputs very large number unnoticed
> Bad things happen.
- Limit input lengths to 12
- Ring bell when exceeding that length
- Warn if the amount makes dubious business sense
- Block screen inputs when popup is active.
- Asserts to prevent edition of the order after validation. Just
in case.
Review kanban to have only create by default without the search view
Rename model leads_dry_run into crm_leads_dry_run
Fix bug when toggle the running field on kanban was done before save
Remove useless link Assign now and Dry Run
Add dry run action_server in team.user more context
Adapt rev 4a3e5df93a and rev e1cde4d038 to the current webclient
structure. Without this patch, autocomplete widget is completely broken
with multiple viewmanager.
For companies not working with variants,
it is important to be able to search in the
Products menu (product.template) using
product codes.
It is useful as well to see the codes
in the default kanban view too, even if
it is only the code of the first variant.
When a stale XML ID exists in the database, `_update_dummy()`
must consider it as missing entirely, and the next call
to `_update()` will take care of cleaning up the old XML ID.
Failing to do so for `noupdate` records means the `_update`
will never happen, and as soon as another record is created
or updated with a relationship to that stale XML ID, it will
plainly crash the installation/update.
Takes care of resetting it from older versions
e.g. rev d97e7a6a4e
and c0076916f3, as
the old `variants` field that was used does not
exist anymore, crashing at opening.
Aaron Bohy