Login
Register

VirtueMart

WooCommerce

Others

Docs

Support

Blog

About

Shipping by Rules for VirtueMart

Open ToolsOpenTools LogoText 100px 

IMPORTANT ANNOUNCEMENT: Plugin development ceased, all plugins made available freely (GPL)

With great sadness we have to announce that we are ceasing development of all our VirtueMart, WooCommerce and Joomla plugins. Effective immediately, all our plugins -- even those that were paid downloads -- are made available for free from our homepage (GPL license still applies), but we cannot and will not provide any support anymore.

It has been a great pleasure to be part of the thriving development communities of VirtueMart as well as WooCommerce. However, during the last year it became painstakingly clear that in addition to a full-time job, a young family and several other time-consuming hobbies at professional level (like being a professional singer) the plugin development and the support that it requires is not sustainable and is taking its toll. It has been an honor, but it is now time to say good bye!

×

Notice

The forum is in read only mode.
Welcome, Guest
Username: Password: Remember me
Forgot your password? Forgot your username?
  • Page:
  • 1

TOPIC:

Error in VMshipment rules template 07 Feb 2017 07:00 #1

  • Mclernons
  • Mclernons's Avatar Topic Author
Joomla 3.6.5
Virtuemart 3.19.3
Warning: Missing argument 5 for plgVmShipmentRulesYOUR_PLUGIN_NAME::onVmShippingRulesGetCartValues() in /home/officeasy/public_html/plugins/vmshipmentrules/YOUR_PLUGIN_NAME/YOUR_PLUGIN_NAME.php on line 45


function onVmShippingRulesGetCartValues(&$cartvals, $cart, $products, $method, $cart_prices) {

Delete $cart_prices and the error goes away. So has a security update to joomla or virtuemart broken this?

Error in VMshipment rules template 07 Feb 2017 11:17 #2

Dear McLernons,
Thanks for pointing this out. The $cart_prices Argument was removed a year ago (Version 6.0 of the plugin) from the call in our plugin, as it does not work with the evaluate_for_categories etc. functions. Apparently the plugin template was not updated correspondingly. Simply removing it from the function signature (as you do) is the proper fix.

Best regards,
Reinhold
  • Page:
  • 1