View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004860||OXID eShop (all versions)||1.02. Price calculations (discounts, coupons, additional costs etc.)||public||2013-01-17 12:50||2023-11-17 13:37|
|Product Version||4.6.5 revision 49955|
|Target Version||Fixed in Version|
|Summary||0004860: "Shipping Cost Rules" with assigned user groups and "Calculate default Shipping costs when User is not logged in yet"|
|Description||In case you turn "Calculate default Shipping costs when User is not logged in yet" on and then a not logged on user "hits" an Shipping Cost Rule that have assigned Usergroups and than no other one without assigned usergroups, the shipping are "0" eq "false".|
Even if there are more possible Shipping Cost Rules with assigned usergroups the shipping cost will be 0.
|Steps To Reproduce||User Demoshop.|
Assign to all Shipping Cost Rules a group and activate "Calculate default Shipping costs when User is not logged in yet".
Put Something cheap in you basket, go to the basket and you will see Shipping cost = 0 €
1. Each shipping costs rule has assigned user group.
Not logged in user would see 0 as shipping cost in first basket step. He would see matching shipping cost after he enters information about shipping place (in second step).
2. Each shipping cost rules but one has assigned user group. One shipping rule has no user group assigned.
Not logged in user would see amount of not shipping cost which has no user group assigned. This might change when he enters his shipping information.
This looks like correct behaviour as 0 shipping price appears, in basket first step, when no shipping rule match user data. And no shipping rules match not logged in user if all shipping rules require user group information.
||I think if no rules match no shipping costs should be displayed instead of zero, like with "Calculate default Shipping costs when User is not logged in yet" unchecked.|
||We have missing documentation, so for this reason this bug is confirmed|
||I do not see this as an issue. Behaviour is correct. I will confirm the issue so we can add a warning to the documentation.|