I use DNN 5, I am completely new to this exciting project. I do research so I may consult my company if DNN is the best solution for us.

I get the following error when I insert a Store Catalog module in a page.

A critical error has occurred.
Method not found: 'Void DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(System.String,

DotNetNuke.Entities.Modules.PortalModuleBase, System.Exception, Boolean)'.

I would be gratefull to anybody that might help me.

D. Peris

So, in the functional releases of DotNetNuke 5.0.0, the store module that is packaged with it does not work?  The question I have then is why is a non-functional module included in the package?  I understand that the store module is an important feature and "should" be included, I just don't understand why a non-functional version would be included, or more specifically why DotNetnuke 5.0.0 would be released containing a core module that is non-functional.  This makes not sense to me.

So anyhow, I started building out a new site on the newest (5.0.0).

So far, I've added a very minor amount of content, manually fixed the sitemap, by copying an old version of sitemap.aspx and the code behind, but renaming it sitemap2.aspx.  I've finally gotten to the part where I'd like to work with the store module, start installing and setting up the store admin section...all prepared and excited only to learn that I have to wait an undetermined amount of time to finish this section, when someone decides to fix the included but not compatible module. 

I love DotNetNuke, and truely appreciate it and all the hard work that is contributed, but I can't help to giggle to myself wondering what the heck is going on here??!?!?!  Someone decided it was the right thing to do to package an incompatible module into a release version?

Just my 2 cents.  Can we get an ETA on an upgrade to the store module included in DNN to one that is compatible with DNN?

Thanks

Josh

Josh Martin