Bug
Partial module import leaves system in inconsistent state
Issue description
When a module library contains mapping errors and the admin initially does not ignore these, the module is partially imported: the topic map was persisted (though the schema indices doe not show new topics, e.g. topic types), but on the index the new topic type is present.
Developer comments
It is clear that this is unacceptable, since the admin might simply abandon the task and not repeat the import with ignoring mapping errors. The module should either be imported completely or not at all. The problem here is that for the mapping of the code i need the system ids in the target store.
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.