We managed to reproduce the problem.
The actual problem seems to be how nopCommerce works with newly installed plugins.
It is a general problem, so we are going to report it in the nopCommerce forums.EDIT: The problem is reported here Solution:
The easiest fix is to simply change the Global.asax
file’s date modified, which will cause you application to restart and find the controllers of the newly installed plugins. There are other ways to restart your web application as the ASP.NET engine watches for changes in several places i.e the bin folder of the application. But the simplest and easiest way is to change the Global.asax
file.How to do it?
You can do this by opening the file Global.asax
in Notepad and simply add a blank space at the end of the file and then save it.
file is located in the main folder of your application(the same folder where the Web.config file is).
Make sure the Global.asax
file has an updated date modified.
You should now be able to open the plugin pages.