[Updated] Release 2.0.18c

[Milbo]

Changes from 2.0.16c -d
- added cdata for javascript
- synchronising media got new break
- installation script, set max limit to 140 only if set lower already
- fixed that canonical cat is always a published one
- fixed problem with pagination, using manufacturer id as filter in category view
- prevent overwrite of child products if non price is set, if the parent is stored with more than one price
- opening a product, with a zero price is not anylonger storing the price as 0.0

Changes from 2.0.16d - 2.0.18a
- Front end editing : Adding Joomla text filtering when saving product description
- allow simple html for vendors
- Added default values to prevent error in registry.php
- breadcrumbs are more robust
- fixed category bulk, missing shopfunctionsf.php
- fixed canonical links

Changes from 2.0.18a - 2.0.18b (14. February)
- small fix in BE/tmpl/order.php, should show now first_name . last_name
- set the filter for customplugin data for the cart less strict
- added calculation per category for rules per cart
- added correct reducing of tax when a discount is used and different vattaxes are used for the products (thanks to Maik Künnemann)
- custom prices in dropdown applied all vattaxes in the list, should be fixed
- fixed ordering BE product list (thanks to David jardin)
- added if isset check in shoppergoup model to prevent notice
- Email subject price displayed in the correct currency
- Fixed displayed several times payment/shipment methods when a shopper is in several shopper group-
- fix in convertDimensionUnits
- fixed the doubled & in pagination routing
- stocklevel for stockindicator is now $product->product_in_stock - $product->product_ordered;
- moved TOS to top of check in cart.
- unpublished related products are not creating an empty div anylonger.
- vmtables, added a table fixer for the userfields (checking in modifytable if the column is actually there)
- Fixed an error which let rules count as vaild without customer input.
- added that shipment and tax, use generic rule, if only one product vat is used
- added step_order_level by Székely Dénes (thank you)
- added small function in the config view, which is testing if the vendorId of the storeowner is correctly set
- Added cancelTax to avalara
- added vmcalculation to trigger in order for avalara
- small adjustments to avalara userfields
- avatax,  country validation configuration
- avatax,  tax type with categories (prefix avatax-)

Changes from 2.0.18b - 2.0.18c (1. March)
- fix by kkmediaproduction (Maik Künnemann) and Max for cart rules per category.
- added ordering for child products
- added manufacturer for rules per product, thanks to <mediaDESIGN> St.Kraft, but wont work for rules per bill despite the categories
- RSS feed for homepage and category
- Fix for bug, that an admin changing address of a user could lost its own address, if the user was not a vm user already
- taxes for shipment selection view.html.php
- fix for email (thanks stan)
- exchanged calculateSalesPrice against setCartPrices (proxy function for legacy still there)
- fix, step_order_level by Székely Dénes was not working with old overwrites, compatibility enhanced
- removed non working cloning function of the prices
- fixed category sharing
- little fix in router, for standard listing
- new option for avalara, option to disable taxes if it is not the cart.
- avalara caching
- avalara added purchase order number,

Changes from 2.0.18c - 2.0.20a (13. March)
- added unified way of tcpdf , thanks Reinhold Kainhofer
- updated tcpdf
- removed fixed width in emails
- small fix for router, if used in 3rd party
- fix for unknown mathop
- For 2.0.20 added change of #__virtuemart_medias' 'file_params' to prevent notice doing update.
- Added min_order_level in default_addtocart.php to the quantity input box
- RSS feed topten
- fix to store the category depended results in the order
- Multilingual images (different images for each language)
- fixed setStoreOwner function (you can actually fix your store now with it)
- small Klarna fix (link corrected)
- Heidelpay, added missing arguement
- Country name libya changed to 'Libyan Arab Jamahiriya' and a few typos in language files
- added use vendor email address to the shopconfig, so you can activate the stan fix or not
- jquery.validationEngine-xx.js loaded by language
- increased size of userfield names to avoid problems with tooo long language keys
- fixed the problem that childs using price of parent had no prices in the cart
- added cache for getVendorCurrency function
- fixed displayed currency in orderslist. Now using the currency of the order
- moneybookers small fixes
- Added checks if invoice folder is writeable

http://dev.virtuemart.net/projects/virtuemart/files

[lipes]

Hallo! i've did the update from 2.0.18 a to b

and in the first file (com_virtuemart.2.0.18b.zip) give me this error:
vmError: alterTable CHANGE nl94_virtuemart_medias.file_url_thumb :

PS: another litle problem that i've detect is that in the VM Product module if we work with the default CSS and set "NO" in the option "Show Add-to-cart Link?" the products  will appear in column and not in row. If enabled the add to cart link the products will appear in row...

Some prevision about the VM 2.1 release date ?
Will be possible to VM dev team give a "new life" to VM product module... with multiple category selection in 2.1 (with using the category filter option)?

[r_ekkie]

and in the first file (com_virtuemart.2.0.18b.zip) give me this error:
vmError: alterTable CHANGE nl94_virtuemart_medias.file_url_thumb :

Same problem over here

[BaidareW]

vmError: alterTable CHANGE yy5qv_virtuemart_medias.file_url_thumb :

Is this means something ?

[Milbo]

Is not a big thing, the table stays then as it was before, which is also okey. I just increased the length of the url.

new version is up, two small notices fixed.

[lindapowers]

We had the same warning but testing the site works perfectly and we have not noticed any serious bug, actually we have not noticed any bug yet.

Great work although we are still completely pissed by the checkout but we still hope you look in to it for the future, at least the TOS are moved to their logic place.

Looking forward for the 2.1 version.

[rodfarrell]

Does this solve the vat tax calculations when shopper groups have different rates?

[Milbo]

When shoppergroups have different rates? This should work since a long time. But the upcoming version has a calculator which can now use different rules per category. in the 2.0.18b the fix is not working :-(

[rodfarrell]

No, it doesn't work at all and may require me to scrap the whole site and start again with other software as it is a core requirement for my client.

The only way to have different tax rates for different shopper groups appears to be to assign one vattax to a usergroup and then assign a billtax for another group.  If you have two vattax rates everyone is charged the higher rate.  I don't know what you would do if you need three tax rates.

[Milbo]

I am quite sure you do not use it correct. We use this construction ourself since August in our own shop, so ....

[Milbo]

Sorry guys, I forgot a file, new version is uploaded.

[lindapowers]

Still dont understand how updates work here, if 2.0.18b and 2.018c are marked as stable why is my system telling me:

A new version is available
Installed version 2.0.18b
Latest version 2.0.18a

I never know what is the latest official release.

Edit, read your reply here http://forum.virtuemart.net/index.php?topic=113103.0;topicseen

[BaidareW]

Hello,

 updated from 2.0.18b to 18c and got this message on checkout :
 "Info: Unrecognised mathop  in calculation rule found, seems you created this rule with plugin not longer accesible (deactivated, uninstalled?)"

 Using istraxx quantity plugin and OPC module.

[Milbo]

Almost impossible. I mean, I have no clue how this message is connected to the update

[Nils]

We also updated from 2.0.18b to 18c and got this message on checkout :
 "Info: Unrecognised mathop  in calculation rule found, seems you created this rule with plugin not longer accesible (deactivated, uninstalled?)"

So, clearly this has something to do with the 2.0.18c version