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

Forums / Security / ASP.NET Workaround and Localization

ASP.NET Workaround and Localization

3 posts, 1 answered
  1. Will
    Will avatar
    23 posts
    Registered:
    30 Jun 2009
    21 Sep 2010
    Link to this post
    We have implemented the workaround posted by Scott Guthrie on a number of sites. We encountered a challenge with one site that utilizes localization though. This site adds /en/ to the path of all pages and does not find the error page correctly. We tried adding /en/ to the path to the error page, but we are still having a problem.

    Any suggestions?

    Thanks,
    Will
  2. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    22 Sep 2010
    Link to this post
    Hello Will,

    Thank you for using our services.

    Can you please let us know which version of Sitefinity are you using? This should not be a problem in the latest versions of Sitefinity (after Sitefinity 3.7 SP1). If they are regular .aspx pages in the root of your website you will have to create a directory for each of your languages and copy the pages for each language. For example for English you will have to create an en folder in the root of your website and add the error pages there.

    You can alternatively create your error pages in the CMS. For example create them in the root of the site map for each language version and then set them in the custom errors configuration section similarly to the markup bellow:
    <customErrors mode="On">
        <error redirect="404.aspx" statusCode="404"/>
    </customErrors>

    I have created a page called 404.aspx in the root of my CMS sitemap and set it to be non navigable.
     
    Best wishes,
    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
    Answered
  3. Will
    Will avatar
    23 posts
    Registered:
    30 Jun 2009
    22 Sep 2010
    Link to this post
    Radoslav,
    Thanks for your help. We ended up remedying this a different way, using the website configuration. Thank you for your suggestions though. Some of them were already in place and may have contributed to the solution.
    Will
Register for webinar
3 posts, 1 answered