 |
|
|
 |
Joined: 2/20/2014
Posts: 26
|
|
|
I'm trying to use Smith Cart 6.0 on an old DNN 5.06 site which I do not wish to upgrade to the latest version of DNN. Am I going to get a bunch of errors trying to do this? The install went fine, but when I try to use the BuyNow module I get the error below. Any ideas how to fix this, and if I do fix it will there just be other errors due to compatibility issues?
Error: Smith.BuyNow is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: (0): error CS1705: Assembly 'SmithBuyNow, Version=6.0.0.0, Culture=neutral, PublicKeyToken=null' uses 'Telerik.Web.UI, Version=2012.3.1205.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4' which has a higher version than referenced assembly 'Telerik.Web.UI, Version=2010.3.1317.35, Culture=neutral, PublicKeyToken=121fae78165ba3d4' ---> System.Web.HttpCompileException: (0): error CS1705: Assembly 'SmithBuyNow, Version=6.0.0.0, Culture=neutral, PublicKeyToken=null' uses 'Telerik.Web.UI, Version=2012.3.1205.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4' which has a higher version than referenced assembly 'Telerik.Web.UI, Version=2010.3.1317.35, Culture=neutral, PublicKeyToken=121fae78165ba3d4' at System.Web.Compilation.AssemblyBuilder.Compile() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---
|
|
|
|
 | |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hi Kyle,
SmithCart 6.0 is not compatible with DNN 5. The last Cart version released for DNN 5 is version 5.0 released on 6/6/2012.
The security of your website should be the top priority and I do not recommend using DNN 5.0.6. It was released about 6 years ago and is not secure. Malicious users will attack known security vulnerabilities in older versions of DNN. I highly recommend test driving a DNN upgrade with a clone of the site. Our in-house consulting team can also do the upgrade of DNN for you.
|
|
|
|
| |
|
|
|
Joined: 2/20/2014
Posts: 26
|
|
|
I do see where some invisible spam links are showing up in the page source at the bottom of all pages on my site, which were probably put there through some form of SQL injection. I have another DNN site running 7.02 and it has been hacked in the same way, so whatever the security hole is that allows this, DNN has not fixed it. The main reason I hate to upgrade the 5.02 site, other than being a bunch of work that is sure to produce all kinds of new time wasting problems to solve, is that the latest version of DNN seems to run much slower than the older version. I also like the CMS interface better on the old versions as well. Upgrading might also break a bunch of modules that were purchased four years ago, requiring me to buy updates for them. This illustrates a general problem with using DNN and probably any other CMS to build sites-- trying to upgrade one module at a later date winds up causing you to have to rebuild the whole dang site, spending time and money all over again for things that are otherwise working fine.
|
|
|
|
| |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hi Kyle,
I understand where you are coming from. While it's important to make sure your site stays functional, it's equally important to ensure that it's secure. Even comparing DNN 5.0.2 to DNN 7.0.2 isn't a fair comparison as 7.0.2 was released on January 11, 2013 and from my personal experience there have been many performances improvements since the early releases of DNN7. In fact, we've done upgrades on quite a few sites from DNN 5 to 7 with minimal issues other than skins and a module update from a third party vendor. Please see the following link for a list of security updates in DNN: http://www.dnnsoftware.com/platform/m...
If you do not have a "sandbox" to try out the upgrade, please read the How To KB article at the following link: http://helpdesk.smith-consulting.com/...
There is no reason not to have a development site. It doesn't take another server, you don't even have to install DNN or SQL Server again, but you can make your changes, test them, and then copy the ascx files over to your live system once you have tested.
|
|
|
|
| |
|
|
|
Joined: 2/20/2014
Posts: 26
|
|
|
I decided to just rebuild the site from the ground up rather than trying to upgrade the existing design. I did try to upgrade it but ran into all kinds of problems even just getting it staged locally, whereas installing the latest version of DNN locally worked fine so now I'm just building it up from there. I still have problems with the smithcart BuyNow module not working though. I'm trying to put smithcart 6.0 on DNN 7.4.1 and getting the following error:
Error: Smith.BuyNow is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Could not load file or assembly 'dotnetnuke.log4net, Version=3.0.0.0, Culture=neutral, PublicKeyToken=53eb1fac7b60111f' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly 'dotnetnuke.log4net, Version=3.0.0.0, Culture=neutral, PublicKeyToken=53eb1fac7b60111f' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) at Smith.DNN.Modules.BuyNow.MyCart..ctor() at Smith.DNN.Modules.BuyNow.ProductsList..ctor() at ASP.desktopmodules_smith_buynow_productslist_ascx..ctor() at __ASP.FastObjectFactory_app_web_productslist_ascx_54f2e0e1_fvwh_i9j.Create_ASP_desktopmodules_smith_buynow_productslist_ascx() at System.Web.Compilation.BuildResultCompiledType.CreateInstance() 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.WebFormsModuleControlFactory.CreateModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration) at DotNetNuke.UI.Modules.ModuleControlFactory.LoadModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---
|
|
|
|
| |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hi Kyle,
Version 6.0 of the Cart references a specific version of the DNN log4net.dll and in DNN 7.4.1 the dll was updated to version 3. The solution to the error is to upgrade to the latest Cart which no longer references a specific log4net version.
|
|
|
|
| |
|
|
|
Joined: 2/20/2014
Posts: 26
|
|
|
What will it cost me to upgrade?
|
|
|
|
| |
|
|
|
Joined: 7/15/2011
Posts: 21
|
|
|
Hi Kyle,
I would be happy to go over your upgrade options with you.
Please send your original order ID in an email to licensing@smith-consulting.com so I can determine your discount eligibility.
At your service,
Kelli, SC
Kelli Kropko
Licensing and Marketing
949.218.9600
 |
|
|
|
| |