The “Authentication via LDAP” module is not available on Transifex for
Odoo 16+ projects. This commit adds it to the list of translatable
resources by referencing it in .tx/config.

closes odoo/odoo#128431

Signed-off-by: Louis Wicket (wil) <wil@odoo.com>

Before this commit, a crash occurred when the user changed after
starting a livechat conversation.

Steps to reproduce (login => logout)
- Login on admin
- Go to the website
- Start a livechat conversation
- Logout
- Start typing on the chat window composer
- Crash due to `NotFound` raised after `notify_typing`

The same error could occur the other way around (logout => login).
This error is due to the user not being a channel member after it
changed.

In order to fix this issue, livechat session is cleared when the
user changes. Indeed, it the "new" user is not linked to the livechat
conversation so it makes no sense to display it.

fixes https://github.com/odoo/odoo/issues/128206


opw-3421386

closes odoo/odoo#128301

Signed-off-by: Matthieu Stockbauer (tsm) <tsm@odoo.com>

Steps to reproduce
==================
- Create and confirm MO with BOM1
- Consume the theoretical qty of your MO
- Update the BOM1
- Click on the `Produce All` button
- You will receive a message that the consumed quantity does not match the quantity
  of the BOM1 anymore
- When clicking on the set quantities and validate button, the consume
  quantities are not the ones that are previewed in the flexible consumption message,
  but the initial MO quantities.

So in this commit, we updated the `To Consume` quantities as per the flexible
consumption wizard.

task - 3323154

closes odoo/odoo#121602

Signed-off-by: William Henrotin (whe) <whe@odoo.com>

Current behaviour:
If you disable the recurrence for 1 task in a suite of recurrence,
if you had other tasks belonging to the same recurrence suite, they
would still be with recurrence activated.

Expected behaviour:
It doesn't make sense for some of the tasks in a suite of tasks in a
recurrence to enabled and others disabled. If we disable the
recurrence on 1 such tasks, all tasks should linked to that
recurrence should be set as non-recurrent, regardless if the
edit-mode is set on "This task".

Steps to reproduce:
- For 14.0 -> saas-16.1:
  - Install Project, Studio
  - Turn on in Settings the "Recurrent Tasks"
  - Create a new project and a task in it
  - With studio, in debug mode, add a related field to the task form
    that relates to `next_recurrence_date`. Make sure it's not "read
    only"
  - On the task, turn on the recurrence, set the frequency to each
    day, set the `next_recurrence_date` as a day in the past
  - Run the Scheduled Action "Project : Create Recurring Tasks"
  - On one of the task, disable the recurrence
  - Go to the other task, see that their recurrence is still active,
    and the frequency changed to the defaults values of once a week.
- For saas-16.2 -> master:
  - Install Project
  - Turn on in Settings the "Recurrent Tasks"
  - Create a new project and a task in it
  - Activate the recurrence on the task, set a planned date in the past
  - Set the task as "Done", this should create an new instance of the
    recurrence.
  - Disable the recurrence option in one of the task, observe that
    is doesn't change for the other task, and the recurrence
    frequency is reset to default values.

Reason for the problem:
When disabling the recurrence on 1 task, with the edit-mode set as
"This task", the recurrence is being deleted, but we don't disable
the recurrence of the other tasks linked to that recurrence.

Fix:
When we are writing `False` on `recurring_task` on a task, we
explicitely write `False` on `recurring_task` on all tasks that belong
to the recurrence after the deletion of the recurrence itself.

Affected versions:
- 14.0
- 15.0
- saas-15.2
- 16.0
- saas-16.1
- saas-16.2
- saas-16.3
- master

opw-3265212

closes odoo/odoo#128389

X-original-commit: cbca63d7
Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>
Signed-off-by: Piryns Victor (pivi) <pivi@odoo.com>

In the new version of the iot we import a new "crypt" library which is not available for windows

Addition of the class in the input of the password

closes odoo/odoo#128318

Signed-off-by: Quentin Lejeune (qle) <qle@odoo.com>

If applied, this commit will solve the issue of the list view selection when
the record is not actually created but it can be selected and can able to
perform the action.

Steps to produce:
- Open Accounting > Configurations > Chart of Accounts.
- Click on the 'New' button.
- Select the new line which has been added.
- Perform the 'Duplicate' action for that record.

