Please restore from your backup and try installing 3.88 on a test site first.

-Scott

---

Scott Kelly
Project Manager

We are releasing a hotfix for 3.88 that could fix this issue today. Check the downloads page after noon pst for the hotfix.

-Scott

---

Scott Kelly
Project Manager

After installing the hotfix, the following modules generated errors: Categories, Featured Products, MiniCart, and Product Details. I pasted the error below, just keep in mind that the same error is being generated by all the modules I listed above. Unfortunately the checkout situation is unchanged. One thing I did notice though: when you click the button to update the quantity, the partially rendered for at the bottom of the page disappears, but all the dropdowns are still empty.

ModuleId: 754
ModuleDefId: 175
FriendlyName: Featured
ModuleControlSource: DesktopModules/Smith.FeaturedProducts/FeaturedProducts.ascx
AssemblyVersion: 5.2.3
PortalID: 10
PortalName: Vapor X
UserID: 30
UserName: mgcox
ActiveTabID: 252
ActiveTabName: Shop Online
RawURL: /ShopOnline.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: https://www.myvaporx.com/ShopOnline/tabid/252/ctl/Module/ModuleId/841/Default.aspx
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 90187afb-48e5-4606-959e-32882ad04b40
InnerException: Could not load file or assembly 'App_SubCode_SmithCart, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: Smith.DNN.Modules.FeaturedProducts.FeaturedProducts..ctor
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Could not load file or assembly 'App_SubCode_SmithCart, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. ---> System.IO.FileNotFoundException: Could not load file or assembly 'App_SubCode_SmithCart, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. File name: 'App_SubCode_SmithCart, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' at Smith.DNN.Modules.FeaturedProducts.FeaturedProducts..ctor() at ASP.desktopmodules_smith_featuredproducts_featuredproducts_ascx..ctor() at __ASP.FastObjectFactory_app_web_khbbhijy.Create_ASP_desktopmodules_smith_featuredproducts_featuredproducts_ascx() at System.Web.UI.TemplateControl.LoadControl(IWebObjectFactory objectFactory, VirtualPath virtualPath, Type t, Object[] parameters) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. --- End of inner exception stack trace ---
Source:
Server Name: WIN-20R7V0NLMUH

I got an error after installing the beta. In version 3.88, I have the BuyNow module on another portal, and when I update the settings it affects the behavior of the checkout process. In my production portal, the checkout process behaves as if I placed the BuyNow module on the page and attempted to checkout without updating the settings at all. Why would one portal not pickup the settings and another does? Any idea how I can fix this? Maybe by forcing it to read the settings? Any help would be appreciated, thanks.

-Marvin Cox

I figured out the problem. For some reason there were records in the TabModules table that were pointing to module IDs that didn't exist anymore but they had the same tab ID of the working BuyNow module. While the settings and store admin functions were being saved under the correct module ID, clicking checkout or view cart was inserting these "orphan" module IDs in the URL because they occurred first in numerical sequence in the TabModules table. The solution was to delete these the two records in the table that had the same tab ID as the correct module yet didn't actually appear on the page. My guess is that when I removed the BuyNow module from my Order Online page and added it again, the DNN framework didn't cascade the deletes in the database. This is why the hotfixes and upgrades weren't fixing the problem, it was information contained in the database unique to my store that caused it. Thanks for your help Scott, just want to let you know that in my situation the problem doesn't lie within Smith Cart, I think it's DNN itself.

-Marvin Cox