Site Structure URL pointing. - General Discussions - General Discussions - Progress Community
 General Discussions

Site Structure URL pointing.

  • Site Structure URL pointing.

  • I am contemplating migrating my existing custom site to Sitefinity 4 and have the following question regarding site structure.

    One of my existing pages (sections) has a fair whack of incoming links and many hundreds of pages within so I do not want to redirect it to a new url, 

    The existing URL would be for argument sake.

    ~/blog/

    In the site in sitefinity, I would want the Blog page (section) to appear as a sub page of anotherpage within all site navigation (sitemap) but wish it to retain its existing URL.

    So in the sitemap I wish to structure it as   resources > blog 

    however url wise i wish it to retain the existing url of  ~/blog/, however when i try to add it as a sub page of the resources page it always tries to change the url to ~/resources/blog/  which i cannot allow.

    Any advice on how to accomplish this?





  • I'm starting to think that this isn't possible and that I am going to have to write a lot of  funky REG-EX redirects to do some mapping of old to URL's to new ones if there is no other way of achieving this.

    Can anyone save me from REGEX Hell ?
  • Hi Stephen,

    Thank you for using our services.

    We had a url rewrite module in Sitefinity 3.x which would handle such requests. However we have decided not to introduce on in Sitefinity 4.0 as the one built in IIS is much more flexible and usable. You can check it out here: http://www.iis.net/download/urlrewrite.
    Greetings,
    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
  • Dear Radoslav

    Some of us are on shared hostings and have not to much access to IIS.

    Markus
  • Hello Markus Berchtold,

    Thank you for joining the conversation.

    Can you confirm that on shared hosting the hoster does not allow you to use the UrlRewrite module of IIS? Generally UrlRewrite module can be configured from web.config, also rewrite rules are configured from web.config. So basically if your hosting service provider has the module installed you should not need access to IIS to configure it.

    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
  • Is the IIS URL Rewrite Module only in IIS 7?
  • Hello greg,

    Microsoft URL Rewrite Module requires IIS 7.You can take a look at System Requirements section for URL Rewrite Module

    Regards,
    Ivan Dimitrov
    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
  • We won't be using IIS 7 on our web server.

    Is it possible to use the ASP.NET4.0 URL Rerouting by putting code in the global.asax file like this?

    		protected void Application_Start(object sender, EventArgs e)


    RegisterRoutes(RouteTable.Routes);


    void RegisterRoutes(RouteCollection routes)

    routes.MapPageRoute("PromoRoute",
    "test""~/promo");
  • Hi greg,

    Yes you can use custom route handlers that registered in Global.asax in Application Start event handler. As a matter of fact that is what we use in Sitefinity to serve the dynamic pages - we rely heavily on the ASP.NET 4.0 Route handlers. We are also going to release a url rewrite module in Sitefinity which is going to use the route handling to handle alternative urls.

    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
  • Thanks. Is this working in the RC?
  • Hello greg,

    In the RC there is no UrlRewrite module. We are going to work on UrlRewrite module Q1/Q1 2011

    All the best,
    Ivan Dimitrov
    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
  • Hi,

    please provide status on the URL rewrite and would be great to have a simple sample when available.

    Thanks,
    JH
  • Hi JH,

    With the Q1 2011, we are going to provide new page types, and API for working with rewriting of URLs. Here is the list of pages types coming: 

    1. "Standard": Standard page with page data.
    2. "Group": Group page without page data.
    3. "External": External aspx page from the file system. It's outside of Sitefinity but it is inside of the web site. The page node has a page data object with ExternalPage property set.
    4. "InnerRedirect": Redirect inside of Sitefinity (redirecting page). The page node has no page data but keeps the id and the provider of another page node (linked page). It uses the lifecycle and multilingual versions of the linked page. A request to the URL of this page performs permanent redirect to the linked page. In the navigation control the URL of the linked page is rendered instead of the URL of the redirecting page.
    5. "OuterRedirect": Redirect outside of Sitefinity. The page node has no page data and permanently redirects to a page from the web. The URL of the linked page is stored in the RedirectUrl property of the PageNode. Supports multilingual, i.e. different URLs for the different languages.
    6. "Rewriting": Rewrite inside of Sitefinity. Same as InnerRedirect but loads the page data of the linked page, i.e. the page data is reachable by two URLs. Accessible only through API.

    Greetings,
    Georgi
    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
  • Dear Georgi

    Once again great news.

    You might want to think about the naming having non technical end users in mind.

    - Normal Page (displays own content)
    - Page Group (redirects to its first subpage)
    - Internal Sitefinity Link (links to a Normal Sitefinity Page)
    - Internal Link (links to a page outside Sitefinity but withing the own domain: .aspx, .html )
    - Externel Link (links to any page of the web: http://www...   )

    Or anyhting like it. I guess your UI team will work something out - Just keep endusers in mind :-)

    Markus