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

Forums / Bugs & Issues / SiteMapNode - Did the sitemap provider change?

SiteMapNode - Did the sitemap provider change?

7 posts, 0 answered
  1. Ben Alexandra
    Ben Alexandra avatar
    215 posts
    Registered:
    15 Sep 2012
    15 Oct 2007
    Link to this post
    Hi,

    On many of my sites we have nodes, such as Contact Us listed under various sections.  One is an actual page, the others are just External Pages pointing to that page.  So, under About us we might have a page "contact_us.aspx" and then under Home there might be an External Page that points to ~/about_us/contact_us.aspx.

    In code I then use:

    SiteMapNode smn = SiteMap.CurrentNode;

    And then set menus and other items based on smn.  This used to work perfectly and if you went to Contact Us from under the Home menu it would jump to the About Us menu and highlight it correctly.  That's how I wanted it to work and how it's been all along.  Made sense and worked.

    In Sitefinity 3.1 the sites suddenly behave differently and the smn it uses isn't necessarily the Primary (actual) page, but seems to sometimes show the pointer pages.  So if there were 1 Contact Us page and 3 pointer pages that go to that page, that last one of those pages (be it the real or the pointer page) would be the selected one.

    I guess what i'm saying is that it now seems to consider real and pointer pages identical and the menus being shown are not really the way they should be.

    Let me give a specific example that you can see: http://76.12.13.117/images/sitemap.jpg
    <img src=http://76.12.13.117/images/sitemap.jpg>

    In this example the page is under Home, but you can see that it uses the Support > Contact Us as the current node and for the left menu, even though it should be Home.  Hope that makes sense.

    Is there a work around?  Was there a reason you changed how it worked?  In 3.0 and SP2 it would show up as Home, not Support.

    Thanks!

    Ben
  2. Slavo
    Slavo avatar
    295 posts
    Registered:
    24 Sep 2012
    17 Oct 2007
    Link to this post
    Hello Ben Alexandra,

    Thank you for reporting this issue. You are right, for version 3.1 we fixed some bugs in our Sitemap provider and this occurs only after our changes. The issue will be fixed for the service pack coming out next week.
    You Telerik points have been updated!

    Best wishes,
    Slavo
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  3. Ben Alexandra
    Ben Alexandra avatar
    215 posts
    Registered:
    15 Sep 2012
    17 Oct 2007
    Link to this post
    Great.  Do you have a target date for the release?  End of next week?

    I know if the past you've done hot-fixes that just have the /bin/ and /sitefinity/ folders mainly.  Have you considered doing a release that JUST has the required changed files?  So even just the .dlls that have changed between 3.1 and 3.1 SP1 and maybe a few files in the /sitefinity/ folder that have changed too.

    Just wondering if that's something you've considered.

    Also, do you know when the Prometheus version of the editor will be incorporated into Sitefinity?

    I know these might not be the best questions for this thread, but just curious.

    Thanks

    Ben
  4. Slavo
    Slavo avatar
    295 posts
    Registered:
    24 Sep 2012
    17 Oct 2007
    Link to this post
    Hi Ben Alexandra,

    We haven't set an exact date for the service pack. Currently we are working on known issues and our goal is to fix as many as possible, so yes, it would be about the end of next week. We will provide both an installer and a hotfix containing only new functionality. The hotfix is a zip file with the /bin and /Sitefinity folders only, so you would be able to upgrade existing projects easily without reinstalling.
    The integration of Prometheus controls in Sitefinity is scheduled for version 3.2 after the service pack.

    Regards,
    Slavo
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  5. Ben Alexandra
    Ben Alexandra avatar
    215 posts
    Registered:
    15 Sep 2012
    24 Nov 2007
    Link to this post
    Hi,

    I've upgraded to 3.1 SP1 and this issue of the sitemap seems to persist. 

    The essence of the problem is that SF now recognizes pointers to external pages as being the actual page.  So if there's a pointer to ~/contact_us/index.aspx under Support that points to the REAL page under Home, the sitemap now returns the Pointer node as the current node, not the REAL page. See the image I referenced (The image is now here: http://www.trakkware.com/images/sitemap.jpg)

    I hope this can be fixed by SP2, as I have a lot of clients who use external pages to reference other pages in their own sites and now they're all getting messed up (their navigation is showing your in the wrong section just because they happen to have a pointer in that section).

    Thanks, and please let me know the plan

    Ben
  6. Ben Alexandra
    Ben Alexandra avatar
    215 posts
    Registered:
    15 Sep 2012
    24 Nov 2007
    Link to this post
    Oh, and also, have you considered a hot-fix that ONLY has the necesary/changed files.  So, for example, from 3.1 SP1 to SP2.  It might only have 5 .dll files and 3 or 4 files for the /Sitefinity folder (instead of the whole /bin and /Sitefinity folders.  This is mainly an issue of knowing what to update locally, in Source Safe and online.  FTP'ing the whole /bin and /sf folder isn't a huge deal, but just updating 6 or 7 files would be easier ;)

    Do you have updated dates for 3.2 and 4.0?  They both look like they have amazing stuff in them, and I know we're all excited.

    Thanks so much for all your hard work.  Loving working with Sitefinity (the product and the team ;)
  7. Slavo
    Slavo avatar
    295 posts
    Registered:
    24 Sep 2012
    27 Nov 2007
    Link to this post
    Hi Ben Alexandra,

    After investigating the issue for a while, I could only reproduce it in Site PanelBar. The problem does not come from the provider itself, as SiteMap.CurrentNode always returns the actual page, not the external one. It appears that the issue occurs only if Site PanelBar is configured to persist its state in a cookie. Then, probably even after the redirection to the actual page is done, the state is loaded from the cookie resulting in the wrong node highlighted. A workaround for the moment is marking nodes as selected in the PanelBar manually using the SiteMap, instead of relying on the Panelbar itself. In the screenshot you've sent I also saw you are using a TabStrip or Menu (not sure which), but i could not reproduce the issue with them.

    I would like to ask you to test with the rest of the navigation controls (except PanelBar), and if the issue persists, let us know or send a project where we can observe this behavior, so that we can investigate it further. Please excuse us for the inconvenience.

    Sincerely yours,
    Slavo
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
Register for webinar
7 posts, 0 answered