Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0014683 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| design defect | [Openbravo ERP] A. Platform | minor | have not tried | 2010-09-23 15:23 | 2022-02-01 08:08 | ||||||
| Reporter | plujan | View Status | public | ||||||||
| Assigned To | Triage Platform Base | ||||||||||
| Priority | normal | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | |||||||
| OS | Any | Database | Any | Java version | |||||||
| OS Version | Database version | Ant version | |||||||||
| Product Version | main | SCM revision | |||||||||
| Review Assigned To | |||||||||||
| Web browser | |||||||||||
| Modules | Core | ||||||||||
| Regression level | |||||||||||
| Regression date | |||||||||||
| Regression introduced in release | |||||||||||
| Regression introduced by commit | |||||||||||
| Triggers an Emergency Pack | No | ||||||||||
| Summary | 0014683: DE015 Module update process changes when a module has expired | ||||||||||
| Description | Module update process changes when a module has expired | ||||||||||
| Steps To Reproduce | 1. 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. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0042994) johnfandl (reporter) 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 (manager) 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. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2010-09-23 15:23 | plujan | New Issue | |
| 2010-09-23 15:23 | plujan | Assigned To | => alostale |
| 2010-09-27 08:59 | alostale | Status | new => scheduled |
| 2011-11-18 17:24 | johnfandl | Note Added: 0042994 | |
| 2012-04-04 12:46 | alostale | Note Added: 0047384 | |
| 2012-04-04 12:46 | alostale | Type | defect => design defect |
| 2017-03-31 14:36 | alostale | Status | scheduled => acknowledged |
| 2017-04-10 14:34 | alostale | Assigned To | alostale => platform |
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |