As the function 'action_cancel' is multi, we cannot set the value
'is_locked' to True by using '='. Because it will raise an error if self
contains more or less than 1 record.
To fix this we call the 'write' method which support all cases
This revision ensures that users cannot modify the current quantity or
enter lot numbers from the so-called manager view. This is because the
'tablet view' is not aware of the changes made in the manager view.
Previous to this rev., sometimes None could be added
to the list of _init_modules in the registry, this would
then be problematic in ir_http since a sorted would be
performed on this list, which works in py2 but in py3
None and string can't be compared implicitly.
Purpose:
* when installing enterprise, postgresql refuse to install if there
is a '+' char in the install path.
* when uninstalling, the nssm and python dirs are not removed
Purpose: When installing postgresql under windows, the '+' character is
unallowed. This was creating a bug when using the windows installer the enterprise
version which derivate the install path from the version number.
IAP allow app publishers to charge for ongoing services. In that context, Odoo
acts mostly as a payment platform between the service user (client) and the service
provider (Odoo App developer).
When the quickreate fail and a slow create is used instead, don't
display the error that happened as is done in kanban and calendar
(following 0f7f3fc2f) quick create.
Commit f4200f376b aimed at avoiding 414 errors on too long uri.
But it brought up something else: on a new pos.config, the customer display html was not set due to that commit meddeling with the iframe's url.
This present commit forces the set up of the html field on create and write (according to the values, as usual)
the price to pay is to not being able to edit the html right away
Read(['start', 'start_datetime', 'start_date']) make the cache corrupt
for computed field start_datetime or start_date.
Now we don't read (for nothing ?) these 2 fields.
We can remove the skip for the test #500fabf1
Before this commit, a simple :
x = self.create({'name':'subject', 'allday': False, 'start': foo, 'stop': bar})
create randomly an event withtout start_datetime
- value move lines created when the move is done
- when reducing done out move, increase latest in move in order to not
lose the returned quantity in the fifo chain
In case you have a delivery partner set on your shipping contact,
when checkouting your cart, the preferred carrier will be used instead
of the first available carrier.
The production_id on the stock move line is a helper field for work
orders and you can not assume it is always set correctly. As
non-tracked stock moves create the stock move lines themselves it is not
set.
So, for logging notes, we check the 2 production order fields through
the moves.
Before this fix, you can break a test class by simply adding an
incorrect import like this:
`from gloubiboulga import Casimir`
--> No error message, the test is simply not run
This is due to the fact that we want to ignore ImportError's... only
when there is no `.tests` submodules (actually, we ignored them all!)
This commit fixes the condition and re-enables error logging when tests
actually encounter ImportErrors
Initially, the check was done in _compute_practical_amount.
However, in case of no account_ids, an error is raised at each click until the account_ids are set.
was PR #19860
test_03_test_serial_number_defaults creates 3 stock.production.lot
but in a test case they have the same create_date.
Moreover this test go through _assign_default_final_lot_id that do
a search on lot ordered by create date. That's why the test is non-
determinisitc since it could pick one of the 3 lots randomly
This commit add the id in the order.
When producing a finished product with a lot, also the raw materials
without lot tracking should split the move lines to at least know the
quantities consumed for every lot produced. This way, the traceability
report will not confuse the user.
mncoon