c2c-oerpscenario team mailing list archive

[xrg <xrg@xxxxxxxxx>]

On Friday 12 November 2010, you wrote:
> I'm closing this bug, as it's indeed a very-low priority wishlist that
> we can't fix easily, and out of scope at the moment (none of the
> proposed solutions are both acceptable and easy to implement)
> ...

Let me make 2 comments on that:
1st: installing source (python) modules through the OpenERP server should be 
highly discouraged for production systems. Reason is, the server should NOT 
have write access to its own code, as a security measure. So, the whole .zip 
idea is something I oppose. Please, install the files as administrator, at a 
system level (eg. through RPMs or DEBs) and then instruct the OpenERP server 
to load those modules.

2nd: the command-line --import or --update options serve another purpose: they 
are intended for those cases where the server wouldn't start because of a 
previously failed installation. They cause those modules to be rectified (eg. 
at our development trees we had a chance that the 'base' module would 
introduce new columns. So, the databases we had[1] wouldn't allow the clients 
to connect. 


[1] I repeat, this only happened during the development cycle, wouldn't happen 
at release-ready versions.

-- 
"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.