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

Forums / Bugs & Issues / Image Libraries and AOL?

Image Libraries and AOL?

5 posts, 0 answered
  1. Jeff
    Jeff avatar
    27 posts
    Registered:
    18 Jun 2008
    16 Apr 2010
    Link to this post
    We've been trying to diagnose this issue for a while now, and all we can come up with is something is going on inside Sitefinity that's not letting the image libraries work with AOL. I don't know if this is one of your supported browsers, but I just wanted to report the potential bug in case it is a more widespread problem. Also, we only see this happening with our image libraries we use. The rest of the content pages seem fine.

    Our error logging system keeps picking up errors like "The file '/SomeLibrary/SomeImage.sflb.ashx' does not exist.". We've confirmed numerous times the image exists through Sitefinity and it is accessible from the browser by hitting the URL directly from any other browser we support on our end.

    Upon further investigation the user agent always gets logged with AOL listed: "Mozilla/4.0 (compatible; MSIE 7.0; AOL 9.1; AOLBuild 4334.5009; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)". We have yet to find one single occurance where it wasn't, typically we get around 50 of these errors logged per day.

    Here's the exception detail and stack trace if you're interested:

    System.Web.HttpException, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a

       at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath)
       at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
       at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
       at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
       at System.Web.UI.SimpleHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
       at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
       at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


    Any help would be appreciated. Thanks!
  2. Jeff
    Jeff avatar
    27 posts
    Registered:
    18 Jun 2008
    16 Apr 2010
    Link to this post
    I forgot to mention, we're currently using Sitefinity 3.7 SP1

    <meta name="Generator" content="Sitefinity 3.7.2022.2:1" />
  3. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    19 Apr 2010
    Link to this post
    Hello Jeff,

    Thank you for contacting Telerik Support.

    Could you please tell us in which part of the website you are getting this error - is it on the public end or in the administrative area? AOL browser is not supported for working in the back end of a Sitefinity website. Do you reproduce the error on your end using this kind of browser, or you are getting this from the error log from some of your users?

    Thank you for your cooperation in advance.

    Kind regards,
    Radoslav Georgiev
    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.
  4. Jeff
    Jeff avatar
    27 posts
    Registered:
    18 Jun 2008
    19 Apr 2010
    Link to this post
    I checked with our content admin, and none of his team is using an AOL browser to manage content. I also double checked the URL that was being hit which caused the problem, and that was our external address (we have the admin piece running on a separate server). The problem must have been coming from an external request made by a user.

    We have not tried to reproduce the problem as we do not have access to the AOL browsers from our workstations. I looked on their website and their client software seems to be what is causing the problem, not their custom copy of Internet Explorer.
  5. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    19 Apr 2010
    Link to this post
    Hello Jeff,

    Thank you for the feedback.

    I hope you are able to find exactly what is causing issue. I will try to download the AOL browser and see if I can reproduce the error, however I do not have an AOL account and am not sure how successful I will be. If you find any additional information, please feel free to share it with us.

    Sincerely yours,
    Radoslav Georgiev
    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.
Register for webinar
5 posts, 0 answered