Error on previewing framework skins

A place for discussion about skinning and design. Before posting questions here you should review the documentation about creating skins.

11/4/2017 1:34:55 PM
Gravatar
Total Posts 500
feet planted firmly on the ground

Error on previewing framework skins

I'm trying to review the new framework skins and scout skin on an existing site that uses an old artisteer-based skin.

When I preview the new skins I get an error with this in the log:

2017-11-04 18:28:37,736 ERROR 82.69.43.209 - en-GB - /Data/style/mojo1.css - mojoPortal.Web.PageNotFoundHttpModule - Referrer(https://www.breconfans.org.uk/Error.htm?aspxerrorpath=/Default.aspx)  PageNotFoundHttpModule handled error.
System.Web.HttpException (0x80004005): The file '/404notfound.aspx' does not exist.
   at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath)

I have upgraded to latest version

mojoPortal Version 2.6.0.0 MSSQL

Operating System Microsoft Windows NT 6.1.7601 Service Pack 1

ASP.NET Info 4.0.30319.42000 Running in Full Trust

Any thoughts what's wrong? 

11/4/2017 2:50:45 PM
Gravatar
Total Posts 1981

Re: Error on previewing framework skins

Hi Crispin,

Are there any other errors in the log? That error was also handled by mojo so it's not why the error page showed up. It mentions the error page because the link that is on the error page was probably clicked to go to the home page. (Referrer ...). Chances are there is something in the framework skin theme.skin that your copy of mojoPortal doesn't have. That shouldn't be the case but that is usually why the error page pops up after a skin has been chosen.

Framework doesn't use /Data/style/mojo1.css. That seems like an old file that the built-in fallback skin might be using.

One more question, are you using the Preview link in Site Settings to view these skins or are you changing the Site Skin to one of these to test?

Thanks,
Joe

11/5/2017 1:37:45 AM
Gravatar
Total Posts 500
feet planted firmly on the ground

Re: Error on previewing framework skins

I was using the preview function in site settings. I will have another look if I get time today...

11/5/2017 2:00:04 AM
Gravatar
Total Posts 500
feet planted firmly on the ground

Re: Error on previewing framework skins

Switching the site to clean-white crashes it. Setting the skin back to previous in the mp_Sites table gets the site working again once the application pool is recycled.

Errors in the log include:

2017-11-05 07:53:06,863 ERROR 82.69.43.209 - en-GB - /Admin/SiteSettings.aspx - mojoPortal.Web.Global - 82.69.43.209 /Admin/SiteSettings.aspx Referrer(https://www.breconfans.org.uk/Admin/SiteSettings.aspx) useragent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063
System.Web.HttpParseException (0x80004005): Could not load file or assembly 'sts.Web.UI' or one of its dependencies. The system cannot find the file specified. ---> System.IO.FileNotFoundException: Could not load file or assembly 'sts.Web.UI' or one of its dependencies. The system cannot find the file specified.
File name: 'sts.Web.UI'
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at System.Web.Configuration.CompilationSection.LoadAssembly(String assemblyName, Boolean throwOnFail)
   at System.Web.UI.TemplateParser.AddAssemblyDependency(String assemblyName, Boolean addDependentAssemblies)
   at System.Web.UI.MainTagNameToTypeMapper.ProcessTagNamespaceRegistrationCore(TagNamespaceRegisterEntry nsRegisterEntry)
   at System.Web.UI.BaseTemplateParser.ProcessDirective(String directiveName, IDictionary directive)
   at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding)

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].

   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)
2017-11-05 07:53:07,198 ERROR 82.69.43.209 - en-GB - /Data/style/mojo1.css - mojoPortal.Web.PageNotFoundHttpModule - Referrer(https://www.breconfans.org.uk/Error.htm?aspxerrorpath=/Admin/SiteSettings.aspx)  PageNotFoundHttpModule handled error.
System.Web.HttpException (0x80004005): The file '/404notfound.aspx' does not exist.
  

11/5/2017 2:15:25 AM
Gravatar
Total Posts 500
feet planted firmly on the ground

Re: Error on previewing framework skins

OK solved... theme.skin in clean-white has the settings for FWP and Calendar Pro un-commented by default. Commenting these out has my site working.

Thanks!

 

11/6/2017 10:17:02 AM
Gravatar
Total Posts 1981

Re: Error on previewing framework skins

Hi,

I'm glad you found the problem and were able to remedy it.

Was this skin downloaded recently? We try to keep things like that commented out in the theme.skin files that are saved to the repo but I know we missed it in a few skins a while back. I checked the repo and the sts.web.ui stuff is commented out.

Thanks,
Joe

11/6/2017 2:05:55 PM
Gravatar
Total Posts 500
feet planted firmly on the ground

Re: Error on previewing framework skins

I cannot quite recall - is clean-white shipped with the standard download? I've a feeling I possibly got it by downloading from the demo site, in which case that would explain it having the optional modules enabled. If so, my apologies for the confusion. The nasty aspect of this is that when it goes wrong, it crashes the site so thoroughly, requiring direct database access to recover the site. Is there any way of making it less fragile? Should the site revert to a default skin if anything's wrong (your earlier reply suggests it does this), and if it does, where is this skin to be found any why would mine also be throwing an error?

11/6/2017 2:45:06 PM
Gravatar
Total Posts 1981

Re: Error on previewing framework skins

Hi Crispin,

The only skin we ship with mojoPortal is "framework". This is primarily to keep the release file smaller in size. 

If something in the layout.master causes problems with the master file from being rendered, it will fallback to a very plain no-frills skin that still lets you access administration so you can change the skin or look at the log. Unfortunately, if there is a problem in the theme.skin the skin will crash the site. It's always been this way but for a long time mojoPortal didn't use the theme.skin much and none of the shipped skins had anything in the theme.skin for the pro modules.

We use the theme.skin a lot because we can use special settings on controls in the theme.skin to control the markup and classes used throughout the site and on specific features. We are looking for ways to trap errors thrown by the theme.skin but we haven't come up with anything yet.

Thanks,
Joe

11/6/2017 3:00:32 PM
Gravatar
Total Posts 500
feet planted firmly on the ground

Re: Error on previewing framework skins

Thanks Joe, and well done on all the great recent work on mojo!