Closed sprankhub closed 9 years ago
Is the old version (GroupsCatalog vs. GroupsCatalog2) installed? You can see it in the name of the node in config/modules in the registry file.
The old version (GroupsCatalog) is not installed in the new 1.9 shop. Only the new version (GroupsCatalog2) is installed there.
If the old version is installed, you have to
I wrote the migration tool back when 1.6 was released for a few upgrades I had to do. That was years ago. To be honest, I'm not confident it still works... best to backup and simply try :)
All the migration does is it moves the visibility settings on the products and categories and the config setting sfrom the old storage areas to the new tables.
Okay, thanks. But this can only be done with the migration tool, right? It is not done automatically by the GroupsCatalog2 extension if the old extension is not installed any more?
No, it is not done automatically if the old extension is not installed anymore.
Thanks!
I did the migration with your tool and it runs fine. Afterwards, I still have two entries of type groupscatalog_hide_type
in the DB table eav_attribute
(source model groupscatalog/config_source_hidetypes_product
and groupscatalog/config_source_hidetypes_category
). Because of that, I get an exception when opening a product in the backend. Do you have any information for me how to handle that? Thanks again!
Just removing them should be fine:
DELETE FROM eav_attribute WHERE attribute_code = 'groupscatalog_hide_type';
Thanks for the extension! In an old 1.5 shop, the extension is installed in version 0.4.6. If I update the shop to 1.9, remove all old extension files and add the GroupsCatalog2 extension files, is there anything else I have to do? I read the readme entry but I am still not sure. The tool says "The old GroupsCatalog module was completely removed, migration should be complete". But I fear that it says that just because all the old extension files are gone...?