Currently, the menu are only translated for installed language when we
create a new website.

When we create a new menu (eg. by installing a module) or install a new
language we will only translate menu without website_id set, so the menu
are not translated.

With this changeset, we try to match translation of menu without
website_id to menu with website_id when translations are updated:

- when a language is installed/updated
- when a module is installed/updated

Without the changeset, the added test would fail with:

- "Menu in english" != "Menu en français"
  Load translation add missing translation from template menu

- "Menu in french" != "Menu en français"
  Load translation with overwriting update existing menu from template

fixes #43365
opw-2209864
closes #48031

closes odoo/odoo#50498

X-original-commit: 998987f8ee148235f4025eb97a424e838ac6fc9f
Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com>
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>

When computing the `arch` from the arch_db, the field gets translated
as a matter of course as `arch_db` is a stored field with a
translation method. This means `arch` is assumed to be in the proper
language in the cache.

However when reading from the filesystem (dev=xml) this is not the
case, and the view XML ends up untranslated.

Fix the issue by applying the translation function from arch_db onto
the stuff we got from the filesystem.

Note: under the assumption that we *do not* want to store translated
archs in arch_db, explicitly set the lang to None when resetting
views.

Task 2059557

closes odoo/odoo#50389

Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>

Some apps, once installed, automatically create a menuitem in website.
What complexify the UI and create useless menu withtout plusvalue.

It is not because you install livechat to make support online, that you want
a link in your menu to show stats e.g.

Now we remove the default menu created, and help user to find it when he create
a link. The autocomplete suggest most of the main App's controllers

task-2189613

closes odoo/odoo#49081

Related: odoo/enterprise#9733
Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>

Remove the default about us page because it could be easily recreated and
doesn't add a lot of value to the website.

task-2189613

Cache should be invalidated when updating `arch_db` via `arch`.

closes odoo/odoo#50512

X-original-commit: 1a14ca163ee256eb26661c900227db49426ec3af
Signed-off-by: Raphael Collet (rco) <rco@openerp.com>

X-original-commit: 7460d65387edd9d8578e048da6ee634ef6a2e71e
Co-authored-by: Christophe Simonis <chs@odoo.com>

There is no way to select all the posted invoices; only the posted and
unpaid.

closes odoo/odoo#50509

X-original-commit: abd53fa8b3e7787b4d3c0ab02e29656f85bfe4a3
Signed-off-by: Quentin De Paoli (qdp) <qdp@openerp.com>
Signed-off-by: wan <william-andre@users.noreply.github.com>

Task-2241443

closes odoo/odoo#50502

X-original-commit: afa2153a
Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>

When no valid phone number was found on a record, and when using _message_sms
directly, no SMS and no notification was created. You could therefore think
everything was ok while it was actually not.

Instead we now create failed notifications. It allows to be notified of it
and fix numbers through cancel / resend wizards.

Task ID 2244192

closes odoo/odoo#50486

X-original-commit: baecdfaa2d31714a20d1fb8af7799af1805cd939
Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>

When no valid phone number was found on a record, and when using the composer
in single recipient mode, you had a crash at sending as composer tried to
write on a field called False.

Instead we just take the first available phone field of the record. As they
are all void we can update them safely.

Task ID 2244192

X-original-commit: 2306d7d79d8e64597912f15365cede7473589731

Task 2222062
The currency could not be on the same line as the amount

closes odoo/odoo#50500

X-original-commit: f75b708f
Signed-off-by: Laurent Smet <smetl@users.noreply.github.com>
Signed-off-by: wan <william-andre@users.noreply.github.com>

In a calendar with 2 weeks mode (odd and even), before this commit, all
new created periods (placed in one of the two sections) don't have the
week_type field set. This generates a confusion, because a period that
should be applied only in odd weeks, for instance, it was applied also
in the even weeks.

Now, the new periods will have the week_type field set with the
week_type of the section where is it. Also, an error message is raised
if a period is not in one of the two sections.

opw-2239966

closes odoo/odoo#50478

X-original-commit: 33a62118
Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com>
Signed-off-by: Jorge Pinna Puissant (jpp) <jpp@odoo.com>

closes odoo/odoo#50269

Task: 2221224
Signed-off-by: Josse Colpaert <jco@openerp.com>

This commit attempts to add the option to order partner levels by sequence.

In this commit, the following changes have been made :

1- Add a handle widget to the sequence field to reorder partner levels (in view_partner_grade_tree).
2- Update default order field in "res.partner.grade" to order records by sequance.
3- Update partners order in 'website_crm_partner_assign' controller to keep the same order in website.

Task ID 2241632

closes odoo/odoo#49882

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>

Revision on 7ecae335

