Odoo-sh Upgrade : How to disable a view / uninstall a module during upgrade process (v13 to v15)?

Question

During the upgrade process on odoo.sh on branch BrStaging, there are errors in the log panel. Some obsolete custom Modules or Views are the cause of these errors. To disable or uninstall them, we have to use SQL queries because we cannot enter odoo which cannot start:

My Try: using in Odoo-sh> SHELL-Tab, the shell command : psql:

To disable a view

UPDATE public.ir_ui_view SET active = false WHERE id = 10381;

To disable/uninstall a module

UPDATE ir_module_module set state='to remove'
WHERE name in ('my_custom_module') and state='installed';

...have tried that request too:

UPDATE ir_module_module set state='uninstallable'
WHERE name in ('my_custom_module') and state='installed';

...But it does t work: after a commit or restart (command: odoosh-restart) the related error still remains!

How to disable a view and uninstall a module during the upgrade process from v13 to v15 ??

How to perform update-request on the database used for the upgrade process ? — S Bonnet
– S Bonnet, Commented Nov 4, 2022 at 11:19

S Bonnet · Accepted Answer · 2023-01-29 09:45:18Z

2

The solution, I have found is using a pre-migrate.py file into one of my custom module : my_custom_module/migrations/15.0.0.0.0/pre-migrate.py which contain the Sql query that i need to execute, to correct the upgrade-log-Error:

def migrate(cr, version):    

    # TO CORRECT UPGRADE ERROR 1 : Element '<xpath expr="//xxxx">' cannot be located in parent view

    cr.execute("""
        update ir_ui_view v
        set inherit_id = NULL, mode='primary', active = false
        where
        v.id in (10563,10539)
    """)

answered Jan 29, 2023 at 9:45

S Bonnet

1,7221 gold badge13 silver badges34 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Lukas May 21 at 9:38

Right solution, also .../migration/0.0.0 folder would be possible to use. The reason why direct update of the database is not working is that the migration process starts with fresh copy from production instance and all changes done in the currently migrated database are thrown away. Changes would have to be done in the main DB and that is not a good idea. Alternatively is possible to uninstall all unused/old modules by hand on production instance, change code and then run migration. But the solution with pre-migration script looks more elegant :)

Collectives™ on Stack Overflow

Odoo-sh Upgrade : How to disable a view / uninstall a module during upgrade process (v13 to v15)?

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related