For updaters: please delete your virtuemart.cfg in /administrators/components/com_virtuemart and
store your vm config one timeWe would like to directly do the final release, but we need more help with testing. Looking back, the M version was already like a final except some small bugs, which we were able to fix within 5 minutes.
So when enough people join the tests here in the forum, we could do the final release next wednesday (assuming we find only 5 minute bugs).
The new version is changing the db layout dramatically, the format how some data is stored is also changed, so the upgrade process is a bit nasty. Vm2 is now always multilanguage, that means, even when you use only one language, vm2 is using speshitpilled tables to store translatable data. Therefore it is
very important before you update to check that your default joomla frontend language is the same as you use in the description of your products. So when you used atm english in your store, but it should be a spain shop than it is important that you change the joomla frontend language to spain before the upgrade.
The updater is also checking every table definition and updating it. The updater is even merging a table. So the upgrade process is quite database intensiv. We tested it of course also with more than just the sampeldata. When there are already a lot products in the store, you should disable the joomla debug, the akeeba enhanced installer and maybe even the vm debugger. Other case it can happen, that you just see a blank page.
It also always good to rise the max_execution time and the memory_limit to prevent that the script stops.
Be aware that the migrator is not updating already done payments or simular, please contact the team in this case.
http://dev.virtuemart.net/attachments/download/369/com_virtuemart2.0.0_RC3_extract_first.zipREMEMBER to install both,
CORE and
AIO!
Also Consider that the update button is now falsly showing that there is a new update available ( in fact you would downgrade). The reason for this is that it is an unofficial release.
Fixed in h:
Pagination fix, when coming from page higher than choosen category
some little typos in shipment/payment plugins
various other small fixes
payment plugins can now handle other currency than shop currency
Fixed in g
- error storing all kind of addresses
- better search support
- order date fix
- language key for router file (you may go in your config and store it one time to apply the correct orderby and search fields
- found some errors in the updater
- various others described the last days here.
- removed stockable customfield plugin
- added specification customfield plugin
Fixed in f
bug creating new product,
some various others
Fixed in e version
not storing of payment/shipment params in j1.7
various small installer bugs
...
Fixed in b version
- aio is deleting now existing files before move, so the updating should work as before
- slug generation adjusted to language tables and checking when the slug is found, if it is from the own identity or another
Fixed in the a version:
- fixed broken calculation rules.
- small typos
General new features and bigger fixes of the N regarding RC3:
- multilanguage system
- enhanced pluginsystem
- found sever security bug (XSS) and fixed.
- joomla cache
- optimisation of queries
- optimisation of tables