Actualización scripts de migración - #111
Open
pepetreshere wants to merge 3765 commits into
Open
Conversation
When sending a mass mail through the composer, if the field ``reply_to`` had to
fall back to being ``email_from``, reply_to would take the value of the template
syntax instead of the rendered value.
This is notably the case when mass-mailing invoices through the accounting app.
Resulting in reply_to fields such as: '{{user.email}}'
On some mail clients (including mailhog), this could also result in template
syntax being shown as part of the subject or sender field.
This commit fixes that by correctly taking the rendered value of 'email_from'
Task-2816845
closes odoo/odoo#95227
Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
This commit attempts to fix an undeterministic error during one of `website_sale_wishlist` tests. Due to a race condition it may happen that the button to add to the wishlist would be re enabled while it should be disabled (if the product is already in the wishlist) causing the tour to fail. closes odoo/odoo#98143 Signed-off-by: William Braeckman (wbr) <wbr@odoo.com>
So that the link works... Task-2954531 closes odoo/odoo#98155 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
Consider this case: Template A has 2 variants: KIT and NOKIT KIT has a total cost of 100, NOKIT costs 50 When selling NOKIT, the current code will select the bom of KIT to calculate the price_unit of NOKIT, which means that when reconciling the aml of the invoice (amount = 100) with the aml of the cogs move (amount = 50), it will be partial due to the difference in amount. This alse messes with the balance sheet report. This fix ensures that only boms directly related to the product or for the generic template are selected. opw-2918080 closes odoo/odoo#97453 Signed-off-by: Steve Van Essche <svs@odoo.com>
/my/account controller blocks name/vat/company_name updating if there are issued invoices. However Before this commit, user can change name via /shop/address page STEPS 1/ install sales, eCommerce,inventory,Accounting 2/ create a sales order from the portal page, validate and create an invoice from SO and post it 3/ Try to change the name from the Portal > Account Result - not possible = correct 4/ Place a new SO by the same portal user and edit the name on the address before proceeding to checkout [1]: https://github.com/odoo/odoo/blob/1f49528a4b198e8912beb33be921d2855c694e2e/addons/account/controllers/portal.py#L111-L113 opw-2848251 closes odoo/odoo#97686 Signed-off-by: William Braeckman (wbr) <wbr@odoo.com>
The model had name_get, but not _name_search, which leads to difference between what user sees and what he get as search results. This patch doesn't fix the issue completly, but adds more search results on searching just by account move (e.g. invoice) name. STEPS: * open menu Analytic Items (account.analytic.line) * make custom filter *Journal items contains "INV/"* ( `[["move_id","ilike","INV"]]` ) BEFORE: no items found even if you see such analytic items --- opw-2691495 closes odoo/odoo#87156 Signed-off-by: William André (wan) <wan@odoo.com>
Steps to reproduce the issue: - Notes app > Kanban view > Create a bunch of notes using the + icon in the kanban view - (optional) Modify the default order of the notes - Add a new note using the quick add feature - Don't modify the order of the notes and refresh the page - The new note will be sent to the bottom of the note list (off-screen if the list is long enough) This happens because new notes have their sequence set to NULL, which places them at the end of the list after ordering by sequence. This commit sets the default sequence of a new note to 0, so that it is placed at the top of the list and adds an additional sort on 'id desc' to consider the case where all notes have the same sequence. opw-2924615 closes odoo/odoo#97023 Signed-off-by: stcc-odoo <stcc@odoo.com>
Facebook no longer supports the option to see the profile pictures of friends who have liked the page. So this commit removes the option (which was no longer useful). See [same issue at WordPress]. [same issue at WordPress]: https://wordpress.org/support/topic/facebook-likebox-disappearance-of-the-faces-of-friends-who-like-the-page/ task-2950329 closes odoo/odoo#98177 Signed-off-by: Romain Derie (rde) <rde@odoo.com>
Steps to reproduce:
- Install `website_event` module
- Go to Events and edit `Design Fair Los Angeles` event
- Edit the title and make it very long then save
- Go to the Website then click on Events in the menu
- Click on Customize and disable `Layout - Columns` to have
a list view.
Issue:
The cover is hidden on edited event.
Cause:
It's a know issue:
https://stackoverflow.com/questions/36247140/why-dont-flex-items-shrink-past-content-size
Solution:
Set min-width: 0 to the div arround the title if screen size bigger
then `sm`.
opw-2882533
closes odoo/odoo#95992
Signed-off-by: Nasreddin Boulif (bon) <bon@odoo.com>
Searching by attributes works via a separate form. It has a copy of other search parameters (`category`, `search`), but not `order`. STEPS 1) enable View "Products Attribute's Filters" in eCommerce 2) enable View "Show Sort by" in eCommerce 3) Set sorting to specific value 4) Change Product Filters Attribute values 5) as you can see, the sorting set in Pt3 is lost.... opw-2956280 closes odoo/odoo#98553 Signed-off-by: William Braeckman (wbr) <wbr@odoo.com>
Exporting data incorrectly formats the float values of group headers Steps to reproduce: 1. Install Planning 2. Open Planning and trigger the list view 3. Remove the default filter and add a group_by on employees 4. Export the data 5. The file produced doesn't have the same format for Allocated Hours in the group headers and in the line details Solution: Create formats for float and monetary values using the user's preferences in decimal separator and decimal precision. For monetary format, we use the biggest decimal precision used in the company currencies. opw-2864273 closes odoo/odoo#94534 Signed-off-by: Julien Castiaux <juc@odoo.com>
Reproduction: 1. Create a dynamic attribute "dyn_att" with a couple of values 2. Create a product template "dyn_prod" with those attribute values 3. Create an order for "dyn_prod", this will trigger creating a variant 4. Make sure to check Variant Grid Entry in Sales Settings 5. Open variant form view of dyn_prod and edit it to allow duplication 6. Duplicating it leads to an error Reason: copying the variant is not possible and disabled here: odoo/odoo#38303 For future convenience, maybe it’s better to give a temporal working solution. The function _create_first_product_variant is used in the product module but only defined in its child module website_sale Fix: copy the product template, create and return its first possible variant. Added test for dynamic variant copy. change the definition place of _create_first_product_variant to module product opw-2790543 closes odoo/odoo#88075 Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com>
Backport of odoo/enterprise@0a8aa0d Don't show the stock input/output accounts in the reconciliation widget. Steps to reproduce: - A product category PC, costing method AVCO, automated valuation and custom stock input(STI)/output(STO) account (reconcile = True) - A Journal Entry with the STI Move line : | Account | Debit | Credit | |---------|-------|--------| | STI | 0.0 | 50.0 | | XXXXXXX | 50.0 | 0.0 | - Create a bank statement with amount corresponding with the journal entry then reconcile -> Line for custom stock input STI account shows up in misc tab on reconciliation widget Fetch all accounts relative to stock accounts properties, then filter them in the domain. opw-2792862 closes odoo/odoo#96131 Signed-off-by: Florian Gilbert (flg) <flg@odoo.com>
Add Jose Moreno Hanshing closes odoo/odoo#98329 Signed-off-by: Josse Colpaert <jco@odoo.com>
In v13 the deafault location of the picking type is used to take the stock in the picking operations of the pos configs. In the migration, this can lead to pickings that were using a common operation type taking the stock from the wrong locations. We prevent it creating new picking types for that configs. TT23199
…ocation_id [13.0][OU-IMP] point_of_sale: stock_location_id
If datetimepickers were used too soon after page loading, they would use the wrong format and UI options as the code in charge of initializing those options was not fully lazy loaded yet. With this patch, we prevent the tempusdominus lib to consider pickers that are in a body that is marked by the lazyloader during the lazy loading of JS files. We could potentially not add the lib attribute (data-toggle="datetimepicker") on those elements and let the business code initializing the pickers add it but that would not have been a stable fix and it may be better this way as this works generically. opw-2944720 closes odoo/odoo#98529 Signed-off-by: Romain Derie (rde) <rde@odoo.com>
…n account This PR adds the 'posted' filter by default on the journal items list view, when coming from an account's form view. opw-2896728 closes odoo/odoo#98183 Signed-off-by: Grazioso Andrea (agr) <agr@odoo.com>
From v13, only certain fields can be updated in a pos.config with an open session. In this case we can safely override that behavior updating the values via SQL to avoid the migration break due to an unconvenient session state. TT23199
…-values [13.0][OU-FIX] point_of_sale: update configs via SQL
This commit addresses a screen refresh problem. closes odoo/odoo#98788 Task: 2961768 Signed-off-by: Arnold Moyaux (arm) <arm@odoo.com>
Before this commit, in invoice/bill, when changing the account of a tax line while having one of the invoice lines with tax 0%, the tax line was not displayed anymore. The cause of the issue is that in _recompute_dynamic_lines method, when setting the tax repartition lines to recompute, we did not filter the 0 tax. The consequence was that we had a delta between expected and current taxes, although the line of tax 0% was not displayed anyway. By filtering the 0 tax, we have expected taxes == current taxes, so we do not have delta anymore, therefore no tax line to recompute. opw-2901833 closes odoo/odoo#97663 Signed-off-by: Florian Gilbert (flg) <flg@odoo.com>
Reverts [this commit] because it modified the format of float numbers in exported xlsx files and we want to avoid introducing an error or unwanted behavior in version 13, for which support will soon come to an end. [this commit]:odoo/odoo@27ab242 closes odoo/odoo#98975 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
Since the accounts without token are useless and could create errors afterwards, we should delete them and automatically create a new one with a new token in case force_create is set to True. closes odoo/odoo#98858 Signed-off-by: Florian Daloze (fda) <fda@odoo.com>
closes odoo/odoo#99083 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
Currently, when creating an invoice from factur_x XML, the vendor is identified by sequentially checking (in this order) the following information : - VAT number - name - email However, when we generate a factur_x XML, we do not include the partner's email address. This means that in some cases, two odoo databases are not able to communicate bills/invoices properly. This commit brings back a behavior that was unintentionally removed in odoo/odoo@d25fdaf opw-2909408 closes odoo/odoo#98896 Signed-off-by: William André (wan) <wan@odoo.com>
closes odoo/odoo#99087 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
[13.0][OU-IMP] base: vacuum of transient models
…e_tab-entry [13.0][FIX] account: don't set exclude_from_invoice_tab for type entry
In the analysis, the record point_of_sale.pos_config_main appears to be deleted. It's true that it is not overridden in the 13.0 version. But this record is not deleted, it still exists as it main definition is in the module point_of_sale. In 12.0 the field crm_team_id is added to point_of_sale.pos_config_main and in 13.0 this field rely only on the _get_default function defined in the pos.config model in pos_sale. There is no need to delete point_of_sale.pos_config_main, and there is no need to modify the crm_team_id value of this record. As this may have been modified by the users.
[13.0][OU-FIX] pos_sale: do not delete point_of_sale.pos_config_main
[13.0][IMP] apriori: edi_oca -> edi
[13.0][FIX] website: also use company logo when website.logo is False
[13.0][OU-FIX] mrp: remove_tables_fks requires list
[13.0][IMP] account: assign tag tags of parent taxes to repartition lines
…mplate [13.0][OU-ADD] product_email_template
[13.0][FIX] github workflows actions
[FIX] account: reversed_entry_id migration was reversed
[13.0][OU-FIX] stock: convert responsible_id to company_dependent
[13.0] [UPD] openupgrade_analysis
…ault_account [13.0][MIG] account_analytic_default_account
Backport of #5765 TT63118 @Tecnativa
[13.0][IMP] base: Load additional renames/merges from env.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
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.
Description of the issue/feature this PR addresses:
Current behavior before PR:
Desired behavior after PR is merged:
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr