Miva Merchant 10.00.x Bug Reports

[habreu]

Atrribute export to XML

I have to edit add-on pricing in the options of several products. I looked on the forums and found a thread suggesting to export as XML with 'Replace All Mode' (I also tried 'Add Mode') but Excel chokes with the following error. I also don't see a way to later import Attributes (maybe the variants?). In any case this could use a fix and some clarity as regard the import export process - don't want to inadvertantly screw up a large amount of options across multiple products.

xmlerror.jpg

[netblazon]

When importing variants using Add/Update Product Variants from CSV and the spreadsheet described at https://docs.miva.com/reference-guide/import-settings, the "Track Inventory" column at the attribute level does not get turned on if the attribute already exists. However, if I delete the attribute and then import, it does.

Import File Header: TRACK_PRODUCT_INVENTORY

Import File Value: Yes

File: mmlsk-variantimport.mv

Function: Update_Attribute

Problem: It does not set the inventory member, although Create_Attribute does.

*** On further review, this may be as designed. If so, the sample spreadsheet probably should not have "TRACK_PRODUCT_INVENTORY" filled in with "Yes" on the attribute and variant rows as I think that's where my confusion came from. Also, if this is as designed, then how would one import variants for attributes that already exist? The only way I can see is for me to go to every product and put a check in the "I" column, manually, which pretty much defeats the purpose of being able to UPDATE variants. Also, it actually creates the variants even if the attribute inventory is not checked, but the admin display for those variants is incorrect. I don't have MySQL access to this store to check the data.

[Brennan]

Hi Colin -

In your use case, when you push code from dev to live, are the feed templates changing or staying the same. Why do the feeds been to be visited, or do you mean the feed just needs to be re-generated?

[dreamingdigital]

Feeds : they are "branched" but the production branch is the only template that runs. Ok, that works BUT when you make your dev branch live then all your feed templates need to be visited and the templates from the previous production branch need to be applied to the dev, now live, branch. Ugg.... That's not really fun. I'm not sure a real solution here other than having branched versions of the feed templates when only possible to run the production one should either add functionality to run whatever branch you want - or not have the feed templates branched.

We have had a few instances of this already and a big one today. It's important to address.

[lesliekirk]

Caching issue tangent - could this also be affecting the admin login screen? I have a store owner that I have had to unlock and reset her password 2-3 times a day since updating her site to MM10.

[Rick Wilson]

It's a caching issue.

[lesliekirk]

Not sure if anyone else has encountered this - we have done 11 updates to Miva 10 and had the same issue only on two stores. We installed the main 10 update. The store still shows updates are available but instead of showing the 10.1 - 10.4 bug fix updates it is still showing the 10.0 update available and if you hit continue the window just pops up again. It appears the main update has not installed properly as admin has changed only partly to the new layout and still stays: Miva Merchant 9.14.00. I have a ticket in but was wondering if anyone else has seen this? We are trying to get this done today.

Ditto

[Leanne]

Yes, I had this problem. It was a caching issue. Try clearing your cache or using another browser.

[afiumano]

Not sure if anyone else has encountered this - we have done 11 updates to Miva 10 and had the same issue only on two stores. We installed the main 10 update. The store still shows updates are available but instead of showing the 10.1 - 10.4 bug fix updates it is still showing the 10.0 update available and if you hit continue the window just pops up again. It appears the main update has not installed properly as admin has changed only partly to the new layout and still stays: Miva Merchant 9.14.00. I have a ticket in but was wondering if anyone else has seen this? We are trying to get this done today.

[habreu]

Error/Sendlane/Basket/Duplicate Entry/Caching?

I'm not sure if this is related to the Sendlane module or a Miva 10 issue so am posting it here. I have tested this in Chrome and FireFox latest versions.

If I log in and put an item in the cart and complete a sale, then logout and go back within a few minutes to order something else with same account I get this

Runtime error in merchant2/5.00/modules/system/sendlane.mvc @ [0000002b:0000021c]: lib/EMS_Resource.mv: Line 25: MvQUERY: mysql_execute: Duplicate entry '71c47f77420bb5f1f2d6e9d895ae101d' for key 's01_Baskets_1'

I assume that something is not being flushed correctly -or maybe it gets flushed after a longer period of time- but right now I have to delete the browser cache to be able to use the site after this happens as the error prevents the page from loading completely.

[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