8.0 Latest updates #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…price of delivery The computation expects uom and it was wrongly passing uos qunatities.
Bug lp:1222289, opw 597639
Missing backport of commit f652402 for buffered dataset Again, should not be forwardported
When a record is created, if it inherits from mail.thread, a message 'OBJECT created' is posted. 'created' is translated but the name of the model wasn't. This fix uses the name of the linked ir.model which is already a translatable field. lp:1262000, opw 611043
…when my product doesn't have any variant
…to get some fields which will be already join in the description from values to custom the behavior from create_lead function
[FIX] account: the 'Customer taxes' field on the product is readonly when my product doesn't have any variant
… 2 lines for the small boxes
…iter/author to insert some tricky code like form or JS
… ? I don't think so...
…ton-css-chm [FIX] website.snippet: display snippet editor button inline insead of 2 lines for the small boxes
Purchase orders created with invoice policy 'Based on incoming shipments' were not keeping the reference to the account analytic distribution when invoiced. opw 607577
…the field is_delivery from module delivery
replace ormcache_context by ormcache: use the context in the cache key is useless set skiparg=3 (default skiparg=2) so the uid is not used in the cache key: the filestore path is the same for all database users
lp:1223922, opw 609656
…difications to be saved anyway
The state has been replaced by stage_id in the view, so the state is no longer used Moreover, when doing an advanced search, the field state is visible and if used -> Traceback (because not available in the report sql table) opw-609984
The user_id is already set by the prepare_invoice method, which is called before the prepare_invoice_group (the user_id is already set, thus) Besides, _prepare_invoice is overriden in sale_stock, to set the picking sale order salesman as user_id, and, without this correct, grouping invoicse by partner re-set the user_id to uid, which is wrong.
…se the path and the id are not separated (e.g.: '/members42')
When searching on memberships, we use domain clauses in the format 'partner.x = y' where partner is a many2one to res.partner. The object res.partner has strict security rules for public users and this search will return zero result if not done with SUPERUSER_ID. In addition, we need to access the list of products (membership_ids) in the domain to be sure we will retrieve only published membership (otherwise it would crash in the sort below).
If the selection label (not value) had accents, it wasn't possible to import it using the label having accents
Allowing UNPACK_SEQUENCE allows the use of the "multi" assignation: a, b = [1,2] for a,b in items
The `prepare_result` dict shouldn't keep a browse record of a survey, as it is explicitely passed to the template by the controller `survey_reporting`
A bit of commenting in order to help future debugging and unf**king of the survey reporting tool.
…s not have a valid email address, redirect to the user's profile instead of crashing when trying to send notifications.
Changing .po files to avoid to retranslate existing terms. Fixes #1328
[FIX] account: fix unexpected invalidation of field account_invoice.reconciled
…/join mode especially for XOR) Makes ordering transitions easier and more deterministic. (Rebase of #1564)
Mandatory since we changed the structure of the dom since 8.0.
- simplify the code by removing unused cases - do not modify input argument 'value' of create/write - do not call BaseModel.read() with reified group fields (this causes warnings)
It is not useful to try to create foreign keys when the destination model is a PostgreSQL view for example. We already do this kind of verifications but ir.actions and transient models but did not for _auto.
…thods This makes the patching mechanism more flexible, and enables patching BaseModel, for instance. This should fix #1501.
opw-611106, when clicking quickly Sales > Opportunities than Sales > Leads.
…t variant Before, the field purchase_ok was set as readonly on the product form if the product wasn't a variant, to avoid users to set all the products variants associated to the product template to be set as purchase able in one action. We now consider that this can be done by the end user
…peruser_id as this field is required in the form view. However no data is displayed, and no data about the contracts are leaked, so no security holes.
…current value The existing code was buggy when writing on *2many fields with a list of commands: the value was converted for the cache, but taking an empty recordset as the current value of the field.
(partial revert of 44a5268)
The one2many field 'user_ids' was initialized with an incorrect value for the inverse field 'wizard_id', using a res.users id. The latter was causing a MissingError exception. The fix is simply to not define explicitly the inverse field in the one2many. Also did a small cleanup of the code of the wizard.
Singleton object was required while access model properties, but search returns multiple results and hence caused traceback while accessing record.property
…all the module Added a record of im_livechat.channel in website_livechat data
As `_inherits` fields are now handled via `related` fields (not stored, obviously), a new descriptor `searchable` has been added to `fields_get()` result to indicated if the field is searchable or not.
If a selection field is defined by a list as selection, such as:
state = fields.Selection([('a', 'A'), ('b', 'B')])
one can extend it by inheritance by redefining the field, as:
state = fields.Selection(selection_add=[('c', 'C')])
The result is that the selection field will have the list
[('a', 'A'), ('b', 'B'), ('c', 'C')] as selection.
This avoids code duplication between methods, and keeps backward compatibility with existing code overriding _name_search().
+ correct tests
Due to the use of a sudo env, the records were being added to the sudo cache one by one instead of all at once. This meant the prefetching was not able to load all records at once, leading to prohibitive times when processing thousands of records.
…pen (assign) or close an issue. Those fields now have a conditional store, because they were not recomputed even when changing date_open and date_closed. Changing the stage now correctly changes the date_closed. Also added some fixes in resource module, the date was not correctly taken into account when computing the number of working hours between two dates.
…e + be sure that date_open and date_closed fields are set)
… managing the received field_list + improved custom call to default_get to correctly manage its in and out values.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.