This commit will fix the generic issue by preventing the record selection while
the record is in 'Edit' mode.

sentry - 4191036697

closes odoo/odoo#121792

Signed-off-by: Mathieu Duckerts-Antoine (dam) <dam@odoo.com>

QR code extraction fails in some cases when we try to get the Base64 content
from the Saudi EDI attachment when the datas is too voluminous. To avoid this, we pass
bin_size=False in the context to always get the attachment datas correctly.

closes odoo/odoo#128315

Signed-off-by: Josse Colpaert <jco@odoo.com>

Sometimes, when the base64 data used to render the QR code is too long,
some of the special characters included might be wrongly encoded in the
url passed to the /report/barcode route. To avoid this, we format the QR
code string through the quote_plus method to make sure it's always
properly encoded

Part-of: odoo/odoo#128315

closes odoo/odoo#125585

Signed-off-by: William Henrotin (whe) <whe@odoo.com>

When user adds rule in the 'Default GS1 Nomenclature' that contains
'Unit product' in Type and 'Date' in GS1 Content Type.

Steps to reproduce the issue:
- Go to Inventory > Configuration > Settings > Barcode
  > Select 'Default GS1 Nomenclature' in Barcode Nomenclature
- Go to Inventory > Configuration > Barcode Nomenclatures
  > Open Default GS1 Nomenclature > Add a line > Select 'Unit Product' in Type
  > Select 'Date' in GS1 Content Type > Add Barcode Pattern for Date
    (ex. '(20)(\d{6})' )
- Go to Barcode > Inventory Adjustment > Click on Add Product
  > In product, add value for that Barcode Pattern (ex. 20230614)

Error: A traceback appears: 'TypeError: expected string or bytes-like object'

When user add barcode of date for product
https://github.com/odoo/odoo/blob/ae94f14a844352f66490ec326fe2d1a716023891/addons/barcodes_gs1_nomenclature/models/barcode_nomenclature.py#LL156C25-L156C63


Here we will receive datetime.date datatype for value.
Now when it tries to match re with datetime.date, it will lead to the
above traceback.

sentry-4236166678

closes odoo/odoo#124958

Signed-off-by: William Henrotin (whe) <whe@odoo.com>

Before this commit:

When format styles were applied to the word table, it would break table.

After this commit:

Now, when format styles are applied to a word table, the style will be applied to it
without breaking the table.

task-3165767

closes odoo/odoo#128059

X-original-commit: cdf74e8a56da6a776ff52ef534c3c9c647519d13
Signed-off-by: David Monjoie (dmo) <dmo@odoo.com>

The module `mass_mailing_event_sms` extends couple methods [1] that are defined
in  module `mass_mailing_event` [2]. However, because of the missing dependency
in manifest, user can uninstall `mass_mailing_event`, while keep
`mass_mailing_event_sms` installed. This leads to error `'super' object has no
attribute 'action_invite_contacts'` [3].

Fix it by adding the missing dependency explicitly.

[1]: https://github.com/odoo/odoo/blob/fd508fe436c64780a8454ddeb6b7ec8f1f80d7c5/addons/mass_mailing_event_sms/models/event.py

[2]:
https://github.com/odoo/odoo/blob/fd508fe436c64780a8454ddeb6b7ec8f1f80d7c5/addons/mass_mailing_event/models/event.py#L23

[3]: https://online.sentry.io/issues/4280254156/



closes odoo/odoo#127995

X-original-commit: add78c90
Signed-off-by: Ivan Elizaryev (iel) <iel@odoo.com>

Trying to access quotations using an older version of a browser, that
doesn't support `structuredClone` like i.e Safari <15.3 will throw a
traceback that will block the regular usage of the app.

We can use an older alternative to handle the deep cloning, with this
approach tho, we will lose the support of Dates, RegExps, Maps, Sets,
Blobs, FileLists, ImageDatas, sparse Arrays, Typed Arrays.

opw-3386434

closes odoo/odoo#127287

Signed-off-by: Samuel Degueldre (sad) <sad@odoo.com>

Sometimes, the net price and the gross price are not present in the
invoice line, but the line subtotal is (for instance, with some xml from
Billit). In this case, it is still possible to infer the Odoo unit price
and parse the xml correctly.

