Here is my story of upgrading.
Joomla 1.7.3, VM1.98M, admin rights, localhost.
I was trying to walk through 1.98M -> 2.0RC3 -> 2.0
Before I started there were 93 tables, 58 of them were of virtuemart.
My actions 1.98 -> 2.0 RC3:
1. Uninstall the vmshipper plugin via the Joomla uninstall menu - success.
2. Delete virtuemart.cfg placed in the administrator/components/com_virtuemart folder - yes.
3. Frontend language and language of products are the same - yes, no action.
4. Start to install 2.0 RC3 from catalog.
The result was:
Info: port Language categories found 18 vm1 entries for migration
Info: port Language manufacturers found 11 vm1 entries for migration
Info: port Language manufacturercategories found 2 vm1 entries for migration
Info: port Language products found 21 vm1 entries for migration
Info: port Language vendors found 1 vm1 entries for migration
Tablename jos_virtuemart_adminmenuentries dropped: 0 altered: 10 added: 0
...
.. (and so on with "successfully installed" in the end)
vmError: TableCustoms COM_VIRTUEMART_STRING_ERROR_NOT_UNIQUE_NAME
vmError:
vmError: TableCustoms COM_VIRTUEMART_STRING_ERROR_NOT_UNIQUE_NAME
Warning: Invalid argument supplied for foreach() in C:\...\com_virtuemart\install\script.virtuemart.php on line 521
The Installation was SUCCESSFUL
By that time there were 102 tables, 67 of them were of virtuemart. New language tables are:
jos_virtuemart_categories_ru_ru
jos_virtuemart_manufacturercategories_ru_ru
jos_virtuemart_manufacturers_ru_ru
jos_virtuemart_paymentmethods_ru_ru
jos_virtuemart_products_ru_ru
jos_virtuemart_shipmentmethods_ru_ru
jos_virtuemart_vendors_ru_ru
All categories, products, orders etc. are visible.
Questions:
1. What does it mean COM_VIRTUEMART_STRING_ERROR_NOT_UNIQUE_NAME?
2. What`s wrong with TableCustoms?
3. Could I upgrade 1.98M -> 2.0 (exclude 2.0RC3)?
So the same error with 1.98M -> 2.0 (vmError: TableCustoms: :bind not executed - or like this, don`t remember)
Could anyone help me with it? Thanks!
Hi!
Does anybody catch that error about customfields? I am disappointed with it, is it serious error? Should I made any change with customfields before updating?
Hi,
Quote1. What does it mean COM_VIRTUEMART_STRING_ERROR_NOT_UNIQUE_NAME?
It means that the field should have a unique name.
Well, thanks! But.. what does it mean? What's wrong with customs and where is that non-unique name?