Vtiger 7.1 - Migration script force disabling custom modules even when are OK

During a migration from Vtiger 7.0.1 to Vtiger 7 I got the attached warning saying the custom modules are not compatible even if the modules are marked as compatible with version 7.*

@cmaggi this is an expected behavior because the specified modules are not compatible with the new version(7.1).

@satish.dvnk If the module is set to max version 7.* how is not compatible with vtiger 7.1?

Max version should be set in the extension store, not in the local files @cmaggi

@satish.dvnk Max version is in vtiger database. look for vtiger_tab_info table

These are custom modules, no module purchase in the extension store. They are not even publish in there

Thanks @cmaggi for the fast replies, We have rejected those modules from extension store as they are violating the guidelines. While migrating, will perform a check whether installed extension modules are compatible or not.If they are not passed the check we will mark them as failed.

How does the user re-enable them after migration?

User can not enable non-compatible extension because those extension may leads to blank page

What happens if they reupload the zip file? Has to be way to enable a custom module if they have a zip file right?

a. What happens if they reupload the zip file?

It has to be approved from marketplace(extension store) team.

b. Has to be way to enable a custom module if they have a zip file right?

Once it is approved, you can see that extension in your instance extension store page. And there you can see Update button (if the extension already installed)

@cmaggi

Status changed to closed

Version 7.x brings in structural change to module and layout, so pre 7.x modules won't likely work. To provide heads up to user about this before migration check is made against installed custom modules.

Status changed to reopened

Status changed to closed by commit 5ab74733