Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0010214 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] A. Platform | major | always | 2009-08-07 14:56 | 2009-10-07 00:00 | |||
| Reporter | vmromanos | View Status | public | |||||
| Assigned To | alostale | |||||||
| Priority | normal | Resolution | no change required | Fixed in Version | ||||
| Status | closed | Fix in branch | pi | Fixed in SCM revision | ||||
| Projection | none | ETA | none | Target Version | pi | |||
| OS | Linux 32 bit | Database | PostgreSQL | Java version | 1.6 | |||
| OS Version | Ubuntu 8.04 | Database version | 8.3.7 | Ant version | 1.7.0 | |||
| Product Version | pi | 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 | 0010214: IsRegistered column of AD_MODULE table is not exported | |||||||
| Description | The IsRegistered column of the AD_MODULE table is not exported, but it should be because it is necessary to keep this value always updated. Imagine that you register the module, you export your database and you run an install.source. The module will appear as not register, although it is registered in the central repository. This can make the developer to become crazy, specially if he doesn't remember if he registered the module or not. | |||||||
| Steps To Reproduce | 1- Create a module and register it. AD_MODULE.IsRegistered should change to 'Y' 2- Export database. Open the module's AD_MODULE.xml file and check the IsRegistered column is not exported 3- Run an install.source 4- Check the module appears as not registered | |||||||
| Proposed Solution | Export the IsRegistered column | |||||||
| Tags | Modularity | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0019316) rafaroda (developer) 2009-08-31 10:05 |
Asier, Can you please comment on this issue? Thanks. |
|
(0020780) alostale (manager) 2009-10-06 12:43 |
This information is not part of the module but of the instance that contains this module (just like is in development check) that's why it is not exported. Furthermore, now in pi when the module is registered the register button is still present, it only disappears when the module is not in development, allowing in this way to re-register a module to change some of its initial values (package...) |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-08-07 14:56 | vmromanos | New Issue | |
| 2009-08-07 14:56 | vmromanos | Assigned To | => rafaroda |
| 2009-08-31 10:05 | rafaroda | Note Added: 0019316 | |
| 2009-08-31 10:05 | rafaroda | Assigned To | rafaroda => alostale |
| 2009-08-31 10:05 | rafaroda | Status | new => acknowledged |
| 2009-08-31 10:05 | rafaroda | Tag Attached: Modularity | |
| 2009-10-06 12:40 | alostale | Status | acknowledged => scheduled |
| 2009-10-06 12:40 | alostale | fix_in_branch | => pi |
| 2009-10-06 12:43 | alostale | Status | scheduled => closed |
| 2009-10-06 12:43 | alostale | Note Added: 0020780 | |
| 2009-10-06 12:43 | alostale | Resolution | open => no change required |
| 2009-10-07 00:00 | anonymous | sf_bug_id | 0 => 2873746 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |