+1-888-365-2779
Try Now
More in this section

Forums / Deployment / Error when deploying external site as sub-site of Sitefinity site

Error when deploying external site as sub-site of Sitefinity site

4 posts, 0 answered
  1. Scott McNeany
    Scott McNeany avatar
    44 posts
    Registered:
    09 Mar 2010
    11 Aug 2010
    Link to this post
    Hello,

    I'm receiving a strange error, and the details are below. It seems to be an issue with the Telerik WebResource handler, but I posted it on the main Telerik forum, and they've referred me here. The original post is at http://www.telerik.com/community/forums/aspnet-ajax/ajax/where-do-i-put-the-radscriptmanager-or-scriptmanager.aspx.
    Below is my dilema:

    Posted on Jul 30, 2010 (permalink)

    I am getting the below error when wrapping my <system.webServer> section with a
    <location path="." inheritInChildApplications="false"> . I did this because I have a Sitefinity site at the root with a non-Sitefinity site in a virtual directory below it. I don't want my sub-application inheriting the configuration, because it doesn't have the necessary DLLs to interpret the handler declarations. When I remove the 'location' tag, my root application works just fine, but my sub-application breaks because of the inherited handlers.

    ~/Telerik.Web.UI.WebResource.axd' is missing in web.config. RadScriptManager requires a HttpHandler registration in web.config. Please, use the control Smart Tag to add the handler automatically, or see the help for more information: Controls > RadScriptManager


    Posted on Aug 2, 2010 (permalink)

    Sebastian,

    Thank you for your help. Basically, Application A (Sitefinity site at the root of the IIS 7 site) works correctly WITHOUT the location tag in its web.config file. The error I get when I add the location tag is what I posted in my previous comment.

    However, Application B (non-SF site as a sub-application) only works WITH the location tag in place, because it does not have the DLLs necessary to understand the handlers.

    I DO want to have the location tag in place, because it keeps Application B separate from anything I configure at the root.
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    12 Aug 2010
    Link to this post
    Hi Scott McNeany,

    You could try to use <clear> or <remove> tags before the handlers, because it looks like the inheritance still persists in some aspects.Make sure that the handler is registered correctly - you can refer to General Troubleshooting. Try adding and removing the assembly version in the handler - it should match Telerik.Web.UI version. Here is some more details about registering RadScriptManager

    Kind regards,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Dustin
    Dustin avatar
    14 posts
    Registered:
    14 Jun 2011
    14 Jul 2011
    Link to this post
    Sorry to dig up an old thread, but I am trying to set up a Sitefinity demo site and am running into the same issue that Scott described above. Sitefinity is my root site and I have another application directly below it. I'm using the location tag with inheritInChildApplications=false around the System.Web and System.WebServer sections of my sitefinity web.config file. With this setup, my sub-application works properly and I can view my sitefinity site correctly, but it errors when I try to navigate to the sitefinity login page. The error that I'm receiving is as follows:

    '~/Telerik.Web.UI.WebResource.axd' is missing in web.config. RadStyleSheetManager requires a HttpHandler registration in web.config. Please, use the control Smart Tag to add the handler automatically, or see the help for more information: Controls > RadStyleSheetManager



    Has there been a resolution to this issue?

    Thank you for your help.

    Dustin
  4. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    19 Jul 2011
    Link to this post
    Hello Dustin,

    I have managed to run a Sitefinity website by simply adding remove statements in the httpModules and modules config sections for the Sitefinity related modules. This was done in the child application's web.config.

    Additionally I have locked some sections (not necessary) to illustrate how this will work (you should not lock system.web/httpHandlers, system.webServer/handlers, system.web/httpModules and system.webServer/modules.

    I have attached both web.configs for reference.


    Greetings,
    Radoslav Georgiev
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Register for webinar
4 posts, 0 answered