nopCommerce 3.80 roadmap and estimated release date. Let's discuss

PayPal Merchant SDK for .NET
This Classic SDK is not actively supported and will be deprecated in the future.
Official source: https://github.com/paypal/merchant-sdk-dotnet

So it will be better if we start using PayPal .NET SDK. for Paypal Direct Payment plugin.
They have proper documentation also.
https://devtools-paypal.com/guide/pay_creditcard/dotnet?interactive=ON&env=sandbox
https://developer.paypal.com/docs/api/

anik1991 wrote:
Thanks! Please find this work item here

I have a suggestion for Acl.
I have created a role.
They can access Admin area. Manage Affiliates,Admin area. Manage Attributes,Admin area. Manage Blog
If I don't check Access admin area. The role can not found any link to go to that page.
So it will be better when some one click some admin area roles then Access admin area set automatically checked true.

I have another suggestion for Sitemap node.
It will be better if we set display order in sitemap Node and display menu list according to that display order in admin area.

I have few sugestion.


1. About "out of stock" products. I was thinking about this problem, and maybe I inventented "easy"? way to marking "out of stock" products on list products.

Maybe you can add "checkbox" like Specification, or "free delivery" or something similiar, where we can mark when we know this product should be not available 1-2 month or longer time, but we don't want unpublish.

Solution:
1. When this checkbox is "checked" in product detail. on list of products we have information "out of stock" (instead buy button) or "send email when available".
a) Nop Partners can create filter "Show only available" - then products unavailable  can be filtered (like products with specifications).
or
b) Products with "checked out of stock - checkbox" are moving to last pagination page.
c) we can also add automatic solution when we have "warehouse" to actually options "When quantity products is less than .... then check "disable buy button and mark out of stock checkbox" or only "mark out of stock checkbox" (sorry I don't think how name it).

2. Information about new delivery on product page. If we know our product be available 30 January or February (few weeks). We can use "Calendar" and put this information. Then where client is on our product page, then see info "Next delivery 30 February", and he don't need to call to us, etc.  

I hope you can understand me ;

And last one.
3. Back in stock subscription to the not registered client. Is this possible?;)

Zyje_sobie wrote:Can't you use

Available start date:  

Available end date:

Hi Andrei!  Nice list of features! I'm looking forward to them.

I haven't seen discussion on meeting the latest PCI DSS 3.1 requirements.  I've looked in the 3.7 version and these do not look to be implemented there.  So, I'm interested in if these features are on your roadmap so that the PCI DSS 3.1 requirements below are covered in nopCommerce.

Here are the items in particular:

Requirement 8.1.7: Password attempt failure Lock-out set to 30 minutes minimum. (may be a admin configured setting)
Requirement 8.2.4: Passwords must be forced to change at least once every 90 days
Requirement 8.2.5: Do not allow an individual to submit a new password that is the same as any of the last four passwords used.
Requirement 10.1: Implement audit trails to link all access to system components to each individual user.
Requirement 10.2: Implement automated audit trails for all system components to reconstruct the following events:
Requirement 10.2.1: All individual accesses to cardholder data
Requirement 10.2.2: All actions taken by any individual with root or administrative priveleges
Requirement 10.2.3: Access to all audit trails
Requirement 10.2.4: Invalid logical access attempts
Requirement 10.2.5: Use of and changes to identification and authentication mechanisms including:
- creation of new accounts
- elevation of privileges
- changes, additions, or deletions to accounts with root or administrative privileges
Requirement 10.2.6: Initialization, stopping, or pausing of audit logs
Requirement 10.2.7: Creation and deletion of system level objects (db tables, stored procs, etc)
Requirement 10.7: Retain audit trail history for at least one year with 3 months minimum available for analysis.

Andrei, it would be good, if more widget zones will be set on admin panel (administration pages, like order, catalog, etc). Very ofen some extra customization is required, and ready widget zone will not require modification at code on customer files.

dmadison wrote:
Thanks a lot! Please find this work item here