Repository navigation
V14 v3tech upgrade - #749
Merged
Merged
Conversation
[14.0][OU-ADD] mrp_account: Nothing to do
Even no analysis file. TT40273
…k_product_configurator [14.0][OU-ADD] website_sale_stock_product_configurator: Nothing to do
The feature of this module has been integrated in core TT34839
…ptcha [14.0][OU-ADD] website_form_recaptcha: Merged in website_form
…sive [OU-FIX] calendar: Fix possible invalid recursive settings
[14.0][FIX] apriori: fix names of camt modules
…ale_product_attribute_filter_category TT37008
…ttribute_filter_category [OU-ADD] website_sale_attribute_filter_category: Renamed to website_sale_product_attribute_filter_category
As these records are created as noupdate=1, we need to manually assign the parent categories that are new in v14. TT41258
…_category-parent [14.0][OU-FIX] base: Assign parent module categories
[14.0][OU-ADD] l10n_multilang: Nothing to do
After odoo/odoo#110918, we put this new format on migrated v14 DBs.
…ddress_format [14.0][OU-IMP] base: Spanish address format
[ADD] website_analytics_piwik renamed to website_analytics_matomo
[FIX][14.0] calendar: fix duplicated events
Due to the error dpkg: error processing archive /tmp/apt-dpkg-install-F5P19I/09-libodbc1_2.3.11_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libodbc.so.2.0.0', which is also in package libodbc2:amd64 2.3.9-5
[14.0][FIX] Remove unixodbc package
This reverts commit 777c740. The module is still there, so it shouldn't be merged: https://github.com/odoo/odoo/tree/14.0/addons/theme_default
[14.0][OU-FIX] theme_default: Revert "[OU-ADD] theme_default: Merged in website"
…sheet_time_control-helpdesk_mgmt_timesheet [14.0][OU-ADD] apriori: merge helpdesk_mgmt_timesheet_time_control into helpdesk_mgmt_timesheet
…ependent [14.0][OU-FIX] account: convert cash rounding fields to company_dependent
fix queries pre-filling the debit_currency_id and credit_currency_id fields of account.partial.reconcile records: debit_move_id and credit_move_id are many2one fields to account.move.line, not to account.move. this resulted in null columns, ignoring the records when computing account.move.line.amount_residual in odoo 16.
…al_reconcile_currency_id [14.0][OU-FIX] fix account.partial.reconcile currency
explain the change of uom rounding value on some records and avoid overwriting the value if it has been changed.
Backport of OCA#5765 TT63118 @Tecnativa
[14.0][IMP] base: Load additional renames/merges from env.
Call cow_templates_mark_if_equal_to_upstream() in the pre-migration and cow_templates_replicate_upstream() in the end-migration. A website that enables an optional template through the Customize widget but never edits it keeps a COW copy; until now that copy was never resynced on migration, so it kept the origin arch_db and inherit_id. When a module migration re-targets which template the view inherits from, the stale copy points at the old parent and breaks rendering, as seen with website_sale_product_attribute_filter_category when website_sale moved a template between versions. cow_templates_replicate_upstream() also propagates inherit_id since OCA/openupgradelib#463. TT64160
[14.0][OU-IMP] website: reset unmodified COW templates to upstream
…ier_validation_forward
…lidation-forward-merged [14.0][OU-ADD] apriori: purchase_tier_validation_forward merged into base_tier_validation_forward
…iliation in SQL fill_statement_lines_with_no_move creates, through the ORM, an entry for every bank statement line that had none. While each move is still being built, the ORM computes the line's stored is_reconciled as True (no suspense line yet) and keeps it pending. fill_account_bank_statement_line_reconciliation then computes is_reconciled and amount_residual in SQL, and a later flush writes the stale pending values over that result. Lines still in the suspense account end up stored as reconciled, and post_statements posts statements that only hold such lines. Flush the statement lines once the loop is done, so the SQL result stands. Assisted-by: Claude Opus 5.5
…_line_is_reconciled [14.0][OU-FIX] account: flush statement lines before computing their reconciliation in SQL
…ut a successor As in 10.0-13.0 and 15.0-18.0: apriori.lost_modules (to_holidays_in_years, merged into resource, and web_diagram).
survey.ir_cron_clean_empty_surveys is 9.0 noupdate data that no later version ships; it calls survey.user_input.do_clean_emptys, removed in 14.0, and then fails at every run. Databases upgraded before the 10.0 script deleted it still have it.
… 14.0 to_website_search_suggestion(_product) have no 14.0 code (website_sale 14.0 has its own search box): merge them into website / website_sale as lost modules, their views go with them. to_hr_work_day_type (merged into hr) becomes a lost module too: nothing replaces work.day.type.
…d view The end of an update deletes the views its module no longer ships under the module uninstall flag, and the core cascades to the children through inherit_children_ids, which leaves out the archived ones (e.g. an option of the website editor turned off). Their foreign key then keeps the parent from being deleted: 'violates foreign key constraint ir_ui_view_inherit_id_fkey' (website_sale.payment_footer at 17.0). Same fix as in the 10.0-13.0 forks.
14.0 no longer ships the About us page, and the migration deletes its page; the update then deletes the generic view, and the cascade of website on the key takes the website-specific copies too: the About us page a customer had edited with the website editor was lost with its URL (v3tech: its company presentation). Give those copies a key of their own before, their pages and content stay.
…ecord
The unlink patch opened a savepoint for every obsolete record deleted by
_process_end and never released it (its name was even the same for all,
str(uuid4) instead of str(uuid4())). Each open savepoint that deletes keeps a
transactionid lock until the end of the update: a large update holds
thousands of them, and with another update running on the cluster the lock
table ran out ("out of shared memory", hop 17.0 of a real database). Release
the savepoint after the delete, and after the rollback when it fails: 200
deletions now hold 1 lock instead of 201.
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.
No description provided.