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!
Welcome,
Guest
|
|
Hi Reinhold,
FYI: Joomla: 3.6.5 - VM: 3.0.18 - Shipping by Rules Plugin: 6.2.1 I want to give the user information dependent on some condition. In this case, how much more to spend before Free shipping is available. If I enter the rule: Notice="To qualify for FREE {ShopperCategory} shipping you would need to spend <strong>GBP{freeshippingmore}</strong>"; FreeShipping>Amount; However this gives me the following error: Unknown rule type '' encountered for rule 'Notice="To qualify for FREE {ShopperCategory} shipping you would need to spend GBP{freeshippingmore}"; FreeShipping>Amount;' The message is still displayed to the user (as well as error message above): To qualify for FREE Retail shipping you would need to spend GBP42.8 I guess this is because their is no Shipping= at the end of the rule. How can I get round this ? Also how do I display two decimal places for the value of freeshippingmore ? regards Eliot |
|
Dear Eliot,
I'm Aware of this Limitation, and I'm thinking about how to properly implement automatic detection (i.e. if a notice/warning/message is given in a rule the shipping cost should not be a required field. However, in the code this is a little harder to get right). As a workaround for now you can simply append Value=0, e.g. Notice="To qualify...."; FreeShipping>Amount; Value=0 This makes the plugin Interpret this rule like a variable Definition (so no warning will be shown), but as no variable Name is given, the plugin will also not make any variable assignment. The message will still be displayed, of course. Best regards, Reinhold |
|
Hi Reinhold
I tried that however it stops users proceeding through checkout to payment. regards Eliot |
|
Dear Eliot,
Are you using some third-party checkout plugin? With the default checkout of WooCommerce, a notice should not prevent users from checking out. I just cross-checked and with the default settings I'm just fine checking out, even when a message is displayed by the shipping plugin. Do you use some third-party OPC plugin? I know that at least the VP OPC plugin does not allow checking out when any message is displayed (which in my eye is a bug in their OPC plugin...). I have informed the author of that OPC plugin a while ago, so he should be aware, but I haven't heard back whether he has fixed this issue yet. It's probably best if you contact the author of your OPC plugin to fix this, if the OPC plugin is the cause of the problem. Best regards, Reinhold |
|
Hi Reinhold
I'll check with the author. How do I display two decimal places for the value of variables when displayed in notices ? regards Eliot |
|
Dear Eliot,
To dispay variables rounded to two decimals, you'll have to add a custom variable that is rounded to two decimals (i.e. rounded to the nearest multiple of 0.01): Variable=RoundAmount; Value=round(Amount,0.01)
Message="Rounded Amount is {RoundAmount}"; Value=0 You can then use this variable in your messages as shown above. Best regards, Reinhold |
|
Hi Reinhold
If the value is say 27.30 then this gets changed to 27.3 in the message or notice regards Eliot |
|
Dear Eliot,
You are right, there is currently no way to format a number with a fixed number of digits. Rounding makes sure to use at most the desired number of digits, but trailing zeroes will not be shown. I'm not aware of a workaround. Best regards, Reinhold |