Commit above introduced activity widget on partner kanban, but
unintentionally affected style of all other kanban views that have
details on kanban record.

This commit fixes the issue by applying special CSS rule only on
partner kanban view, so that other kanban views remain unaffected.

Task-Id 2237638

closes odoo/odoo#50474

X-original-commit: b0ef12bc0bcdb29ffc7e61f1a1a185248650283c
Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>
Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>

This reverts commit 715ef9fc2684dc875cf82ee312f20575ed42f94d.

Purpose of commit above was to fix an issue in kanban view
CSS introduced by 7ecae335

This commit, however broke more kanban views. This happened
because the original commit changed a CSS rule with flex, and
commit above attempted to fix the issue by turning problematic
UI elements to their flex equivalence.

This change is too broad and unsafe, so the better decision is
to revert them.

Task-Id 2237638

X-original-commit: 6badf3839147c0b9a475247699227ed304bd402d

The attribute defined isn't the right one, thus on population,
those models are populated with the default _populate_sizes defined in base.

closes odoo/odoo#50464

X-original-commit: ad7436bb9d2b965f926aa2d1f45a89ea5f6dfc9f
Signed-off-by: Christophe Monniez (moc) <moc@odoo.com>
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>

closes odoo/odoo#50462

X-original-commit: 9040ed92
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>

This reverts commit cc8994a4.

opw-2153840

closes odoo/odoo#50280

closes odoo/odoo#50442

Related: odoo/enterprise#10239
Related: odoo/enterprise#10306
X-original-commit: 43fa375681f4615c0ecc28da625c0a488b38ba0f
Signed-off-by: Nicolas Martinelli (nim) <nim@odoo.com>

- Create a consumable product
- Assign a FIFO product category, automated valuation
- Purchase some units
- Go to the Inventory Valuation report

The product appears in the list, while consumable should not.

We only show products linked to stockable products.

opw-2153840

X-original-commit: 8fa2440e8c055ca80bce27e33d5678745712fe53

- In Website > Settings, set 'Show inventory on website and prevent
  sales if not enough stock'
- Create a consumable product P, publish on the eCommerce
- As user 1, buy 1 units of P => validate the SO => 1 unit is reserved
- As user 2, add 1 unit of P to the cart. In the cart click on the `+`
  to add a unit

The product is removed from the cart.

This happens because `virtual_available` quantity is taken into account,
while it shouldn't be since it is a consumable.

opw-2245075

closes odoo/odoo#50437

X-original-commit: ec6f281f
Signed-off-by: Nicolas Martinelli (nim) <nim@odoo.com>

This commit will clean the code by removing the field
'color' from model 'event.event' since the field is
not used/needed anymore.

Task ID 2243918

closes odoo/odoo#50155

Related: odoo/upgrade#1124
Related: odoo/enterprise#10199
Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>

Purpose of this commit is to allow customization of view types available when
using the activity menu. By default only kanban, list and form are available
as before.

Calendar, pivot, graph and activity have been added for leads, allowing
better user experience in their use of activities.

Task ID: 2228451
Community PR odoo/odoo#50042
Enterprise PR odoo/enterprise#10145

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>

- Move code from kanban view that is common with list view in common files
- Add action to add selected products to cart
- Add/update tests

closes odoo/odoo#47556

Taskid: 2160048
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>

When an expense is create from email, if the product is not set, when you want set the product it is erase the unit price.

closes odoo/odoo#50397

X-original-commit: 74736914
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>

Following the new populate functionality (populating the database with generated records),
this PR aims to improve:

* the creation of users (missed batching opportunity)
* the update of partners (optimized write to potentially reduce database requests).

Followup of #48912
Task Id - 2229358

closes odoo/odoo#50452

Forward-port-of: odoo/odoo#50367
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>

ref() always trigger a database query to verify record still exists.

In frequently used methods, it's best to avoid ref calls if not needed:

* either the records should always exist
* either the record isn't always needed and the ref can be sometimes
avoided.

X-original-commit: c1e05da7b71c8274aff00d67f8d1bc7e209fcaab

When note is installed, res.users are created one by one because its
create override isn't adapted to work in batched.

This commit ensures the create override is adapted to ensure users are
still created in batch when note is installed.

X-original-commit: 1cf7e1ac5dbf174e756a01f9b75abd09b168e52a

Do not loop through the partners, doing the same stuff n times, and
potentially doing multiple searches when one is enough.

X-original-commit: 35713d2ff46dcfc4a578c41dad6f786919754ca2

[FIX] l10n_nl: fix bad forward-port of https://github.com/odoo/enterprise/commit/82608e25033fde6f93b8d0face5774f70930fcd2



closes odoo/odoo#50447

X-original-commit: 4556c0409d7022a2186dcb95307c5a57577d5081
Signed-off-by: Laurent Smet <smetl@users.noreply.github.com>

