Copied to clipboard

Flag this post as spam?

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


  • Amalie Wowern 113 posts 220 karma points
    May 15, 2020 @ 12:10
    Amalie Wowern
    0

    Seo checker redirects not working on existing content

    Hi

    I cant get seochecker to redirect if the page it should redirect from already exist. The live site is hosted on Azure, i have added this to web.config

    <remove name="SEOCheckerValidationqueueModule" />
    <add name="SEOCheckerValidationqueueModule" type="SEOChecker.HttpModules.ValidationqueueModule, SEOChecker" />
    <remove name="SEOCheckerUrlModule" />
    <add name="SEOCheckerUrlModule" type="SEOChecker.HttpModules.UrlModule, SEOChecker" />
    

    I have allowed redirect from nodes that exist in settings

    On my test site there is hosted locally it works.

    Could it be something with azure

    im using umbraco 7.11.1

  • Richard Soeteman 3855 posts 11975 karma points MVP
    May 18, 2020 @ 06:48
    Richard Soeteman
    0

    Did you enable Redirect when node exists in the seochecker settings?

  • Amalie Wowern 113 posts 220 karma points
    May 18, 2020 @ 06:57
    Amalie Wowern
    0

    Yes i have enabled "redirect when node exist"

  • Richard Soeteman 3855 posts 11975 karma points MVP
    May 18, 2020 @ 07:13
    Richard Soeteman
    0

    Other redirects work?

  • Amalie Wowern 113 posts 220 karma points
    May 18, 2020 @ 07:23
    Amalie Wowern
    0

    Yes redirects for urls for nodes that is not existing works

  • Elise Godskesen 6 posts 86 karma points
    Oct 27, 2020 @ 09:00
    Elise Godskesen
    0

    I have the same situation but for Umbraco 8 ->

    • Umbraco's version: 8.6.4
    • SEO Checker's version: 2.9.5
    • Enabled"Redirect when node exists": Yes.
    • Live site is hosted on: Azure
    • web.config setup snippet as described in the first post by Amalie:
      yes.

    It works only if you put redirect to a root node. Otherwise, it does not work, sometimes even if you unpublish the node (then it is the ordinary 404; but this behavior is inconsequential, I cannot reliably reproduce it). Also, if you put first a redirect from Node1 to a root node, then delete this redirect, and add a new redirect from Node1 to Node2, then Node1 still redirects to a root node. There are no error in console when redirects are added, deleted, edited, except for when you try to redirect to a node that already redirects somewhere else. Then you get:

    TypeError: can't assign to property "url" on "<!DOCTYPE html>\r\n\r\n<html lang=\"sv\">\r\n<head>\r\n  <meta charset=\"utf-8\" />\r\n  <meta name=\"viewport\" content=\"width=device-width\" 
    

    In logs we get (I suspect though that it might be related to when you try to redirect to a node that already redirects somewhere else?):

    SEOChecker: SEOChecker: Error in UrlRewriteRedirectsProvider for url rewriting
    System.Threading.ThreadAbortException: Thread was being aborted.
    
       at System.Threading.Thread.AbortInternal()
    
       at System.Threading.Thread.Abort(Object stateInfo)
    
       at System.Web.HttpResponse.AbortCurrentThread()
    
       at System.Web.HttpResponse.End()
    
       at System.Web.HttpResponse.Redirect(String url, Boolean endResponse, Boolean permanent)
    
       at SEOChecker.Providers.UrlProviders.UrlRewriteRedirectsProvider.RewriteUrl(UrlBuilder builder, UrlRewriteConfiguration config)
    
  • Richard Soeteman 3855 posts 11975 karma points MVP
    Oct 27, 2020 @ 09:38
    Richard Soeteman
    0

    Do you have any more info about the Url Property error? The other error is the redirect, error should be catched but is an asp.net issue.

  • Elise Godskesen 6 posts 86 karma points
    Oct 27, 2020 @ 10:23
    Elise Godskesen
    0

    Thank you for the quick reply! We just realized that the "TypeError: can't assign to property "url" on..." is specific to Firefox browser (82). On Chrome (86) it does not appear.

    Here is what we are trying to do:

    • Create a redirect from domain.com/page-1 to domain.com

    • Then create a redirect from domain.com/page-2 to domain.com/page-1

    on Firefox: You cannot even add the /page-2 path to /page-1 (while using SEO Checker Data Type), the TypeError appears in the console.

    on Chrome: goes well without errors in the console.

    If you do changes in Chrome, but then open /page-2 for editing in Firefox, then the following appears in the Firefox's console (but did not appear before changes were made through Chrome):

    Possibly unhandled rejection: {"errorMsg":"Failed to retrieve update status","data":"The page cannot be displayed because the expectation failed.","status":417}
    

    with 417 Invalid token server response on

    /umbraco/backoffice/UmbracoApi/UpdateCheck/GetCheck
    /umbraco/backoffice/UmbracoApi/Tour/GetTours
    /umbraco/backoffice/UmbracoApi/Content/AllowsCultureVariation
    /umbraco/backoffice/UmbracoApi/Content/AllowsCultureVariation
    

    Is there any other type of information that would be useful for you?

Please Sign in or register to post replies

Write your reply to:

Draft