We've prepared the roadmap of the next version of nopCommerce (4.00). The main and most exciting change is moving to ASP.NET Core! Yes, we're finally ready to do it!
I won't list all highlight/enterprise features here as we always did it before. But just because there are really a lot of them. Find them here
Please also find a complete list of all existing work items for this version here.
Your thoughts and suggestions are more than welcome!
Estimate release time - October-November 2017 (7-8 months)
External login should be improved, using Owin Identity. I guess it should be part of Nop and not a plugin
60% of our customers are Facebook login
Owin is part of visual studio projects and very easy to use, simple to set up. already built a plugin using Owin and integration with Nop login system, however the web.config need to be changed.
Great News!!!! Thanks for planing to move ASP.NET Core! Feeling excited!!!
I have suggestion for Login/Registration process in nopcommerce. Registration/Login will be done by Email or Phone as like Facebook.
It would very better I think. In the case of Fackbook Only Email is not mandatory now, either email or phone is mandatory for Facbook. Now Mobile phone is highly use than email.
External login should be improved, using Owin Identity. I guess it should be part of Nop and not a plugin
60% of our customers are Facebook login
Owin is part of visual studio projects and very easy to use, simple to set up. already built a plugin using Owin and integration with Nop login system, however the web.config need to be changed.
thanks
hezy
OWIN is working already, and OAuth2 and OpenId Connect is easy to configure and I havn't had to change the web.config - @HeyZ do you have any more information regarding that change?, there are other identity providers that are not facebook, the plugin is needed to integrate the account information you would share with the authenticator, OWIN is fully working already - you can login/get authorized with it but you don't get an asssociated nopCommerce account - the plugin is needed for this bit - if facebook gets hardcoded then it hinders other providers. In my experience each type of identity provider does need a plugin as the code base for the stores are different, even in PHP the different frameworks mean you have to publish multiple plugins, and I'm predicting FIDO integrations will be needed by the time of the next release...