Inspired by what is done in the task kanban of the project module,
add examples of kanban stage setups for UTM campaigns, and allow users
to load them.

There have also been some minor changes to the campaigns view:

- The helper message when there are no UTM campaigns has been changed
  to a more descriptive message.
- All stages that existed by default (hardcoded in the data XML) have
  been removed except default New one. An user with a fresh database will
  have no stages in their kanban. The old hardcoded stages have been moved
  to the demo data instead, so they will still be added by default if the
  user installs demo data.
- The ghost columns that appear in the kanban when no stages exist have
  been renamed to match the old stages that were hardcoded.
- When the user opens the view to create a column, the 'See examples'
  link will appear below the 'Column title', just like in the project
  addon, and clicking it will open some examples specifically made for UTM
  campaigns. Clicking on the 'Use This For My Kanban' button will load the
  stages of the selected example.
- A min-height property has been given to the example modal view so that
  the view does not change size depending on the number of rows in the
  ghost columns.

Sub commits are present to allow tweaking the feature more that currently
feasible.

Task ID: 2047369
PR #48299

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>

Before this commit, after adding a column or loading examples in a
kanban from the quick create column, it stays open. After this commit,
it will stay open if adding a column through it, but it will fold if the
user has loaded a set of columns from an example.

Task ID 2047369
PR #48299

Inspired by what is done in the task kanban of the project module,
add examples of kanban stage setups for UTM campaigns, and allow users
to load them.

There have also been some minor changes to the campaigns view:

- The helper message when there are no UTM campaigns has been changed
  to a more descriptive message.
- All stages that existed by default (hardcoded in the data XML) have
  been removed except default New one. An user with a fresh database will
  have no stages in their kanban. The old hardcoded stages have been moved
  to the demo data instead, so they will still be added by default if the
  user installs demo data.
- The ghost columns that appear in the kanban when no stages exist have
  been renamed to match the old stages that were hardcoded.
- When the user opens the view to create a column, the 'See examples'
  link will appear below the 'Column title', just like in the project
  addon, and clicking it will open some examples specifically made for UTM
  campaigns. Clicking on the 'Use This For My Kanban' button will load the
  stages of the selected example.
- A min-height property has been given to the example modal view so that
  the view does not change size depending on the number of rows in the
  ghost columns.

Task ID: 2047369
PR #48299

Before this commit, the only module that allows for selecting and
applying kanban column examples is the project module, for its tasks
kanban, so the message in the button to apply the example is hardcoded
as "Use This For My Project".

After this commit, the text in this button can be customized to make
this more generic, so a different module could use a different message
like "Use This For My Campaigns". If no text is specified, a generic
"Use This For My Kanban" is used instead.

Usage

```
kanbanExamplesRegistry.add('utm_campaign', {
    applyExamplesText: _lt("Use This For My Campaigns"),
```

Task ID: 2047369
PR #48299

Before this commit, when a user creates a private channel without adding himself
as a member of it, it raises an access error. After this commit, user will be
automatically added as a member by default when creating a channel.

It makes sense the creator is a member of its channel. Moreover it avoids
issues on private channels.

Task 2172420
PR odoo/odoo#44454

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>

After this commit, out_of_office_date_end will always be set for consistency
even in create mode with default partners.

Task 2172420
PR odoo/odoo#44454

The color picker help the user to choose a color instead of picking it
by id.

The title and arial-label "no-color" default value are removed from the
picker_preview because they are not accurate. Instead name of currently set
color is used.

Task ID 2128166

closes odoo/odoo#47474

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>

Currently, when the unit amount of line is zero and the timer time
spent on entry is less than one minutes then entries are unlinked
once the timer is stopped and due to that the entry disappear from the
kanban view and traceback is generated.

After this commit, we fix the issue by preventing the deletion of
entries by setting options 'prevent_deletion' on widget so we should
no allow to delete the entry if the option is set on widget.

closes odoo/odoo#50395

Taskid: 2230155
Closes: #49128
X-original-commit: 64b9a9b4deaee5a8139b0afbe3f222a476a038f9
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>

Before this commit, the Title for the `"Page Published"` was `visible` and `Not visible`.

With this commitment, we make it align with the main title.

closes odoo/odoo#50344

Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>

Steps to reproduce:
- install eLearning
- go to the website > courses > enroll in any course > leave the course

Previous behavior:
you are not unsubscribed from the slide channel and still receive mail
notifications

Current behavior:
you are unsubscribed from the channel when you leave the course

opw-2244716

closes odoo/odoo#50404

X-original-commit: cb262738
Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com>
Signed-off-by: mightyjol <jhk-odoo@users.noreply.github.com>