opw-3384704

closes odoo/odoo#128303

X-original-commit: a8c82e6e
Signed-off-by: Laurent Smet (las) <las@odoo.com>
Signed-off-by: Julien Van Roy (juvr) <juvr@odoo.com>

Steps to reproduce the bugs:

- Add a banner on the homepage
- Click on the "create a link to target this section" button.
- Edit the anchor name to "bannerAnchor".
- Drop the image-text snippet.
- Double click on the button inside the snippet.
- Choose the homepage as the URL ("/")
- Open the "Page Anchor" select, choose "#bannerAnchor"
- Validate the changes.
- Double Click on the snippet button again.
- First bug: The URL properly shows "/#bannerAnchor" but the page anchor
select does not show anything.
- Open the page anchor select again.
- Second Bug: the "bannerAnchor" option does not appear as a choice.

This commit fixes the two bugs described above.

task-3378864

closes odoo/odoo#128201

X-original-commit: e0f17d9d
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>

A serialization error can happen when chatting with another
user from the company. To reproduce:

- Log into Odoo as User A
- Open another Odoo tab in the same window as User A
- In private mode log into Odoo as User B
- Send a message via chat from User B to User A.

A concurrent update happens in channel_fetched method when writing
on mail_channel_partner.fetched_message_id.

To fix that, update the field
through raw SQL using FOR NO KEY UPDATE SKIP LOCKED in select subquery.
This skips the row should it be already locked, which is fine
as we only need to first transaction in the queue to complete.

opw-3164584

closes odoo/odoo#128154

X-original-commit: 757bfb69
Signed-off-by: Matthieu Stockbauer (tsm) <tsm@odoo.com>
Signed-off-by: Aurélien van Delft (avd) <avd@odoo.com>

*: mail

This commit fixes the href used by the PhoneField. Following the
specs of a phone uri, spaces must be removed from the phone number
when using the href attribute.

A test has been added to verify that any spaces are removed from
a given phone number.

In mail, the SMS button href has been edited for the same purpose.

task-3371999

closes odoo/odoo#125613

Signed-off-by: Florent Dardenne (dafl) <dafl@odoo.com>

When a RR updates the qty of a POL, the qty to order of that RR will
be incorrect

To reproduce the issue:
1. Create a product
   - Storable
   - With a vendor
2. Create a RR:
   - Min 0
   - Max 0
   - Factor 1
3. Confirm a delivery with 1 x P
   - It should create a PO
4. Confirm a second delivery with 1 x P
    - The POL of the PO should be updated
5. Open the Replenishment page

Error: The qty to order of the product is 1 while it should be 0

`qty_to_order` is a computed field and one of the `depends` is the POL
related to the product. This explains why, after step 3, everything
is ok: the compute is triggered (because of the new POL) and the qty
to order becomes 0. However, step 4, the POL qty is updated -> it
does not concern any `depends` -> the compute is not triggered,
hence the error

OPW-3292297

closes odoo/odoo#128245

X-original-commit: 80521431601323c1eb7c85cafbf08e8ae0adbdd6
Signed-off-by: William Henrotin (whe) <whe@odoo.com>
Signed-off-by: Adrien Widart (awt) <awt@odoo.com>

On-time-rate is a non-stored computed fields that can take
some time to load because some partners may have lots of
related purchase_orders. The compute function in itself
is relatively difficult to optimize further. This commit
introduces a new system parameter to reduce the timerange of
orders to consider when computing On-Time Delivery Rate.

That way, if for some customers the on_time_rate computation takes too
much time (leading to a slow FormView loading), they can reduce
the accuracy of the estimation to speedup the field's computation.

closes odoo/odoo#128156

X-original-commit: 2e766f11
Signed-off-by: William Henrotin (whe) <whe@odoo.com>
Signed-off-by: Aurélien van Delft (avd) <avd@odoo.com>

Steps to reproduce the bug:
- Connect with a company using USD currency.
- Create a storable product "P1":
    - Cost: $100

- Create a Purchase order:
    - Add 1 unit of "P1"
    - Currency: USD

- Create another Purchase order:
    - Add 1 unit of "P1"
    - Currency: EUR

