Skip to Content
This question has been flagged
5 Replies
2826 Views
Avatar
iwkse

Hi,

sometimes it happens to add addons in bulk mode, selecting several modules at once and it might happen that one of them has problems and crashes the whole odoo (white page) not allowing to do anything at all.

My fix in this case is to remove the included addon (with submodules) and start to uninstall one by one (this is something that I couldn't find as well..seems not to be a way to uninstall multiple addons, there is for installing but not for uninstalling?) till I find the culprit addon module.

This is time consuming and surely not optimal.

I want to ask to you who have more experience than me with Odoo, how can you directly spot the bad addon and just uninstall it.

Kind regards

Avatar
Discard
Avatar
Ermin Trevisan
Best Answer

Easiest way to avoid this: Don't use bulk installation for third party modules, only for Odoo and OCA modules.

Avatar
Discard
Jake Robinson

It's a sad reflection on the general quality of the app store, but it's so true. It's just not at the point where you should be bulk installing.

Ermin Trevisan

... even more: never install a third party module on a production server. Test it first on a test server.

Avatar
iwkse
Author Best Answer

Thanks for your comments.

Of course this is not a production server, it's a test server  used as a playground. I would have expected at least a way to bulk remove modules (why it's only possible to bulk install?)

The modules I've installed are only from odoo or OCA and the issue it's about some of OCA modules. In general I would have expected odoo to handle such errors in a cleaner way. An addon shouldn't crash the whole app with cryptic message eg: "QWeb2: Template 'Dialog' not found" and let you uninstall one by one (when the system works after you exclude the modules path) a bunch of modules till you find the culprit. Seems a little odd to me.

I really appreciate odoo and this is only a constructive criticism to the software, hoping to make it always better.

Cheers

PS. special thanks to Ravi Gadhia

Avatar
Discard
Avatar
Ravi Gadhia
Best Answer

Hi 

1) look at traceback in the server log and in call stack find that custom module path which may cause the problem
2) start the browser in debug assets mode and look at traceback and inspect call stack and open relevant fine in browser source tab and using reveal in sidebar find the culprit module

those are the very first step to find the buggy module but its not work in all the cases. then roll the sleeves debug step by step using print/pdb and console/debugger; 
​

Avatar
Discard