← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 685328] Re: Module import: no check on file technical format

 

I clearly don't ask that OpenERP will be able to read any kind of file
format !

I just want it checks fileformat is UTF-8 without BOM with Unix coding,
and that openERP generates an error message/popup if it is not the case.

I would add the fact that the file format is really an issue when
clients use Windows environment because Windows and Office applications
produces natively files that are not in the required formats mentioned
above ! And never OpenERP tells it when you import the module ...  And
nowhere openerp's documentation tells it...

-- 
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/685328

Title:
  Module import: no check on file technical format

Status in OpenObject Server:
  Opinion

Bug description:
  Note this bug is potentially applicable to V6...

On my Windows 7 system, I created an Excel macro that generates an OpenERP module with all the required files (init, terp, and all csv containing datas).

When trying to import the zip folder via the administration menu, the system was importing the module in the module list but the module description form was empty or containing partial data in regards to the TERP file content.

Furthermore, after the import of the module into the module list the system was so corrupted (impossible to create new DB anymore) that I had to reinstall OpenERP from scratch.

After check with OpenERP support, it appeared that it was due to the file technical format generated by Windows and the Excel Macro while OpenERP current requirements are:
- UTF8 (without BOM) for CSV upload files but with windows format supported
- UTF8 (without BOM) for TERP and INIT files but accepting only UNIX format

When you know that, it's OK, you know you have to convert your files format. 

Nevertheless, I think it's a security issue because if someone imports a module with unsupported format it corrupts the system and you see only it when you want to create a new DB !!! 

I think a check with an error message/popup should be implemented in order to be sure of the file technical formats when importing a module.





References