Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0010214Openbravo ERPA. Platformpublic2009-08-07 14:562009-10-07 00:00
vmromanos 
alostale 
normalmajoralways
closedno change required 
20Ubuntu 8.04
pi 
pi 
Core
No
0010214: IsRegistered column of AD_MODULE table is not exported
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.
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
Export the IsRegistered column
Modularity
Issue History
2009-08-07 14:56vmromanosNew Issue
2009-08-07 14:56vmromanosAssigned To => rafaroda
2009-08-31 10:05rafarodaNote Added: 0019316
2009-08-31 10:05rafarodaAssigned Torafaroda => alostale
2009-08-31 10:05rafarodaStatusnew => acknowledged
2009-08-31 10:05rafarodaTag Attached: Modularity
2009-10-06 12:40alostaleStatusacknowledged => scheduled
2009-10-06 12:40alostalefix_in_branch => pi
2009-10-06 12:43alostaleStatusscheduled => closed
2009-10-06 12:43alostaleNote Added: 0020780
2009-10-06 12:43alostaleResolutionopen => no change required
2009-10-07 00:00anonymoussf_bug_id0 => 2873746

Notes
(0019316)
rafaroda   
2009-08-31 10:05   
Asier,

Can you please comment on this issue?

Thanks.
(0020780)
alostale   
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...)