The core of the e-commerce part of the overall solution. This is an ecommerce shopping cart solution built on top of the DNN (DotNetNuke) CMS. Anyone can do commerce online now!
In some stores that require membership and also in many B2B scenarios, pricing may be something that is desired to be hidden until the website visitor is logged in. In this case, it would be nice to have a configuration option available to specify this. Right now, hiding pricing requires that the custom viewset is updated with Razor code to accomplish this kind of capability.
Describe the solution you'd like
Add a configuration option in the store to allow the store administrator to change when pricing is displayed. The default would be "Always Shown."
In the Role Administration view, there will be a new setting added that mimics the other existing role-based settings already there. This one will be called something like, "Can View Pricing" and default to All Users.
In the out-of-the-box viewsets and the sample viewsets, this role will be exposed to allow pricing to be hidden by designers, which will likely require a new property to be added to the model in the respective controller(s).
Describe alternatives you've considered
Continue to force people to write code to do this? Nah...
Is your feature request related to a problem?
In some stores that require membership and also in many B2B scenarios, pricing may be something that is desired to be hidden until the website visitor is logged in. In this case, it would be nice to have a configuration option available to specify this. Right now, hiding pricing requires that the custom viewset is updated with Razor code to accomplish this kind of capability.
Describe the solution you'd like
Add a configuration option in the store to allow the store administrator to change when pricing is displayed. The default would be "Always Shown."
In the Role Administration view, there will be a new setting added that mimics the other existing role-based settings already there. This one will be called something like, "Can View Pricing" and default to All Users.
In the out-of-the-box viewsets and the sample viewsets, this role will be exposed to allow pricing to be hidden by designers, which will likely require a new property to be added to the model in the respective controller(s).
Describe alternatives you've considered
Continue to force people to write code to do this? Nah...
Additional context
Hotcakes Cloud Support Request 5741