c2c-oerpscenario team mailing list archive

[xrg <xrg@xxxxxxxxx>]

On Friday 08 April 2011, you wrote:
> Public bug reported:
> 
> if for some reasons (coding or reference error) loading of xml fails the
> module remains in state "to be installed/updated" and the server does
> not restart any more
> 
> IMHO a better and more userfriendly solution would be to set all modules to
> be installed/updated to a safe state "uninstalled" if a xml loading error
> occurs or to allow the server to reastart without loading

That is a long-known issue.

I prefer to leave it as it is, now.
Because, on the other hand, if you load /half/ of your modules (to a running 
db, not a new one), you may get different behaviour of your system..

Take the case of stock_no_auto_picking. Would it be reasonable to continue 
working with a server that was supposed to load that module and it failed?

I think you also need another remark here:
Instead of reloading the server all the time (on a development environment), 
you can use the base_module_import addon[1] to safely test your xml files.


[1] only found on my tree, use with care, please!
-- 
Say NO to spam and viruses. Stop using Microsoft Windows!

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/754373

Title:
  install + update: error in xml prohibts serverrestart

Status in OpenERP Server:
  New

Bug description:
  if for some reasons (coding or reference error) loading of xml fails
  the module remains in state "to be installed/updated" and the server
  does not restart any more

  IMHO a better and more userfriendly solution would be to set all modules to be installed/updated to a safe state "uninstalled" if a xml loading error occurs
  or to allow the server to reastart without loading