- Go to the purchase analysis and select the list view.

Problem:
The purchase order in EUR is converted into the current company
currency, but the Euro currency symbol is used instead of the dollar
symbol

opw-3354221
opw-3348265

closes odoo/odoo#127783

X-original-commit: 6fc5bb27
Signed-off-by: William Henrotin (whe) <whe@odoo.com>
Signed-off-by: Djamel Touati (otd) <otd@odoo.com>

__Current behavior before PR:__
When no width and height is set to resize an image, the dimensions are guessed using the field name. For instance, an image field with `field_name = "XXXX_123"` is resized to 123 pixels when fetched.
However this guess should be done only to know the size of the placeholder to display if there is no actual image.
When there is an image stored in the field, there is no need to guess size.

__Description of the fix:__
Move the call to the method `image_guess_size_from_field_name` in the condition where the `stream` is not set and therefore a placeholder is displayed instead.

closes odoo/odoo#118968

Related: https://github.com/odoo/odoo/pull/117343


Signed-off-by: Julien Castiaux (juc) <juc@odoo.com>

Steps to reproduce:

  - Install CRM and Helpdesk modules (for test purposes)
  - Set a custom alias domain (e.g. "mydomain.com")
  - Go to CRM > Configuration > Sales Teams
  - Check that a team has en email Alias (e.g. "info@mydomain.com")
  - Go to Helpdesk > Configuration > Helpdesk Teams
  - Check that a team has en email Alias (e.g. "support@mydomain.com")
  - Email your instance with the following `to` value:
    info@mydomain.com, support@test.com
    (notice second email does not match the DB alias domain)
  - Go to CRM : A task has been created
  - Go to Helpdesk : A ticket has been created

Issue:

  The ticket in Helpdesk should not have been created.

Cause:

  The message_route method does not check the domain of the email
  address before creating the routes.

Solution:

  If `mail.catchall.domain.allowed` system parameter is set, filter to
  only keep the emails address that match the allowed domains (including
  domain set in `mail.catchall.domain` system parameter).

  The value of `mail.catchall.domain.allowed` system parameter should
  be a comma separated list of domains. e.g. `example.com,example.org`

opw-3150972

closes odoo/odoo#128257

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

Receiving a kit's component will fail in AVCO + multi-uom

To reproduce:
1. Create a product category PC
   - Costing Method: AVCO
2. Create two products P_compo, P_kit
   - P_kit:
     - In Units
   - P_compo:
     - In L
     - Storable
     - Category PC
3. Create a BoM
   - Product: P_kit
   - Type: Kit
   - Components: 1 x P_compo
4. Create and confirm a PO with 1 x P_kit
5. Process the receipt

Error: When validating the receipt, a user error is displayed: "The
unit of measure L defined on the order line doesn't belong to the
same category [...]"

When processing the SM, we create the in-SVL. To do so, at some
point, we need the unit price of the SM, and here is where the error
comes from:
https://github.com/odoo/odoo/blob/708c3d063482e365e49a04f633c83e90e6fa4356/addons/purchase_stock/models/stock_move.py#L39


`self.product_id` is P_component, but `line.product_id` is P_kit,
hence the error with the UoM1
And there will be some similar errors with the `if` block, L40 (we
compare some SM quantities and some POL quantities: we are mixing
components and kit)

For now, in case of a kit, we will always use the `else` block (i.e.,
the unit price of the POL). This will be improved in master

OPW-3357685

closes odoo/odoo#128041

Signed-off-by: William Henrotin (whe) <whe@odoo.com>

The test `test_duplicate_project_duplicates_milestones_on_tasks` and the test class `TestSoLineMilestones`
fail when demo data are not installed.
This commit makes it demo data independent.

Task-3410352

closes odoo/odoo#127326

Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>

Description of the issue/feature this PR addresses:
In the project task view, add initially planned hours 0.05 and assigned a
complete value to the the task then the progress bar shows the wrong value

Current behavior before PR:
when adding the  00:05 planned hours and assigning the complete duration the
The progress bar value is not right

Desired behavior after PR is merged:
progress bar value should be right

task-3280609

closes odoo/odoo#128170

X-original-commit: 052dfb5f
Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>

Livechat override of `_message_update_content` accesses `self` channel
but it was not called with the guest env, leading to access error.

