We understand that your ecommerce site is crucial to the success of your business, from time to time issues and questions can arise and you need to have the assurance there will be someone on hand to help resolve these in a timely fashion so you can spend your time driving your own business forward.

So if you are looking for faster responses to your questions or would like the assurance there is someone on hand for you to contact, fear not we have a number of paid support options that are available to you that can give your organisation the peace of mind knowing a member from the Cart Viper team will always be available to assist!

Purchase a Support Plan

Community Support

HomeHomeIssues and Supp...Issues and Supp...Installation & ...Installation & ...AJAX and SSLAJAX and SSL
Previous
 
Next
New Post
4/29/2013 2:20 PM
 

Hi CV,

Running DotNetNuke Community Edition / 06.02.06 with the latest version of CartViper. We have SSL wrapped around the entire site (due to our Cloud Shared server) and I am getting an error saying their are unprotected items on the page. I had this same issue with non-store pages due to http links to various jQuery files. I resolved by either updating the links to a secure (https) version, or downloading and linking from my DNN site.

There is one jquery (http://code.jquery.com/jquery-migrate-1.0.0.js) being called from 3 different CartViper files (Account.ascx, AjaxAddToCart.aspx and Store.aspx). There is no secure version of this script so I downloaded, saved to my script directory, and updated those 3 pages to link to my server version.

The unsecured items error went away, but so did all my products.

Has anyone had a similar experience, and how did you resolve it.

Thanks for reading.

 
New Post
4/29/2013 8:35 PM
 
Hi John

We have hot linked the loading of the jQuery Migrate to the CDN which is provided by jQuery, however as you have found out this is only available over http and not https.

What you have done is correct, download and place the file into your own directory on the server and reference the script tags to use that version.
Can you see the script being loading in Firebug or similar? Sounds like the script isn't getting loaded.

If you are still having problems send me over the url to the store and we'll have a look.

Regards

Mark
 
New Post
4/30/2013 3:41 PM
 
HI Mark,
I have gone back and updated the Account.ascx, AjaxAddToCart.aspx and Store.aspx files, hard coding the link to the jquery-migrate.1.0.0.js file on our server (to get around the SSL issue).

The page actually generated an error this time, last time I tried my products simply disappeared with no error. I double-checked the coding to ensure it was pathed correctly (<script type="text/javascript" src="<% =SkinPath %>skin_scripts/jquery-migrate-1.0.0.js"></script>). I know this method of pathing works since I am using the same method for some other jQuery scripts. I had Firebug activated but with the error being generated it did not appear to even fire off.

Here is a link to the store:
https://www.hmamembers.org/Meetings/RegionalMeeting/%E2%80%9913Central%28TN%29/EventRegistration/tabid/298/CategoryID/1/Default.aspx

I have added the generated error message below:
--------------------
Error: Cart Viper Catalog is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: \\fs3-n02\stor9wc1dfw1\630057\www.hmamembers.org\web\content\DesktopModules\CartViper\AjaxAddToCart.ascx(3): error CS0103: The name 'SkinPath' does not exist in the current context ---> System.Web.HttpParseException: \\fs3-n02\stor9wc1dfw1\630057\www.hmamembers.org\web\content\DesktopModules\CartViper\AjaxAddToCart.ascx(3): error CS0103: The name 'SkinPath' does not exist in the current context ---> System.Web.HttpCompileException: \\fs3-n02\stor9wc1dfw1\630057\www.hmamembers.org\web\content\DesktopModules\CartViper\AjaxAddToCart.ascx(3): error CS0103: The name 'SkinPath' does not exist in the current context at System.Web.Compilation.BuildManager.PostProcessFoundBuildResult(BuildResult result, Boolean keyFromVPP, VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode) at System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.BaseTemplateParser.GetReferencedType(VirtualPath virtualPath, Boolean allowNoCompile) at System.Web.UI.BaseTemplateParser.GetUserControlType(VirtualPath virtualPath) at System.Web.UI.MainTagNameToTypeMapper.ProcessUserControlRegistration(UserControlRegisterEntry ucRegisterEntry) at System.Web.UI.BaseTemplateParser.ProcessDirective(String directiveName, IDictionary directive) at System.Web.UI.TemplateControlParser.ProcessDirective(String directiveName, IDictionary directive) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseReader(StreamReader reader, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.UI.TemplateParser.Parse(ICollection referencedAssemblies, VirtualPath virtualPath) at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() 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) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String 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 ---

Thanks for your time,
John
 
New Post
4/30/2013 7:53 PM
 
What are, if any, the issues if I just removed the offending link from those 3 files.
I tried as a test and I received no SSL errors in IE, ran through the process, placed an order, received order confirmation, etc.
 
New Post
4/30/2013 8:14 PM
 
Hi John,

If you remove the links the store will stop working so I would not advise that.

You are getting that error as the property "SkinPath" only exists in the context of DNN skins as these files are modules that property does not exist so your are getting that error.

If you change your link too:

<script type="text/javascript" src="<% =ModulePath%>skin_scripts/jquery-migrate-1.0.0.js"></script>

That will output the path:

desktopmodules/cartviper/skin_scripts/jquery-migrate-1.0.0.js

So just just move the folder "skin_scripts" and .js file inside the cart viper folder and it should reference correctly.

Thanks
Nigel.
 
Previous
 
Next
HomeHomeIssues and Supp...Issues and Supp...Installation & ...Installation & ...AJAX and SSLAJAX and SSL


 

We use cookies on our website to improve our service to you, by continuing you agree to our use of cookies. However you are able to update your settings at any time.

Cookie Policy

A cookie, also known as an HTTP cookie, web cookie, or browser cookie, is a piece of data stored by a website within a browser, and then subsequently sent back to the same website by the browser. Cookies were designed to be a reliable mechanism for websites to remember things that a browser had done there in the past, which can include having clicked particular buttons, logging in, or having read pages on that site months or years ago.

Strictly Necessary Cookies

These cookies cannot be disabled

These cookies are necessary for the website to function and cannot be switched off. They are normally set in response to your interactions on the website e.g. logging in etc.

Cookies:
  • .ASPXANONYMOUS
  • .DOTNETNUKE
  • __RequestVerificationToken
  • authentication
  • CV_Portal
  • CV_Store_Portal_Cart_0
  • CV_USER
  • dnn_IsMobile
  • language
  • LastPageId
  • NADevGDPRCookieConsent_portal_0
  • userBrowsingCookie

Performance Cookies

These cookies allow us to monitor traffic to our website so we can improve the performance and content of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited or how you navigated around our website.

Cookies:
  • _ga
  • _gat
  • _gid

Functional Cookies

These cookies enable the website to provide enhanced functionality and content. They may be set by the website or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

Cookies:

Currently we are not utilizing these types of cookies on our site.

Targeting Cookies

These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.

Cookies:

Currently we are not utilizing these types of cookies on our site.

Feedback