Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0043819Openbravo ERPA. Platformpublic2020-04-22 11:082020-04-27 06:53
salvador_campanella 
platform 
normalmajoralways
closedno change required 
5
 
 
Core
No
0043819: When the org.openbravo.service.integration.amazon.s3 module is upgraded the configuration is lost
In the 1.0.0 version, the configuration was set in the "Attachments configuration" window

After the 1.0.2 version, the configuration is set in the "Amazon S3 Configuration"

This change because the configured previously set to be lost after doing the upgrade.

You can see the changeset that causes this problem
https://gitlab.com/openbravo/product/pmods/org.openbravo.service.integration.amazon.s3/-/commit/85629ba404ad236391d4e591341df2e8f8ec1422 [^]

And the mantis issue:
https://issues.openbravo.com/view.php?id=39427 [^]
- install de module in the version 1.0.0
- Create and save the respective configuration in the "Attachments configuration" window http://wiki.openbravo.com/wiki/Module:Integration_With_Amazon_S3 [^]
- Upgrade the module to a version equals o higher than 1.0.2
- Find the configuration in the "Amazon S3 Configuration"

Result: the configuration is missing and is necessary to introduce it again
Create a module script that set the configuration in the new structure
No tags attached.
caused by feature request 0039427 closed caristu Modules Extend the Amazon S3 API to be able to store files apart from the attachments 
Issue History
2020-04-22 11:08salvador_campanellaNew Issue
2020-04-22 11:08salvador_campanellaAssigned To => platform
2020-04-22 11:08salvador_campanellaModules => Core
2020-04-22 11:08salvador_campanellaResolution time => 1589320800
2020-04-22 11:08salvador_campanellaTriggers an Emergency Pack => No
2020-04-22 17:20rafarodaRelationship addedcaused by 0039427
2020-04-27 06:53alostaleNote Added: 0119406
2020-04-27 06:53alostaleStatusnew => closed
2020-04-27 06:53alostaleResolutionopen => no change required

Notes
(0119406)
alostale   
2020-04-27 06:53   
Release 1.0.0 was a preliminary version which only a few customers had installed. This change was communicated to be taken into account by those customers on update to mnaually reapply configuration.

No further actions will be taken.