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

Forums / Developing with Sitefinity / Path Separator

Path Separator

10 posts, 0 answered
  1. mexner
    mexner avatar
    98 posts
    Registered:
    06 Apr 2006
    16 Sep 2008
    Link to this post
    Just upgraded our project to 3.2.1616. After I made some changes to the web.config, I'm getting page not found errors.

    I've narrowed it down to the pathSeparator setting in the web.config

    <cms defaultProvider="Sitefinity" pageExtension=".aspx" projectName="Moms Best Friend" pathSeparator="-" disabled="false" pageEditorUIMode="Overlay">
       
    If I change the pathSeparator back to "/", everything works great. This goes for new and existing pages.

    This was previously documented in a post I started here. Has it been broken again?

    This is a critical "need" of my client, do you have an immediate fix?
    Thanks,

  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    12 Sep 2017
    17 Sep 2008
    Link to this post
    Hi CHRIS mechsner,

    Thank you for your question.

    This issue has been fixed in the latest release 3.2 SP2 hotfix1616. I have just tried to reproduce any error using pathSeparator"-" and there are no error messages. Could you confirm that you have successfully upgraded your project?  You can check your current version by loading a Sitefinity page through the browser and get its Generator metatag content value.
    <meta name="Generator" content="Sitefinity 3.2.1616.2:0"
    Please note that you should not use the same symbols in the URL as those you use for pathSeparators. If your urls contain "-" a error page will be displayed.

    Let us know if this helps.

    Kind regards,
    Ivan Dimitrov
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  3. mexner
    mexner avatar
    98 posts
    Registered:
    06 Apr 2006
    17 Sep 2008
    Link to this post
    Indeed I do have the latest version
    <meta name="Generator" content="Sitefinity 3.2.1616.1:0" />

    I think the problem I'm having is answered with your last statement.

    "
    Please
    note that you should not use the same symbols in the URL as those you
    use for pathSeparators. If your urls contain "-" a error page will be"

    My Client has created several alternate URL's that do include the "-"
    that we are using as the path seperator.

    We'll take it from here, but is that something that will be fixed in future
    releases?

    Seems this situation could happen quite frequently...and to others.

    Thanks for the info and quick turn-around!
    displayed.


  4. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    12 Sep 2017
    18 Sep 2008
    Link to this post
    Hello CHRIS mechsner,

    We will try to come up with a solution in one of the next releases or update the troubleshooting section for this scenario.

    Best wishes,
    Ivan Dimitrov
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  5. mexner
    mexner avatar
    98 posts
    Registered:
    06 Apr 2006
    30 Sep 2008
    Link to this post
    Hi Ivan, I've had some developments with this thread that I would like to share, but first some recap.

    If we have the following page structure....

    Corporate
       - home
       - about
       - press
    Cities
       - city1
            -sub1
            -sub2
       - city2
            -sub1
            -sub2

    My client has requested that we do NOT have the default path seperator "/". They have hired an SEO company and want all the urls to be formatted like this

    http://www.domain.com/corporate-home.aspx
    http://www.domain.com/cities-city2-sub1.aspx

    Essentially making every page of the site be at the root level. No nesting!

    This was working great before we upgraded to the latest version, 3.2.1616.  However, now that we are on 3.2.1616, this functionality has been broken.

    I previously stated that we get an error. That wasn't entirely true. Rather, if we navigate the site, some URL's work, others do not. I can't find a common reason as to why some do and some don't work. The "error" that we get is

    The resource cannot be found.

    Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.

    Requested URL: /Corporate/Press-Room/Press-Room.aspx


    just a standard 404. Our site has over 1,000 pages. And our client has been very methodical about creating additional page URL's for most pages in the site. Sometimes up to 6 per page.

    A standard "additional page url" might look something like this....
    ~/coroporate-homepage.aspx
    ~/corporate-landing.aspx
    ~/corporate-default.aspx


    Do you have any suggestions or work arounds? I will be more than happy to provide the solution if you request.
    Thanks,


  6. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    12 Sep 2017
    01 Oct 2008
    Link to this post
    Hi CHRIS mechsner,

    Thank you for contacting us.

    It is not possible to have the same path separator symbols in the URL as those you use for pathSeparators. The application cannot treat them as a different signs - as path separator and part of the url. This is the reason for the error 404 at your end ( the error will not occur if pathSeparator="/" in the web.config). Please find the attached screenshot. We suggest that you should you use "/" as a path separator. In our future releases "/" will be the only available path separator option.

    In your three examples, no one of the pages contain "-", so it will not be a problem to create them using "-" as a path separator. I created the same scenario and it works.


    Hope this gives you some light.

    Sincerely yours,
    Ivan Dimitrov
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  7. mexner
    mexner avatar
    98 posts
    Registered:
    06 Apr 2006
    01 Oct 2008
    Link to this post
    Hi Ivan, thanks for the quickly reply and your response. I appreciate it. My only hesitation to your answer is that it DID previously work before upgrading.  Are you saying that the in-ability to have the same path separator symbol in the URL as those used for pathSeparators is NEW functionality implemented with 3.2.1616? Thus breaking what was working in the previous version? If your not saying that, then I may not be clearly explaining my problem.


    Also you mentioned that the ability to specify a path separator will be depricated in future versions. Can I ask why that functionality is being removed?

    And do you have a work around to keep this functionality if we choose to upgrade to future versions?

    Thanks again,
  8. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    12 Sep 2017
    06 Oct 2008
    Link to this post
    Hi CHRIS mechsner,

    Thank you for getting back to us.

    We have changed the url logic, because of many additional problems that different path separators could cause. We were forced to limited the pathSeparator delimiter characters in the releases after 3.2 SP1 due to parser issues.

    Best wishes,
    Ivan Dimitrov
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  9. Richard Baugh
    Richard Baugh avatar
    201 posts
    Registered:
    22 Aug 2012
    14 Nov 2008
    Link to this post
    We have run into another issue. If you use the dash as the path separator, then the ContentView's detail will not work.

    If you add a NewsView to a page and your pathSeparator is set to a dash, the list of items will display. However, when you click on an item to view the details, it throws a 404 error. Changing the pathSepeartor back does fix this, but we have a site that was already built out and has done a lot of SEO work so this really isn't a solution for us.

    At first I thought it was do to us upgrading a 3.2 site to 3.5 SP2, but a base project is also doing this.
  10. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    12 Sep 2017
    18 Nov 2008
    Link to this post
    Hello Richard Baugh,

    In Sitefinity 3.5, slash is the default path separator and it cannot be changed. In your case you could use advanced url rewriter to override the links.

    Kind regards,
    Ivan Dimitrov
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Register for webinar
10 posts, 0 answered