Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Garrett Fisher 341 posts 496 karma points
    Aug 26, 2011 @ 18:27
    Garrett Fisher
    0

    4.7 Upgrade Causing Broken XSLT's

    Hi,

    I've just upgraded from 4.5.2 to 4.7 and am seeing that familiar "Error parsing XSLT file" error everywhere on the front end.  In the past (as with my upgrade from 4.0.2 to 4.5.2) I have always fixed this by setting:

    <UseLegacyXmlSchema>True</UseLegacyXmlSchema>

    In my umbracoSettings.config.  However, this isn't working this time.  Can you still use the old XML schema in 4.7?  I can't find any documentation dealing with that if that's an issue.  Does anyone have any ideas on why I might be getting this error still?  I've recycled my app pool and my site several times.

    Thanks,

    Garrett

     

  • Tom Fulton 2030 posts 4998 karma points c-trib
    Aug 26, 2011 @ 19:17
    Tom Fulton
    0

    Hi Garrett,

    To get the "full" error message, try adding ?umbDebugShowTrace=1 to your URL and look at the trace log at the bottom for any errors in red.  Or try saving an XSLT file.

    In 4.7 you have to remove some old DLL files during the upgrade process, or else your XSLTs will fail to render.  The DLLs to remove (per Codeplex) are /bin/Microsoft.Scripting.dll, /bin/Iron * .dll, /bin/RazorEngine * .dll

    Also umbraco.MacroEngines.Legacy if you have it. 

    Otherwise the full error should give you some inidication of which DLL is causing it - paste it here if you're not sure.

    Hope this helps,
    Tom

  • Garrett Fisher 341 posts 496 karma points
    Aug 26, 2011 @ 19:57
    Garrett Fisher
    0

    Thanks for your reply Tom.

    Well here's what happened.  I deleted the DLL's you suggested and restarted, but then I got errors saying that MicrosoftScripting was missing?!   So I re-added them so that I could get the pure error to post here:

    Error occured
    
    System.Exception: Unable to load one or more of the types in assembly 'umbraco.standardFormhandlers, Version=1.0.3625.27286, Culture=neutral, PublicKeyToken=null'. Exceptions were thrown:
    System.TypeLoadException: Could not load type 'umbraco.interfaces.IFormhandler' from assembly 'interfaces, Version=1.0.4085.20549, Culture=neutral, PublicKeyToken=null'.
    System.TypeLoadException: Could not load type 'umbraco.interfaces.IFormhandler' from assembly 'interfaces, Version=1.0.4085.20549, Culture=neutral, PublicKeyToken=null'.
    System.TypeLoadException: Could not load type 'umbraco.interfaces.IFormhandler' from assembly 'interfaces, Version=1.0.4085.20549, Culture=neutral, PublicKeyToken=null'.
    at umbraco.BusinessLogic.Utils.TypeFinder.FindClassesMarkedWithAttribute(Assembly assembly, Type attribute)
    at umbraco.BusinessLogic.Utils.TypeFinder.FindClassesMarkedWithAttribute(Type attribute)
    at umbraco.macro.GetXsltExtensionsImpl()
    at umbraco.macro.b__4()
    at umbraco.cms.businesslogic.cache.Cache.GetCacheItem[TT](String cacheKey, Object syncLock, CacheItemPriority priority, CacheItemRemovedCallback refreshAction, CacheDependency cacheDependency, TimeSpan timeout, GetCacheItemDelegate`1 getCacheItem)
    at umbraco.macro.GetXsltExtensions()
    at umbraco.macro.AddMacroXsltExtensions()
    at umbraco.presentation.webservices.codeEditorSave.SaveXslt(String fileName, String oldName, String fileContents, Boolean ignoreDebugging)
    

    I get this error for every XLST script that is called.  No mention of a DLL though.  Thoughts?

     

    Thanks again,

    Garrett

  • Tom Fulton 2030 posts 4998 karma points c-trib
    Aug 26, 2011 @ 20:01
    Tom Fulton
    1

    I think that one should be removed also:  umbraco.standardFormhandlers.dll - this was from an older version I believe.

     

  • Jeroen Breuer 4908 posts 12265 karma points MVP 5x admin c-trib
    Aug 26, 2011 @ 20:33
  • Garrett Fisher 341 posts 496 karma points
    Aug 26, 2011 @ 21:20
    Garrett Fisher
    0

    Thank you guys -- it was indeed the need to delete umbraco.standardFormhandlers.dll.  That did the trick.  I also had to delete VistaDB*.dll.  All others don't seem to have a negative effect.

     

    //Garrett

Please Sign in or register to post replies

Write your reply to:

Draft