Miva Merchant 10.00.x Bug Reports

[ocpxc02]

I believe I’ve run into a bug involving a product belonging to two collections with each collection being assigned to different price groups. So, the same product is also assigned via collections to both price groups.

Deleting one of the collections is removing the product from both price groups vs. only the price groups associated with the deleted collection.

In looking at the lsk, it appears that the Collection_Delete function is calling Collection_Remove_All_PriceGroup_Products which decrements the collection count for all PriceGroupXProduct records that contain products assigned to the deleted collection. It should be limiting the update to only price groups to which the collection has been assigned.


Paul

[SteveG]

Hi SteveG

i was unable to reproduce what you are seeing. can you provide some more detailed steps to reproduce and a break down of how you have your product, customer, and price group setup?

many thanks
-Eric

Hi Eric,

Sorry for the delay in responding and thanks for looking into this.

The quote has the Quote Exclusion Price Group applied to it, think this is set up automatically and is set up as coupon only. I did try changing it to Exclude For Same Basket and tested again, the item again return to zero pricing.

The customer I use to test has not price groups assigned.

The variant isn't assigned to a price group, however its master product is (20% discount legacy price group)

The price only changes once the customer logs in (I tested checking out without an account, and the quote pricing stayed as quoted)

Module - Basket Price Group Recalc.

Other than that I don't think there much more I can add.

Steps

1. Enter an un-priced product variant into the quote, assigning a quote price of $200,
2. Customer receives and converts quote to a basket
3. Upon logging in the price reverts to the variant products base price, in this case zero

[Eric Foresman]

Managed Quotes and Basket Price Group Recalc.
Been trying this new feature which is great, however the Quotes seemingly can be overridden when a customer logs in, in this instance when the product variant price is zero. The Basket Price Group Recalc is designed to ensure price group members receive their pricing so wonder if that's the issue.

When entering an un priced variant product into the quote, assigning a quote price of $200, it reverts to zero when the customer logs into to pay for it. I experimented by giving the variant a $150 value to see if the price would change in that instance, and yes, same thing, the quote price changed to the variant price. So something seems not quite correct here.

Hi SteveG

i was unable to reproduce what you are seeing. can you provide some more detailed steps to reproduce and a break down of how you have your product, customer, and price group setup?

many thanks
-Eric

[SteveG]

Managed Quotes and Basket Price Group Recalc.
Been trying this new feature which is great, however the Quotes seemingly can be overridden when a customer logs in, in this instance when the product variant price is zero. The Basket Price Group Recalc is designed to ensure price group members receive their pricing so wonder if that's the issue.

When entering an un priced variant product into the quote, assigning a quote price of $200, it reverts to zero when the customer logs into to pay for it. I experimented by giving the variant a $150 value to see if the price would change in that instance, and yes, same thing, the quote price changed to the variant price. So something seems not quite correct here.

[William Davis]

Hi William

i just tried checking out at runtime with address verification turned on and was able to complete checkout both with selecting the "verified" version of the address and the "as entered" option.

do you happen to have the address the customer was using that caused that error?

as far as the first issue goes "1. Three times wrong address was not not flagged, fortunately our fulfillment software caught it."

I'm not sure there is anything we can do about that. if the address is so off that UPS and/or USPS don't return any "verified" versions of it we still allow the order to complete. we do this so that we don't get into a situation where the Customer Can't complete checkout. for that same reason we have the "Use As Entered" option. but because of that, it does allow a customer to enter a bad address and just bypass or skip the address verification.

-Eric

Eric, thank you for your quick reply. I don't recall as that happened some time ago. But I caught your other relating to the same issue, and will give it another go this week and report back here. Thanks again!

[Eric Foresman]

Address Validation Issues

We disabled the feature back in 2022/03 due to the following issues:

1. Three times wrong address was not not flagged, fortunately our fulfillment software caught it.
2. Twice shoppers were not able to place orders.

Refer to post:

Title: Any issues with Address Validation?
Link: https://www.miva.com/forums/forum/on...ion#post720252

Note: Two other merchants on the post disabled the feature due to other problems as well.

I do not believe Miva is aware that there might be an issue with this feature.

Hi William

i just tried checking out at runtime with address verification turned on and was able to complete checkout both with selecting the "verified" version of the address and the "as entered" option.

