Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014683Openbravo ERPA. Platformpublic2010-09-23 15:232022-02-01 08:08
Reporterplujan 
Assigned ToTriage Platform Base 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusacknowledgedResolutionopen 
PlatformOS5OS Version
Product Versionmain 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0014683: DE015 Module update process changes when a module has expired
DescriptionModule update process changes when a module has expired
Steps To Reproduce1. You have a big list of modules, including Quick Start Spain and a 3rd party module, lets say myOnlyModule from ClosedBravo Inc.
2. You made an agreement with Openbravo for using QuickStart and another one with ClosedBravo for myOnlyModule
3. Both QS and mOM expire. You renew with Openbravo but with ClosedBravo you cannot make a new agreement
4. You are able to disable the module so users are allowed to use the system. However, from now on, if any update of myOnlyModule, updating QuickStart is a nigthmare. You cannot use the Install Updates button anymore but to install the updates in a one-by-one basis.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-09-23 15:23plujanNew Issue
2010-09-23 15:23plujanAssigned To => alostale
2010-09-27 08:59alostaleStatusnew => scheduled
2011-11-18 17:24johnfandlNote Added: 0042994
2012-04-04 12:46alostaleNote Added: 0047384
2012-04-04 12:46alostaleTypedefect => design defect
2017-03-31 14:36alostaleStatusscheduled => acknowledged
2017-04-10 14:34alostaleAssigned Toalostale => platform
2022-02-01 08:08alostaleAssigned Toplatform => Triage Platform Base

Notes
(0042994)
johnfandl   
2011-11-18 17:24   
If myOnlyModule is included in the QuickStart pack, then the system is working as designed. If any dependent component of a pack is disabled, then the integrity of the entire pack is considered compromised--but we let you install those components individually. So, we say "you broke the pack", but you can manage the components individually.

If the myOnlyModule is unrelated to the QuickStart pack in this example, then it sounds like an issue that could be improved at some point.
(0047384)
alostale   
2012-04-04 12:46   
Currently, disabling modules has nothing to do with updates. In fact it is needed to update if possible to maintain module consistency.