closes odoo/odoo#128200

Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>

Steps to reproduce:
- set shipping methods country to mexico (empty states)
- fill an order on website on check out select seprate shipping/billing
- on billing set country as US
- on shipping the only country avialable is mexico
- avialable states are the ones from the US not mexico

Bug:
the states are set from the country of the customer even though it isn't
an option on any carrier.
bug was introduced by this commit[1]

Fix:
revert the mentioned commit(1) since a new commit[2] was introduced that
correctly handles that use case too

[1]:https://github.com/odoo/odoo/commit/d59fe9c58c2dcc2bf6613adb7ac3662597b50496
[2]:https://github.com/odoo/odoo/commit/297641da69982d6c76bd591296636b479cabf657



opw-3230361

closes odoo/odoo#128185

X-original-commit: 264b8fb8
Signed-off-by: William Henrotin (whe) <whe@odoo.com>
Signed-off-by: Walid Hanniche (waha) <waha@odoo.com>

Commit [1] was forward ported in Odoo 16 with commit [2] which actually
was badly rebased.
The conflict resolution led to an extra line somehow that shouldn't have
been there.

runbot-23175

[1]: https://github.com/odoo/odoo/commit/b6c82b33e7b702cb432a3b1eb92c3d968d22af99
[2]: https://github.com/odoo/odoo/commit/0f8f0aa84ac0a852aaa92653a3952404cbbe9187#diff-fac2e83d66fbd557807861a2fa1aadefb43a91bd14fdd0958c5893fef4b1d346R415



closes odoo/odoo#128155

Signed-off-by: Romain Derie (rde) <rde@odoo.com>

Change a constraint that was meant to prevent deletion of an
account.payment.method.line when related provider is in 'enabled'
or 'test' state. The constraint is now handled only on the payment method
lines that are actually modified, and not on everything like previously.
This constraint was failing during upgrades because it was too broad,
its initial purpose was to raise error to user at the moment he tries
to remove payment method lines from its journals.

closes odoo/odoo#128094

X-original-commit: 70f8abbc
Signed-off-by: Laurent Smet (las) <las@odoo.com>
Signed-off-by: Claire Bretton (clbr) <clbr@odoo.com>

Current behaviour:
Next contracts searching will search incorrect state.

Expected behaviour:
Next contracts should not contain draft state contract.

Explanation:
Contracts state field new state should use the value draft.

closes odoo/odoo#128082

X-original-commit: aaf36439
Signed-off-by: Kevin Baptiste <kba@odoo.com>

X-original-commit: f158abd5
Part-of: odoo/odoo#128082

Create a Bill
Register payment
Create the bank statement
Match with the payment
Go to accounting dashboard, hit "Vendor Bill" (open bill list view)
Clear filters
Add filter: Unpaid

Issue: Users should not be able to clear the journal filter when opening
the bill view

This commit align the behavior of the dashboard to the menu entries
by adding a default search domain to the actions instead of the default
search filter

opw-3228450

closes odoo/odoo#125273

Signed-off-by: Olivier Colson (oco) <oco@odoo.com>

Before this commit if we go to website and choose tasks and if we search
anything it shows no tasks available and if we select milestone it shows table.

Steps:
- Go to website and select tasks and search anything in search bar.
- Showing  no tasks available
- choose milestone from drop-down and search anything it will show table labels.

Fix:
- Added condition for checking if milestone is passing empty record set  and
 added another condition to handle it

task-3183771

closes odoo/odoo#114407

Signed-off-by: Xavier Bol (xbo) <xbo@odoo.com>

__Description of the issue:__
- The `replace` method in JS only replace the first occurrence of a
string (unless `g` flag is used in the regex)
- There could be an apostrophe (`‘`) in a string value which would be
replaced by a quote (`“`)
- There could be “None”, “False” in a string value which would be
replaced too
- “True” is not taken into account

__Description of the fix:__
Those regex are meant to deal with more edge cases when transforming a
python dict to a JSON in JS. However there are still ways it could go
wrong. For the forward port in master, it could be a good idea to
consider converting dictionnaries directly in the backend using the
`json` python library.

