Miva Merchant 10.00.x Bug Reports

[Eric Foresman]

Rounding error

This is the second time billing has mentioned an incident like this. They did modify the order via the admin to add a coupon using the ADD/REMOVE COUPONS so I am not sure if that was the cause or it is something else.

There seems to be a difference between how the line item discount calculations and the subtotal discounts are calculated.

Line item shows we have 12 units that each get a 16 cent volume discount. The total volume discount is 1.92. Miva shows that as 1.94 at the end of the invoice.

If we do the math the actual cost per unit is 5.2283 after the volume discount of 3% is applied. If you multiply that in Miva x 12 you get 62.7396 which Miva rounds to 62.74 which seems to be the line item calculation. But if you round 5.2283 first to 5.23 then multiple by 12 you get 62.76 which is the number in the subtotal area. 2 cent discrepancy.


rounding-error.jpg

Hi habreu

We have a bug on that issue and the fix is already in testing.

Hope this helps
-Eric

[habreu]

Rounding error

This is the second time billing has mentioned an incident like this. They did modify the order via the admin to add a coupon using the ADD/REMOVE COUPONS so I am not sure if that was the cause or it is something else.

There seems to be a difference between how the line item discount calculations and the subtotal discounts are calculated.

Line item shows we have 12 units that each get a 16 cent volume discount. The total volume discount is 1.92. Miva shows that as 1.94 at the end of the invoice.

If we do the math the actual cost per unit is 5.2283 after the volume discount of 3% is applied. If you multiply that in Miva x 12 you get 62.7396 which Miva rounds to 62.74 which seems to be the line item calculation. But if you round 5.2283 first to 5.23 then multiple by 12 you get 62.76 which is the number in the subtotal area. 2 cent discrepancy.


rounding-error.jpg

[Eric Foresman]

Let me know if you need more info for this, but if I create a javascript resource in a branch with name 'abc', I can't create a javascript resource with that same name in Production. I believe this issue popped up when I went to merge a bunch of changesets to production that included creating the new javascript resource, which the merge wasn't able to do (and thus the end result was all messed up).

Hi new_user2018

I'm not able to reproduce this. If I create a JavaScript resource in my “testing” branch, when I switch to the Production Branch it already exists.

If possible can you open a service ticket so that support can take a look at your store?

Thanks
-Eric

[new_user2018]

Let me know if you need more info for this, but if I create a javascript resource in a branch with name 'abc', I can't create a javascript resource with that same name in Production. I believe this issue popped up when I went to merge a bunch of changesets to production that included creating the new javascript resource, which the merge wasn't able to do (and thus the end result was all messed up).

[Eric Foresman]

Hi Psydde


I have reproduced this and field a bug for it. thanks for letting us know about this issue.

-Eric

[delcorsets]

Order Processing > Order Detail Screen > Order History

This will open a modal window with the customer's order history, but clicking on the order link does not do anything - you are not taken to the selected order as expected.

Screen Shot 2020-11-28 at 7.33.17 AM.png

[habreu]

prodold.jpg
Version 9 PROD


prodnew.jpg
Version 10 PROD

Okay so I dragged all the resizers for my SFNT page in version 10 dev store and the new width is saved but when I got to the PROD page I have to do the same (and I assume every other page). I looked at version 9 PROD page and it fills the screen correctly but you don't have the left menu that is in version 10 so it fits fine. I guess it copied over the page widths from the old version 9 store. It might be good to be able to have a 'reset all page widths' if that's the cause or you may need to account for the extra width on the left in red when setting the width? Hope that made sense.

[Brennan]

Thanks, I filed a bug to correct the Alt text.

For the update button being hidden, do you have any of your text areas expanded to be wider than default? That is a common case we see. We currently save the settings anytime you expand a text area so next time you visit the page it loads those same settings. We have a bug filed to remove this since we now have full screen mode. Bringing your text areas back to normal should bring the update button back in to view, without having to scroll right to see it.

[habreu]

Testing 10 on a dev site.

Minor bits:

report1.jpg

Guess it should say 'manage tags'

and

report2.jpg

I am using a 32" monitor set to 1920 x 1080 and by default when I look at the code sections the window extends well beyond the edge of the screen which pushes the update button offscreen as well.

[Kent Multer]

Kent Multer are you also experiencing a runtime error when trying to add available modules?

I've created a post here that describes when the error comes up.

https://www.miva.com/forums/forum/on...ilable-modules

Hi Sid, No, I haven't seen that problem. But I haven't done much work in v10 stores yet. I'm subscribed to that other thread, so I'll see any new info that comes up there; and I'll post if I see the problem in any of my clients' stores.

[SidFeyDesigns]

Another thing I have noticed when upgrading to v10.

Prior to the upgrade the deferred baskets setting seemed to be doing its job as over the course of a week there would only be a couple hundred baskets created.

Since the update that number jumped to over 16,000 baskets in a week, most of which were empty.

I was thinking it may be a bug since the review baskets tool received a huge update.

[SidFeyDesigns]

Kent Multer are you also experiencing a runtime error when trying to add available modules?

I've created a post here that describes when the error comes up.

https://www.miva.com/forums/forum/on...ilable-modules

[Kent Multer]

CORRECTION: the problem seems to be worse than I thought at first. I'm looking at a store that was just upgraded to v10, and it seemed that the custom tax module I wrote for them was not accepted for the upgrade. On the Modules page, I can't find it at all. Typing in the first part of the module name doesn't cause it to show up.

The Type menu doesn't even include "Tax" as one of the options. The only types in the menu are Shipping, Payment, Fulfillment, Utility, System Ex, and Logging. What happened to all the others?

When I looked at Store Settings, I found that my module actually is in the store, and it's selected as the current tax module. So that part, at least, is OK. But it's weird that I can't find it on the Modules page.

[Kent Multer]

I just found a bug on the Modules page. When you type text in the Search box, the store only searches the module name. It doesn't search for a match in the module code, vendor, or other fields.

This is a significant inconvenience for me. I've written a lot of modules in the last 18 years, and many of my clients use more than one. All my module have codes that start with "MAGIC_." When I log into a store to do some work, I often start by doing a quick check to see which of my modules the store is using. I used to be able to do this by just typing MAGIC_ in the Search box. That doesn't work any more. I have to either scroll through the entire list of modules, or type in module names one at a time to find out if they're installed.

Thanks --

[Rick Wilson]

Q1 is my guess