Odoo Upgrade to v15 - OpenUpgrade : dealing with obsolete but inherited views?

By -

I am currently following the UPGRADE process in odoo.sh to migrate to Odoo v15. Because some of the templates have been removed or renamed in v15, I got 100 errors similar to:

ValueError: External ID not found in the system: website_sale.header

Most of these errors are caused by the third party template: "Theme Clarico Vega".

How to deal with (Theme-) templates which are not existing in the destination version? I have heard about pre-migrate scripts to disable views during migration process: https://www.youtube.com/watch?v=n0jQQlEnUUQ but i can t figure out how to manage the steps to handle views (see screen shots in attach). Scripts examples (pre-migrate.py, post-migrate.py and end-migrate.py) are welcome :)

enter image description here enter image description here enter image description here

I have also tried to figure out what to do with the OpenUpgrade informations: https://github.com/OCA/OpenUpgrade/blob/15.0/openupgrade_scripts/scripts/website_blog/15.0.1.1/upgrade_analysis.txt For instance:

---Models in module 'website_blog'---
---Fields in module 'website_blog'---
---XML records in module 'website_blog'---
NEW ir.asset: website_blog.s_blog_posts_000_js
NEW ir.ui.view: website_blog.s_blog_posts
DEL ir.ui.view: website_blog.assets_editor
DEL ir.ui.view: website_blog.assets_frontend
DEL ir.ui.view: website_blog.assets_snippet_s_latest_posts_css_000
DEL ir.ui.view: website_blog.s_latest_posts
DEL ir.ui.view: website_blog.s_latest_posts_big_picture_template
NEW website.snippet.filter: website_blog.dynamic_filter_latest_blog_posts


Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more