Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Fix unusable shop after activation of a module with migrated metadata (v2) #663
When a module that was previously activated with metadata v1 is activated after its metadata has been migrated to v2, the old extensions are currently not correctly purged from the database.
Due to the way
Additionally, the ModuleChainsGenerator now correctly handles special cases where two modules have extensions to oxconfig and one of them is not available anymore (e.g. because of migrated metadata).
These two bugs together can cause a shop to become unusable when
When these conditions are met, the faulty
The provided OXID function in the "Installed shop modules" tab on the extensions page in the backend, which correctly alerts the admin to the fact that some legacy module extensions are present in the database, results in all module settings (including admin-set values etc.) being deleted from the database, which is not useful in the context of upgrading a module to metadata v2.
The proposed commit fixes both these issues.