MMUI to CSSUI conversion tool error

[lesliekirk]

I do have a ticket open for this but I'm wondering if any one else who has used the MMUI to CSSUI conversion tool has encounter this error:

May 27 2016 10:06:09 MER-WIZ-MMUI2CSSUI-00031 There are items that have
extensions that reference non-existent modules. Address this issue, and
restart this migration utility. The list of affected item codes is:
product_list



Errors. Please address the above issues and restart the migration.

Isn't product_list a default MMUI module?

[ids]

I am pretty sure this component item, product_list, has another component item assigned to it as an item extension. If that's the case, that item extension needs to be unassigned. I think it's possible that the module itself may have been removed but the assignment still exists. I don't know if it's a bug with Miva or in the assigned component module.

[lesliekirk]

I am pretty sure this component item, product_list, has another component item assigned to it as an item extension. If that's the case, that item extension needs to be unassigned. I think it's possible that the module itself may have been removed but the assignment still exists. I don't know if it's a bug with Miva or in the assigned component module.

The question is - what module needs to be removed? How would I figure out what item extension to remove? Are you suspecting something third party that isn't playing nicely with the conversion tool?

[ids]

If what I described is the issue, then I am not sure you need to know what module it is. If you drill down the Item -- Extensions screen you'll see the list of assigned modules as an extension to the item. You would unassign in that screen.

More info: what I have discovered is that when a module is uninstalled from the store, it appears MM properly removes any components from that module assigned to items . I have not tested removing the module before uninstalling it from the store. That scenario IMO is not easy to do

I don't think any of this excludes any 3rd party module from playing nice in this scenario.

Scott

[lesliekirk]

So let's back up a bit. The Item that is causing this error - product_list - is the MMUI Product List and it looks to be assigned to the PLST page. So I'm not sure it should be unassigned.

[ids]

Maybe I've misunderstood something. The error message mentions this:

"There are items that have extensions that reference non-existent modules."

For me, this means item extensions which is different than Items assigned to a page.

When you drill into the product_list item, are there any modules assigned in the Extensions tab?

Side Note: Item extensions aren't used very much I have found. But, it's a really powerful feature. For example: If I have a module that is assign to the basket item, the component initialize feature will be applied to the basket item everywhere it's assigned.

[lesliekirk]

I think I know what you need me to check. I should compare the product_list Item in this store, to a product_list Item in a store that hasn't barked at me like this one has.