c2c-oerpscenario team mailing list archive

["Ferdinand @ Camptocamp" <384826@xxxxxxxxxxxxxxxxxx>]

@xrg
thanks for clarifiying this (a bit)

what I was trying to say that after updating a module (changes in py files as Jay put it) the server has to be restarted. 
this can only be done (AFAIK) from someone who has access to the server.
Hence importing and updateing modules using a client updates only the XML in the database, but does not restart the server - leaving the whole thing in an inconsitent state by default. I can't believe that this can be considered as userfriendly.  
IMHO automatically restarting the server after update and/or a message telling to do so and/or  a button - "restart server" would be helpful

-- 
"import module + Apply scheduled upgrades" is not equal to the server command --update=module_name
https://bugs.launchpad.net/bugs/384826
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Server: Won't Fix

Bug description:
import module and apply scheduled upgrades transfers the zip file to the server and installs it "partly" - especially view definitions are not available after the upgrade.

workaround - use --update=<moduel-name> and restart the server

this is particularly annoying if the module must be installed by a "non expert" customer who has no access to the server.