Copied to clipboard

Flag this post as spam?

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


  • pieter van Uhm 23 posts 49 karma points
    Aug 05, 2015 @ 07:59
    pieter van Uhm
    0

    Upgrade from 1.6 to 1.9. (umbraco 4.10.1) Installation succesfull but in content/nodes i get errors

    Hi,

    I have upgrade SEO Checker from 1.6 to 1.9 and it is installed succesfull.

    I can acces the SEO Checker Section, everything is working here.

    But when i want to access for example the Homepage (content), i get this error.

    See image for error message.

    I hope somebody can help me!enter image description here

    Error message: Server Error in '/' Application.

    Could not load type 'SEOChecker.Core.Helpers.Logging' from assembly 'SEOChecker.Core, Version=1.9.0.0, Culture=neutral, PublicKeyToken=null'.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.TypeLoadException: Could not load type 'SEOChecker.Core.Helpers.Logging' from assembly 'SEOChecker.Core, Version=1.9.0.0, Culture=neutral, PublicKeyToken=null'.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [TypeLoadException: Could not load type 'SEOChecker.Core.Helpers.Logging' from assembly 'SEOChecker.Core, Version=1.9.0.0, Culture=neutral, PublicKeyToken=null'.] SEOChecker.DataTypes.Seo.SEOCheckerDataEditor.OnInit(EventArgs e) +0 System.Web.UI.Control.InitRecursive(Control namingContainer) +186 System.Web.UI.Control.InitRecursive(Control namingContainer) +314 System.Web.UI.Control.InitRecursive(Control namingContainer) +314 System.Web.UI.Control.InitRecursive(Control namingContainer) +314 System.Web.UI.Control.InitRecursive(Control namingContainer) +314 System.Web.UI.Control.AddedControl(Control control, Int32 index) +189 umbraco.controls.ContentControl.addControlNew(Property p, TabPage tp, String Caption) +8908 umbraco.controls.ContentControl.CreateChildControls() +1744 System.Web.UI.Control.EnsureChildControls() +189 umbraco.controls.ContentControl.OnInit(EventArgs e) +127 System.Web.UI.Control.InitRecursive(Control namingContainer) +186 System.Web.UI.Control.AddedControl(Control control, Int32 index) +189 umbraco.cms.presentation.editContent.OnInit(EventArgs e) +2119 System.Web.UI.Control.InitRecursive(Control namingContainer) +186 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2098

    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18446

  • Casper Andersen 126 posts 506 karma points
    Aug 05, 2015 @ 12:22
    Casper Andersen
    0

    No idea if this will help, and if this is even possible in umbraco 4 since i only know umbraco 7. But i would try and republish the entire site and see if that might help, im guessing u might have some properties from the SEO package on some content and that is what can not be loaded and there by causing the problem.

  • Richard Soeteman 3234 posts 9118 karma points
    Aug 06, 2015 @ 05:25
    Richard Soeteman
    0

    Can you try to copy the seochecker.logging dll and seochecker.core.dll from the package file to the /bin folder. Umbraco installer always says all is good even when it's not.

    Hope this helps,

    Richard

  • pieter van Uhm 23 posts 49 karma points
    Aug 06, 2015 @ 14:22
    pieter van Uhm
    0

    Hi Richard,

    This doesn't work :( do you have maybe other solutions?

    Kind regards,

    Pieter

  • pieter van Uhm 23 posts 49 karma points
    Aug 06, 2015 @ 14:25
    pieter van Uhm
    0

    @Casper, republishing also didn't work..

  • Richard Soeteman 3234 posts 9118 karma points
    Aug 06, 2015 @ 14:33
    Richard Soeteman
    0

    Hi Pieter,

    Sorry missed that you used an older version of Umbraco. Delete seocheck.logging and use SEOChecker.LegacyLogging..

    If that doesn't work validate your install via the manual configuration in the SEOChecker manual.

    Hope this helps,

    Richard

  • Geoff Beaumont 59 posts 84 karma points
    Sep 23, 2015 @ 13:23
    Geoff Beaumont
    0

    Hi Richard,

    I've got what looks like exactly the same issue:

    2015-09-23 14:19:35,056 [135] ERROR SEOChecker.HttpModules.UrlModule - [P12656/T35/D9] SEOChecker: Error in HttpModule for url rewriting
    System.TypeLoadException: Could not load type 'SEOChecker.Core.Helpers.Logging' from assembly 'SEOChecker.Core, Version=1.9.2.0, Culture=neutral, PublicKeyToken=null'.
       at SEOChecker.MVC.PreRequest.EnsureUmbracoContext.Execute(HttpContext context)
       at SEOChecker.Core.Umbraco.RequestHandler.PreRequestFactory.Execute(HttpContext context)
       at SEOChecker.Core.Extensions.HttpContextExtensions.RequestIsAllowedForRewriting(HttpContext context)
       at SEOChecker.HttpModules.UrlModule.(Object , EventArgs )
    

    This is SEOChecker v1.9.2 on Umbraco v7.2.8, so no old versions here.

    Geoff

  • Richard Soeteman 3234 posts 9118 karma points
    Sep 23, 2015 @ 13:26
    Richard Soeteman
    0

    Make sure SEOChecker.Core (from latest package )and SEOChecker.Core.Logging.Legacy are in the bin folder

  • Geoff Beaumont 59 posts 84 karma points
    Sep 23, 2015 @ 13:37
    Geoff Beaumont
    0

    I've got the latest SEOChecker.Core. SEOChecker.Core.Logging.Legacy wasn't there, so I tried adding that - it didn't fix the error, and also caused additional warnings to appear advising updating code to not use deprecated logging methods (I didn't copy the the error I'm afraid, but it looked to be causing core code to call deprecated logging methods rather than the new ones).

  • Geoff Beaumont 59 posts 84 karma points
    Sep 28, 2015 @ 08:35
    Geoff Beaumont
    0

    Hi Richard,

    I've just discovered that this exception is breaking the XML sitemap (you get a 500 error with this exception).

    Any further ideas on how to fix this?

    Geoff

  • Richard Soeteman 3234 posts 9118 karma points
    Sep 28, 2015 @ 09:36
    Richard Soeteman
    0

    I think the install somehow got corrupted. Best to follow the manual installation steps in the seo checker user manual

    http://soetemansoftware.nl/seo-checker/downloads

  • Geoff Beaumont 59 posts 84 karma points
    Sep 28, 2015 @ 19:24
    Geoff Beaumont
    0

    That results in the following error:

    Type 'Umbraco.Core.Models.PublishedContent.PublishedPropertyType+CompatConverter' cannot be an IPropertyValueConverter for property 'seoChecker' of content type 'HomePage' because type 'SEOChecker.PropertyEditorConverters.SEOCheckerMetadataConverter' has already been detected as a converter for that property, and only one converter can exist for a property.
    

    I suspect the manual install instructions are out of date? They don't mention that the DLL files in the ZIP have all had their extension changed to .dl (one l not two), and say to copy all DLLs to the /bin directory, when the Umbraco package and NuGet installer both put some of them in a temporary directory (presumably so on some are installed depending on the version of Umbraco?).

  • Geoff Beaumont 59 posts 84 karma points
    Sep 28, 2015 @ 20:05
    Geoff Beaumont
    0

    Judging by the errors I saw as I removed DLLs, I presume that where there's a "Legacy" DLL that should replace the standard DLL in some cases - what's the logic flow for determining which is needed?

    As I'm on the latest release of Umbraco, should I actually be using any Legacy DLLs at all? Are some of the standard ones actually targetting Umbraco 7.3?

  • Richard Soeteman 3234 posts 9118 karma points
    Sep 29, 2015 @ 05:37
    Richard Soeteman
    0

    The normal ones are targeting 7.x (7.3 is not officially released yet) and legacy is everything before. V2 will be 7.x only

  • Geoff Beaumont 59 posts 84 karma points
    Sep 29, 2015 @ 08:00
    Geoff Beaumont
    0

    In that case I have the latest version of all non-legacy DLLs, and I'm still getting the Logging error.

  • Richard Soeteman 3234 posts 9118 karma points
    Sep 29, 2015 @ 08:04
    Richard Soeteman
    0

    Topic says you are using 4.x? Also copied SEOChecker normal dll's?

  • Geoff Beaumont 59 posts 84 karma points
    Sep 29, 2015 @ 08:31
    Geoff Beaumont
    0

    The original poster (pieter van Uhm) is using Umbraco v4.x - I'm seeing the same issue on v7.2.8.

  • Geoff Beaumont 59 posts 84 karma points
    Sep 29, 2015 @ 15:26
    Geoff Beaumont
    0

    Okay, just tried installing SEOChecker 1.9.2 on a new instance of Umbraco 7.2.8, using NuGet - it failed to install any of the DLLs that have two versions (legacy and standard) - they weren't even present in the /App_Data/TEMP/SEOChecker directory, and, obviously, caused errors on the site.

    Uninstalled NuGet package - it left behind module registrations in the web.config which I had to remove manually to get the site working again. Not sure if it left anything else.

    Installed the Umbraco package version of SEOChecker 1.9.2. Still none of the legacy/standard DLLs installed, had to drop them in manually. Also didn't create the module registrations in web.config (but did at least warn it hadn't in the back end).

    Now...same as my other site. Lots of errors in the log and sitemap not working:

    2015-09-29 16:17:56,825 [23] ERROR SEOChecker.HttpModules.UrlModule - [P7660/T32/D18] SEOChecker: Error in PageNotFound Module
    System.TypeLoadException: Could not load type 'SEOChecker.Core.Helpers.Logging' from assembly 'SEOChecker.Core, Version=1.9.2.0, Culture=neutral, PublicKeyToken=null'.
       at SEOChecker.MVC.PreRequest.EnsureUmbracoContext.Execute(HttpContext context)
       at SEOChecker.Core.Umbraco.RequestHandler.PreRequestFactory.Execute(HttpContext context)
       at SEOChecker.HttpModules.UrlModule.(Object , EventArgs )
    

    First site is due to go live tomorrow...looking like this is going to be a missed deadline :(

  • Richard Soeteman 3234 posts 9118 karma points
    Sep 29, 2015 @ 15:40
    Richard Soeteman
    0

    When installing make sure modify rights are on the mentioned folders. Remove references from web.config and install again. Easier from package installer.

  • Geoff Beaumont 59 posts 84 karma points
    Sep 30, 2015 @ 08:49
    Geoff Beaumont
    0

    Both sites are running in Visual Studio/IIS Express and have full file permissions for all folders.

    Comparing the DLLs between the sites and those in both the Umbraco and NuGet packages, SEOChecker.MVC.dll was a different size. The version on the sites was 18KB, the one in the packages 10KB. Both reported themselves as v1.0.0.0, but I'm guessing one is from the previous version of SEOChecker? It presumably wasn't overwritten when I upgraded on the first site (after both installers failed on the second site I copied the missing DLLs from the first site, which upon reflection was a bit dumb, given that site wasn't working properly...).

    Copying the 10KB version onto both sites has got rid of the errors, and the sitemap is now working.

    Thought I'd tried overwriting all the SEOChecker DLLs manually, but now doubting I did - if it failed to overwrite manually it should have told me...

    Now debating whether to switch the second site back to NuGet - both installers seem to be seriously flaky!

    PS. Not sure what's going on with the .dl/.dll files in the Umbraco package - if I browse within the ZIP (just Windows Explorer) I see only .dl files - if I extract it I end up with a full set off files with each extension! Weird...

  • Richard Soeteman 3234 posts 9118 karma points
    Sep 30, 2015 @ 09:09
    Richard Soeteman
    0

    Hi Geoff,

    Is it an idea to go through the install tomorrow via Team viewer? Don't have the time today, but tomorrow will be possible.

    Best,

    Richard

  • Geoff Beaumont 59 posts 84 karma points
    Sep 30, 2015 @ 09:46
    Geoff Beaumont
    0

    Hi Richard,

    Happy to if it's helpful - however, I've tracked back and figured out where that old DLL is coming from in my solution.

    I'm using Jeroen Breuer's Hybrid Framework for these sites, and this has the SEOChecker DLLs in it's library of non-NuGet managed dependencies (these are included in even the cut down "clean" version). The DLLs are an out of date version and I hadn't noticed that they were there and not NuGet managed, so I hadn't updated them.

    I would imagine it's highly likely this is also responsible for the issues with installing both the NuGet and Umbraco SEOChecker packages into the site.

    I'll update my Hybrid Framework projects so that they're using NuGet for SEOChecker and also not copying the DLLs locally so they don't interfere with NuGet managing the files directly on the web sites.

    Geoff

Please Sign in or register to post replies

Write your reply to:

Draft