Miva Merchant 5 Bugs?

[Julie Wilber]

This thread is for pointing out bugs you might have found using Miva Merchant 5.

Please include as much information as possible, including if it can be duplicated and under what conditions.

Before posting anything, please run a search of the forums to see if something has already been posted.

Thanks!

[ILoveHostasaurus]

The Merchant 5 order export is broken. The following two lines of code need to be added where appropriate to reset the shipping and tax counters for each exported order and that will resolve the issue:

<MvASSIGN NAME = "l.order_tax" VALUE = "">
<MvASSIGN NAME = "l.order_shipping" VALUE = "">

[Scott Gilbert]

Bug or easy fix?

Maintanence mode warning message does not show.

Docs say: "
When you are preparing to close the store for maintenance, select Offline At, and specify the time (in 24-hour time) and date when your store will close.
When you click Update, users will see your warning message right away. When the specified time arrives, the store will go offline, and users will see the maintenance message."

Users do not see message right away. Users see no message until store is offline.

Question: How does one get this message to display on all store pages?

Thanks, Scott

[alexboyer]

The Merchant 5 order export is broken. The following two lines of code need to be added where appropriate to reset the shipping and tax counters for each exported order and that will resolve the issue:

<MvASSIGN NAME = "l.order_tax" VALUE = "">
<MvASSIGN NAME = "l.order_shipping" VALUE = "">

Any word from Miva about fixing this??? It seems like a quick fix if it just needs a variable reset and considering it's currently the only included way of getting customer orders out of Miva, this is pretty important...

[Julie Wilber]

Any word from Miva about fixing this??? It seems like a quick fix if it just needs a variable reset and considering it's currently the only included way of getting customer orders out of Miva, this is pretty important...

Hi Alex,

We watch the forums closely, and Jimmy and I make sure that the right people see the right threads. Beyond that, all I can say is that it is being looked into. We may not always post a response, but I assure you, Mark gets daily emails from me. :D

Thanks!

[Hostasaurus]

Bug: Multiple Upsale Items selected cause Fatal Error on OSEL.

What: MM5, MySQL, VM5.04, all available updates applied. Can reproduce in multiple stores.

Where: On the multiple item Upsale page, check one or more products (error does not occur if no products are selected). Click Continue. OSEL displays:


Error Code: MER-00001
Description: <b>Unknown Error</b><br><br>&nbsp;&nbsp;Action = AUPM<br>&nbsp;&nbsp;Screen = OSEL
Other Information:


Jen

[wcw]

Here's a nasty bug. I just helped a UK store with a checkout issue. When clicking continue on the osel page, the opay page would never show and the system would timeout. They were using shopper selected sales tax and only had one setting, which was None for 0% tax. Here is the kicker. If the products in the basket had NO attribute/options, it was fine. But if the basket item had options, the screen freezes and opay never shows. Apparently there is an infinite loop in the basketoptions totalling routine of this tax module. He has changed to one of the vat tax modules until miva fixes the bug and it is working fine. I am reporting it so it will go on the list for tracking.

The shopper selected sales tax module has an infinite loop when the basket contains options.

[tenquill]

Thanks Bill

I had no idea the attributes were causing my problem, but I originally posted this time-out issue a couple of weeks ago:

http://extranet.miva.com/forums/showthread.php?p=1727

Now it makes sense, sort of ;) There's two attributes my client's customers are required to specify.

Wonder is this can be fixed quickly, or if I need to have my client switch back to the State-based method?

Tim Rains
www.tenquill.com

[wcw]

I am reluctant to just correct miva's code and make it available as I don't think the developer's license allows me to just post it. The actual error line is

<MvASSIGN NAME = "l.bask_opt_pos" VALUE = "{ l.bask_opt_count + 1 }">

It should read

<MvASSIGN NAME = "l.bask_opt_pos" VALUE = "{ l.bask_opt_pos + 1 }">

It should take them 5 minutes to fix it and post. But unfortunately the preparation for a streaming update is not that easy. Maybe Jimmy could get a corrected copy, post it to somewhere at miva.com, then make the official update in a streaming update.

[Martine]

Export orders and attributes
I have defined a few attributes for some products (using an attribute template).
When I export my orders, the attribute field names are exported but not the values entered in the orders! Is this a bug?
I can see the values in the order reports but not if I export the orders.
I need to be able to export these attributes values in a file. How can I do that?

Thanks for your help.

Martine

[Vic - WolfPaw Computers]

Improper linking after login

When a customer logs in from the LOGN screen (as opposed to following the checkout link), after login and Order=0, the customer is incorrectly returned to the SFNT screen in secure mode.

<form method="post" action="&mvt:global:secure_sessionurl;">
<input type="hidden" name="Store_Code" value="&mvte:store:code;">
<input type="hidden" name="Screen" value="SFNT">

Should be:

<form method="post" action="&mvt:global:sessionurl;">
<input type="hidden" name="Store_Code" value="&mvte:store:code;">
<input type="hidden" name="Screen" value="SFNT">

[alexboyer]

Unable to authorize payment: Select failure

Got this error when testing the store. After reading a couple posts in the MM4 and older bugs thread, it seems this is a known issue.

Honestly, I don't care who is blaming who at this point, but it needs to be fixed because it exists in the current MM5.

[sebenza]

State Based Tax Rounding Error

Looks like Tax calculation for State Based Sales tax is not rounding correctly.

The tax is 8.25%. For instance, an order for $19.95, the tax was $1.64, but should have been $1.65 as the calculation should be $1.645875.

[Julie Wilber]

Looks like Tax calculation for State Based Sales tax is not rounding correctly.

The tax is 8.25%. For instance, an order for $19.95, the tax was $1.64, but should have been $1.65 as the calculation should be $1.645875.

Actually, this is working as intended. However, both Mark and I are looking into this and seeing about maybe changing it to more of an arimathical rounding system, like the one most of us learned in school. No promises, but I am doing some research into it.

They tried to tell me that it was called Bankers' Rounding, however, in my time working for a bank, we never used this, instead we did the old fashioned 0-4 and round down, 5-9 and round up.

[Jimmy Cooper]

MIVA Merchant has been using banker's rounding (also known as gaussian rounding) in all version since as long as I can remember. (Well, it's been 5 years at MIVA, so maybe that long...) It was designed to function this way.

"When you add rounded values together, always rounding .5 in the same direction results in a bias that grows with the more numbers you add together. One way to minimize the bias is with banker's rounding."

Banker's rounding means that you round to the nearest even number. So, 1.645 would be 1.64 while 2.255 would be 2.26. There is an explanation on this method here: http://thesaurus.maths.org/mmkb/entr...ryById&id=3064