__Steps to reproduce the issue:__
1. Edit the view `website.contactus`
(If `website_crm` is installed, either uninstall it or disable the
`website_crm.contactus_form` view)
2. At line 5, change the attribute `t-att-data-values` to a more
complicated dict like:
```
"{'email_to': res_company.email, 'name': 'Alice True', 'age': None, 'active': True, 'attr1': None , 'attr2': False , 'attr3': 'let\'s go'}"
```
3. Go to `/contactus` on the website
↳ Traceback

opw-3328690
task-3340946

closes odoo/odoo#128068

X-original-commit: 5360e10d
Signed-off-by: Romain Derie (rde) <rde@odoo.com>

Prior to this commit, the application encountered errors when the
'Cash In' or 'Cash Out' buttons were clicked in the cash move popup,
while the input field was empty or contained `-`. These actions
triggered the `handleInputChange` function, which wasn't equipped to
handle these cases.

This commit fixes this issue by adding appropriate validation checks in
the `handleInputChange` function to prevent errors when handling empty
or `-`.

opw-3419645

closes odoo/odoo#128061

Signed-off-by: Joseph Caburnay (jcb) <jcb@odoo.com>

Usecase to reproduce:
- Create and validate a PO + receipt
- Import a file containing a different PO line quantity

Expected behavior:
The PO line is modified and the receipt has the a new move

Current behavior:
UserError asking to modify the quantity done of stock.move.line instead
reserved quantity.

Following commit 76ad7b7d

The purpose is to block import with reserved quantity

It happens because the PO line import trigger the creation of a new
stock.move and reserve it (create the stock.move.line). However since
it's created by the system the data are correct.

There is no issue in multiple step since the internal step requires
the move_orig_ids and thus the product_uom_qty is empty

To fix it:
- Relax the constraint to only consider sml having an impact on quant

opw-3336131

closes odoo/odoo#127888

X-original-commit: 38468d0364519cf90c2546cc4a11b93da195b604
Signed-off-by: William Henrotin (whe) <whe@odoo.com>

When user creates a new 'livechat channel' in website, and click on
'Optimize SEO' a traceback will appear.

Step to reproduce:
- Install 'website' and 'im_livechat' module
- Go to 'website' module
- Click on 'NEW' and then create a new 'Livechat Widget'
- Go to 'Site' and click on 'Optimize SEO'

Error: A traceback appears: Invalid field 'website_meta_title' on model
'im_livechat.channel'

The menu should not be shown for such model which do not inherit the
SEO mixin. This commit ensures that.

sentry-4241511888

closes odoo/odoo#127043

Signed-off-by: Colin Louis (loco) <loco@odoo.com>

Purpose:
--------
Currently, the calendar common popover has an incorrect color class if
the value of the field used to color the records in the calendar is not
a number. Therefore the popover header remains grey although the event
is colored, and the header content is misaligned.

This commit fixes this behavior by using the `getColor` method to obtain
the class name to use in the popover, which is the method currently used
to obtain the class name to use in the event. If this method does not
return a number, the default color class (o_calendar_color_0) is used.

Task-3239985

closes odoo/odoo#123110

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

When investigating an issue on a customer database, the diff view modal
can be pretty useful. However it is not very good looking and therefore
poorly readable.

This PR improves the CSS styling of that modal so that it resemble more
the diff view of GitHub. This is done by:
- Increasing the width of the modal
- Aligning the text to the top of the table cell, that way there is no
text floating in the middle of two lines
- Lightly coloring the whole line when there is a change on it while the
actual change is on a darker background
- Putting in red all types of change on the left and in green on the
right (instead of mixing green, red and orange together)

This commit is improving the tool that was made at [`96d3fa4e`](https://github.com/odoo/odoo/commit/96d3fa4e01bf8afc35dbf0b7301ce75c6bf3a5c7

)

closes odoo/odoo#127282

X-original-commit: bc188d62
Signed-off-by: Romain Derie (rde) <rde@odoo.com>

before this commit, the warning message is not
added to the pot file.

warning added in this commit: https://github.com/odoo/odoo/commit/52631ac88c1ec8f6f5fd6542d6b38a200f83372c



after this commit, the pot file is updated
to its latest.

closes odoo/odoo#126632

Signed-off-by: Joseph Caburnay (jcb) <jcb@odoo.com>