do you happen to have the address the customer was using that caused that error?

as far as the first issue goes "1. Three times wrong address was not not flagged, fortunately our fulfillment software caught it."

I'm not sure there is anything we can do about that. if the address is so off that UPS and/or USPS don't return any "verified" versions of it we still allow the order to complete. we do this so that we don't get into a situation where the Customer Can't complete checkout. for that same reason we have the "Use As Entered" option. but because of that, it does allow a customer to enter a bad address and just bypass or skip the address verification.

-Eric

[William Davis]

Address Validation Issues

We disabled the feature back in 2022/03 due to the following issues:

1. Three times wrong address was not not flagged, fortunately our fulfillment software caught it.
2. Twice shoppers were not able to place orders.

Refer to post:

Title: Any issues with Address Validation?
Link: https://www.miva.com/forums/forum/on...ion#post720252

Note: Two other merchants on the post disabled the feature due to other problems as well.

I do not believe Miva is aware that there might be an issue with this feature.

[SidFeyDesigns]

OKay, that actually makes a lot of sense. Thank you for sharing that info.

[Eric Foresman]

Possible Customer Password Reset Bug:

The success/information message is being displayed rather than an error message when entering an email that does not exhist in the store for customer accounts.

This is happening on FPWD and the magnific popup form on LOGN (Suivant Theme).

I entered a goofy email "[email protected]" and made sure there is no account using it.

Hi SidFeyDesigns

That is intentional and part of PCI-dss requirement #6.5.5

https://www.pcidssguide.com/pci-dss-requirement-6/


“A common example of improper error handling is user ID and password input. If an attacker receives the message, "incorrect password provided," that error message is telling them they've given a correct user ID. Now, they can focus on hacking the password. The PCI DSS recommends using generic language in your error messages so that no useful information is accidentally given to attackers. Instead of saying "Incorrect password provided," try giving the error message, "Data could not be verified."

Hope this helps

-Eric

[SidFeyDesigns]

Possible Customer Password Reset Bug:

The success/information message is being displayed rather than an error message when entering an email that does not exhist in the store for customer accounts.

This is happening on FPWD and the magnific popup form on LOGN (Suivant Theme).

I entered a goofy email "[email protected]" and made sure there is no account using it.

[heatherwebdev]

No, its up to date

[Eric Foresman]

We're using flat rate shipping methods based on basket subtotal amount, but when a coupon discount is applied, the flat rate option does not show in the shipping selection. Should it be triggering the flat rate option in a lower price tier?
eg,
Option 1 - $0-20
Option 2 - $20.1 - 40

Discount of $5 on a $23 order, should show option 1 instead of option 2, but instead theres no flat rate option

Hi heatherwebdev

i was not able to reproduce that issue in my test store, we did have a bug similar to that which was fixed in 10.04.01, do you happen to be on a version of Miva Merchant older than that?

thanks
-Eric

[heatherwebdev]

We're using flat rate shipping methods based on basket subtotal amount, but when a coupon discount is applied, the flat rate option does not show in the shipping selection. Should it be triggering the flat rate option in a lower price tier?
eg,
Option 1 - $0-20
Option 2 - $20.1 - 40

Discount of $5 on a $23 order, should show option 1 instead of option 2, but instead theres no flat rate option

[Eric Foresman]

Hello Miva.


I'm not sure if this has already been brought up. Ever since the last miva update and UTC time functions were added for page builder, we've noticed price groups keep converting and updating times when saved. Our marketing team was not aware of this (changed price group title several times) and it delayed our sale execution.

Is this feature intentional? Resetting the price group date & time wasn't something we had to worry about before the last update.

Thank you-

Hi Salamader

thanks for the info, i have filed a bug for this issue.

-Eric

[Salamader]

Hello Miva.

https://drive.google.com/file/d/1_mD...vWhP6csrw/view

I'm not sure if this has already been brought up. Ever since the last miva update and UTC time functions were added for page builder, we've noticed price groups keep converting and updating times when saved. Our marketing team was not aware of this (changed price group title several times) and it delayed our sale execution.

Is this feature intentional? Resetting the price group date & time wasn't something we had to worry about before the last update.

Thank you-