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

Forums / General Discussions / Locked down page not showing up in sitemap

Locked down page not showing up in sitemap

3 posts, 0 answered
  1. Darth Obiwan
    Darth Obiwan avatar
    4 posts
    Registered:
    25 Jun 2009
    11 Aug 2009
    Link to this post
    I created my own role and membership providers and they work very well in sitefinity but I'm getting an issue with the SiteMap. I have a set of pages that are only allowed to be accessed by logged in users, I want the links to show for the pages and then have it redirect them to login if they go to those pages. But instead it is not showing the pages in the menu at all.

    When using a .sitemap file this can be accomplished by setting  securityTrimmingEnabled="false" in the web.config. This setting doesn't seem to be listened to by the CmsSiteMapProvider


  2. Darth Obiwan
    Darth Obiwan avatar
    4 posts
    Registered:
    25 Jun 2009
    11 Aug 2009
    Link to this post
    I just noticed that it's doing this on any links in generic content too. There's gotta be a setting I'm missing. Any pages I link to in generic content that are set to deny anonymous I get
    <a href="Item not found: [Sitefinity]1d19a6bb-123a-4873-9bb1-219c038cc5ab"> if I turn anonymous access back on it links correctly.


  3. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    14 Aug 2009
    Link to this post
    Hi Darth Obiwan,

    This time I understood correctly what you mean :)

    In order to show secured pages in the sitemap (such which denied anonymous checked), add the following Sitemap Provider setting:
    web.config
    <siteMap defaultProvider="CmsSiteMapProvider" enabled="true" > 
          <providers> 
            <clear/> 
            <add name="CmsSiteMapProvider"  
             showSecured="true"  
             description="Displays Cms Pages" 
             type="Telerik.Cms.Web.CmsSiteMapProvider"/> 
          </providers> 
        </siteMap> 

    As for the second problem, it has been fixed in Sitefinity 3.7. You should not face it when you upgrade to that version.

    Greetings,
    Georgi
    the Telerik team

    Instantly find answers to your questions on the newTelerik Support Portal.
    Check out the tipsfor optimizing your support resource searches.
Register for webinar
3 posts, 0 answered