Forums

Home / Developer Network / Forums / Sitefinity Older Versions (3.x): Developing with Sitefinity > Extensionless URLs in Sitefinity 3.6

• David

  Posted on Apr 6, 2009 (permalink)

  Hi,
  
  I am using the latest version of Sitefinity (3.6.1870). According to this post (http://blogs.sitefinity.com/Ivan/Posts/09-02-12/Sitefinity_3_6_released.aspx) there are now extensionless URLs.
  
  How do I use extensionless URLs? The documentation (http://www.sitefinity.com/support/documentation.aspx) is still for 3.5.
  
  I have a site that is made up of microsites and want to create URLs like these:
  http://www.mysite.com/
  http://www.mysite.com/site1/
  http://www.mysite.com/site2/
  
  I do not want each microsite landing page to have a filename. So this is wrong:
  http://www.mysite.com/default.html
  
  I have amended:
  <cms defaultProvider="Sitefinity" pageExtension=".aspx"
  to be:
  <cms defaultProvider="Sitefinity" pageExtension=".html"
  
  Thanks
  Dave Cooper

  Reply

• Georgi Georgi

  Posted on Apr 6, 2009 (permalink)

  Hello David,
  
  This part of the documentation is not changed, but it applies for version 3.6 as well.
  
  Basically you need to take the following steps:
  
  1. Set the customErrors properties in the web.config file like:
  

  <customErrors mode="On">

  <error redirect="~/Sitefinity/nopermissions.aspx" statusCode="403" />

  <error redirect="~/sf404.aspx" statusCode="404" />

  </customErrors>

  
  Sf404.aspx is an internal Sitefinity page. If I should be honest, it is not even a page, but Sitefinity is handling the requests having sf404.aspx, and knowns that the user want to use extensionless urls.
  
  You can do the same in IIS, instead of the web.config file.
  
  2. You will now notice that you can perform requests as the following:
  http://site.com/page1
  http://site.com/group/pagex
  
  3. If you want your Sitemap links to be generated without extension as well, you should set the pageExtension property to empty string:
  

  <cms defaultProvider="Sitefinity" pageExtension="" ..

  
  Give a try to this approach, and let me know if this is the behavior you expect.
  
  Greetings,
  Georgi
  the Telerik team

  
  Check out Telerik Trainer , the state of the art learning tool for Telerik products.

  Reply

• David

  Posted on Apr 6, 2009 (permalink)

  Thanks for the reply.
  
  The behaviour is not quite right. The issues I have are:
  
  1. The home page redirects from "/" to "/default.html"
  
  2. The pages do not work correctly if the URL ends in a slash. I have seen a post that gives a solution to this but even with this solution the CSS file added as part of the theme have the wrong path so the page looks wrong.
  
  Any help is appreciated.
  
  Thanks
  Dave Cooper
  

  Reply

• Adam @Habanero

  Posted on Apr 6, 2009 (permalink)

  If we change the cutom errors 404 to redirect to sf404.aspx, can we still somehow wire up a custom error page?

  Reply

• David

  Posted on Apr 7, 2009 (permalink)

  Hi,
  
  I have continued to look into URL rewriting with Sitefinity and although I have a lot of respect for how Sitefinity does a lot of things, I must say that the URL rewriting aspects are not good at all. I can report the following bugs:
  
  1. When changing the pageExtension attribute in the web.config, the cms will break with the error message "telerik.cms is undefined"
  
  2. Also after making the above change the homepage of the site can no longer be accessed using "/" but needs to be "/home.html"
  
  3. When extensionless URLs are used the stylesheets added in by .NET from the themes folder no longer work. The URL to them are now wrong so extensionless URL rewriting is useless.
  
  The only thing I need to fix is number 3, the aspx to html thing I can do custom rewriting. I think that what needs doing is that Sitefinity is now handling the rewriting of the URLs that end in / but you need to use the RewritePath overload as described here: http://msdn.microsoft.com/en-gb/1kz7fdx9.aspx so that the path to the theme css is not broken.
  
  Thanks
  

  Reply

• David

  Posted on Apr 7, 2009 (permalink)

  Since the elegant solution to this problem is not possible since the code I need to change is compiled away, I have written a work-around that is not great but it works:
  
  protected override void Render(HtmlTextWriter writer)
      {
          if (Request.RawUrl.EndsWith("/"))
          {
              RecurseControls(Page.Controls);
          }
  
          base.Render(writer);
      }
  
      private static void RecurseControls(ControlCollection controls)
      {
          foreach (Control control in controls)
          {
              HyperLink anchor = control as HyperLink;
  
              if ((anchor != null) && anchor.NavigateUrl.StartsWith("~/"))
              {
                  anchor.NavigateUrl = anchor.NavigateUrl.Substring(1);
              }
              else
              {
                  HtmlLink link = control as HtmlLink;
  
                  if ((link != null) && link.Href.StartsWith("~/App_Theme"))
                  {
                      link.Href = link.Href.Substring(1);
                  }
              }
  
              RecurseControls(control.Controls);
          }
      }
  
  Thanks
  Dave Cooper
  

  Reply

• Gabe Sumner MVP

  Posted on Apr 7, 2009 (permalink)

  Hey Dave,
  
  Thanks so much for your contributions to this thread!  I've been interested in the extensionless URLs topic for awhile.
  
  Georgi, I tried using an empty string for the pageExtension property:
  
  <cms defaultProvider="Sitefinity" pageExtension="" ...
  
  In my example, this broke the entire web site.  All web pages return the following error:
  
  

  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: /standard-3.6/sf404.aspx
  
  I'm probably doing something wrong, but I've had no luck with this.  Thoughts?
  
  Gabe Sumner
  http://www.sitefinitywatch.com/

  Reply

• Nikolai Nikolai

  Posted on Apr 8, 2009 (permalink)

  Hello,
  
  Could you please try this:
  1. Leave this <cms defaultProvider="Sitefinity" pageExtension="" as it is.
  2. Open IIS and map a custom error page for the 404 error handling like this /[YourProjectName]/sf404.aspx
  
  By taking these steps, you will be able to use extensionless URLs. Your links will be generated without extensions as well.
  
  Sincerely yours,
  Nikolai
  the Telerik team

  
  Check out Telerik Trainer , the state of the art learning tool for Telerik products.

  Reply

• Mark

  Posted on Jun 27, 2009 (permalink)

  Hello,
  
  I would like to use extensionless URL and I have set pageExtension="" in the web.config.
  
  Now if I try to create a new page or edit an existing one I am redirected to the login page, even though I am logged in already. If I try to log in again I am still redirected to the login page.
  
  Have you heard of this and can you suggest a reason/solution?
  
  Regards,
  Mark.
  

  Reply

• Vlad Vlad

  Posted on Jun 30, 2009 (permalink)

  Hi Mark,
  
  The problem is that FormsAthentication and RoleManager modules are not available for extensionless requests. You can find more details here:
  ASP.NET Integration With IIS 7.0
  

  You could to fix this issue by setting runAllManagedModulesForAllRequests attribute of the system.webServer -> modules element to true in the web.config:
  

  <system.webServer>

  <modules runAllManagedModulesForAllRequests="true">

  Or, you can add the modules manually without precondition:

  <system.webServer>

  <validation validateIntegratedModeConfiguration="false"/>

  <modules>

  <remove name="FormsAuthentication"/>

  <remove name="RoleManager"/>

  <add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule" />

  <add name="RoleManager" type="System.Web.Security.RoleManagerModule" />

  
  Hope this is helpful.
  
  Sincerely yours,
  Vlad
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Check out the tips for optimizing your support resource searches.

  Reply

• Mark

  Posted on Jun 30, 2009 (permalink)

  That worked. Thanks.
  Mark.
  

  Reply

• Richard

  Posted on Dec 8, 2009 (permalink)

  I'm not happy with this functionality so far (in 3.7). I've set up the sf404.aspx workaround and it doesn't quite do what I want. The URL the browser gets is a redirect URL starting with sf404.aspx. That's just a cosmetic issue, but I'm finding that actual "missing" pages come up blank - no 404 error.

  
  

  What I expected to be able to do was set up a page group that would lead to a default page. So I set up a page group called "InfoTours". I set up a sub page "default.aspx". Sitefinity tells me that the page can be accessed at ~/InfoTours/default.aspx. I have IIS set so default.aspx is the default document for the whole site.

  
  

  So currently I can get to this page in the following ways:

  
  

  ~/InfoTours.aspx

  ~/InfoTours/default.aspx

  
  

  What I can't do, that I NEED to do is get to it through:

  
  

  ~/InfoTours/

  
  

  All of our published URLs are in this format.

  
  

  I would like Page Groups to be extensionless, and only Page Groups. Or I would like the application to honor the IIS default document. Or I would like sf404.aspx to allow proper 404 errors (and custom errors as well) when appropriate. Or some better mechanism for extensionless URLs in general. In any case, I need this functionality before I can use the product (which we have purchased a license for). Thanks!

  
  

  
  

  Reply

• Georgi Georgi

  Posted on Dec 9, 2009 (permalink)

  Hello Richard,

  Unfortunately the Extensionless urls could not be limitted to the page groups only. This is a core functionality and could not be changed that easy, but we will definitely put it under question, and perhaps extend it to meet these requirements. 

  By the way, when you append an additional slash (/) at the end, the Url path is changed, at least this is the case by the specifications.

  Which version of 3.7 are you running on?

  
  Best wishes,
  Georgi
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Reply

• Richard

  Posted on Dec 10, 2009 (permalink)

  I am running 3.7 SP2.

  
  

  Please address the rest of my question: 

  Or I would like the application to honor the IIS default document. Or I would like sf404.aspx to allow proper 404 errors (and custom errors as well) when appropriate.

  
  

  The current mechanism for extensionless URLs is not working for me. Is sf404.aspx supposed to return a blank page when the page is not found? It does for me. This makes it unusable.

  
  

  
  

  
  

  
  

  Reply

• Georgi Georgi

  Posted on Dec 11, 2009 (permalink)

  Hi Richard,

  As I mentioned in the previous post, this is the current implementation, it is root implementation and could not be changed easily. What we can do though is to evaluate it again and possibly change it in out future 3.x versions.

  Have you tried to use wildcard mappings, to map all request to Asp.Net?

  
  Best wishes,
  Georgi
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Reply

• Richard

  Posted on Dec 11, 2009 (permalink)

  Thank you for your reply. Wildcard URLs aren't practical as over half my content is old asp pages. sf404.aspx is broken as it returns blank pages for actual 404 errors. This is a serious bug. It appears to me that these are issues that you promised to fix back in 2007 in this thread:

  http://www.sitefinity.com/support/forums/sitefinity-3-x/developing-with-sitefinity/extensionless-urls.aspx

  
  

  I'm sorry but I need this to work now. sf404.aspx must return 404 errors when it is appropriate or (better) redirect to another error page. Since it returns blank pages I would consider that a bug that needs to be fixed rather than a feature request.

  
  

  I have licensed this product and am trying to move my main Web site to it. Without properly functioning extensionless URLs that can't happen. This is a really common, basic requirement for many sites. Nobody who implements a CMS wants to have to change all of their URLs, particularly when they are published in articles, on business cards, etc. Please allocate the necessary resources and resolve this issue.

  
  

  
  

  Reply

• Georgi Georgi

  Posted on Dec 14, 2009 (permalink)

  Hello Richard,

  The sf404 approach works in Classic pipe line mode, but not in integrated mode. The integrated mode works in a very different way, and has wildcard mappings mapped by default - due to the integration between the ASP.NET runtime and IIS, the default integrated pipeline mode handles all requests through a unified pipeline. I am sure there is a way to run both old asp code and to have the rest of the requests mapped to asp.net. 

  The questions is, are you running the application in Integrated Pipeline mode? if this is the case, then sf404 is not used at all. 

  When I use the sf404 approach in a local project (running on IIS7.5, Windows 7), here is what I do:

  1. Set the pageExtension to empty string in the web.config file - ""
  2. Do not add an entry in the web.config in the <customErrors.. section
  3. Set the 404 error page in IIS to Execute the following path /37sp2/sf404.aspx 
  4. Swith to Classic mode 

  If I request a page which does not exist, I get a 404 not found error (coming from Asp.Net, not from IIS!).

  Please let me know about your web.config and IIS settings, as well as if you are running in Classic or Integrated pipeline mode. 

  
  

  All the best,
  Georgi
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Reply

• Richard

  Posted on Dec 14, 2009 (permalink)

  Georgi,

  
  

  Thanks for your reply.

  
  

  The application is running in Classic mode. However, the thread from 2007 referred to a problem when the site was running as the root directory rather than a virtual directory.That is the way my site is configured. IIS is configured with the physical path for the site pointing at the Sitefinity project directory and for the 404 error to go to /sf404.aspx. The extensionless URLs work in this configuration but no error is returned for legitimate 404 errors.

  
  

  If you create a site where the Sitefinity project is the root directory rather than a virtual directory do you still get normal 404 errors?

  Reply

• Georgi Georgi

  Posted on Dec 15, 2009 (permalink)

  Hello Richard,

  I have tested with with a root site as well, but everything is fine. I have attached screenshots for you of all settings that I have done. 

  Best wishes,
  Georgi
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Attached files

  • 404-not-found.png
  • iis-errors-settings.png
  • apppool-settings.png
  • custom-errors-advanced-settings.png

  Reply

• Richard

  Posted on Dec 15, 2009 (permalink)

  Georgi,

  
  

  This is interesting. I still have the same issue, with the same settings as yours. On two different servers. I have done a packet trace and found that the web server is returning a 404 error that has no content, so the page is blank.

  
  

  I will submit a support ticket.

  
  

  Reply

• Georgi Georgi

  Posted on Dec 16, 2009 (permalink)

  Hi Richard,

  All right, let's escalate this to a support ticket. We will follow up there. 

  Kind regards,
  Georgi
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Reply

• Armysniper Intermediate

  Posted on Dec 17, 2009 (permalink)

  This work did not seem to help the issue we have of people requesting the "folder" and not getting anything. I am looking for a way to handle users who are requesting www.mysite.com/jobs (which is a folder) to be taken to www.mysite.com/jobs/default.aspx. 
  
  There are ways to handle this in code with a handler:
  
  http://weblogs.asp.net/scottgu/archive/2007/02/26/tip-trick-url-rewriting-with-asp-net.aspx
  
  or I could handle it in IIS 7 with an extension:
  
  http://www.iis.net/expand/URLRewrite
  
  I would like to avoid that though if I can handle it at the Site Finity level.

  Reply

• Georgi Georgi

  Posted on Dec 18, 2009 (permalink)

  Hello,

  I suggest you trying the following:
  

  You should be working in integrated mode. Set the custom errors showed just like on my screenshot (attached to this post). Create a directory named test, and place a default.htm file inside containing some text. Make sure that the pageExtension property is set to empty string in the web.config file. 

  Now, browse a page from the sitemap, without the extension. You should be able to see it. Try to browse http://localhost/test - you should be able to see the default.htm file contents as well. 

  Sincerely yours,
  Georgi
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Attached files

  • errors.png

  Reply

• Richard

  Posted on Dec 18, 2009 (permalink)

  Georgi,

  
  

  Thanks, that works - except that the detailed errors are more information than I would like to send to users. One of the reasons for going extensionless is to hide the implementation details of the server. The detailed errors give a LOT of information including the physical paths of the files.

  Reply

• J.Hoventer Master

  Posted on Dec 18, 2009 (permalink)

  I must be entirely out of my depth here since I don't know much about IIS's way of handling requests and mapping, but browsing to a directory rather than a page seems to me to be a fundamental requirement for any website albeit CMS or not.

  
  

  For an entertainment company you would absolutely want to be able to promote the URL 

  www.MyEntertainmentCompany.com/movies or 

  www.MyEntertainmentCompany.com/games or

  www.MyEntertainmentCompany.com/books

  
  

  I don't understand where 404 error pages fits into this at all? Sitefinity's motto is that it's very easy for developers to extend, but this seems highly complicated and most certainly unnecessary for a feature that is so commonly used. 

  
  

  Regards,

  Jacques

  
  

  Reply

• Georgi Georgi

  Posted on Dec 19, 2009 (permalink)

  Hello J.Hov,

  Well, it was really hard to have extensionless urls and directory handling in IIS 5/6 and classic pipe line mode. If you dig into the request and their execution path, you will see what I mean. Considering the fact that all pages and sub pages are not physical ones, the 404 error makes perfect sense - you should teach your application how to handle it. Instead of writing this from scratch, we are providing it and its ready to use. 

  Try to write an application for classic mode, with dynamic pages saved in database, and try to handle extensionless urls having in mind directories. Needless to say, we would be glad if you could share your experience - perhaps there is a better way of handling this scenario. 

  Greetings,
  Georgi
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Reply

• J.Hoventer Master

  Posted on Dec 19, 2009 (permalink)

  Hi Georgi,

  
  

  Thanks for your comments. 

  
  

  1. Does what you say apply to the IIS standard method of dealing with 'default' files where http://www.mysite.com/movies/ is redirected to http://www.mysite.com/movies/default.aspx? 

  
  

  2. When you say it's difficult to achive does this mean it's something that is going to take a long time to bring into the 'easily configurable' feature set of Sitefinity? 

  
  

  Regards,

  Jacques

  Reply

• Georgi Georgi

  Posted on Dec 19, 2009 (permalink)

  Hello J.Hov,

  The answer is Yes, to both questions. This is only valid for IIS5/6 and IIS7 in Classic pipeline mode. IIS7 Integrated mode is different story - the 404 errors are not used at all to handle the files and directories correctly.

  All the best,
  Georgi
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Reply

• Richard

  Posted on Dec 19, 2009 (permalink)

  It appears to me that Sitefinity's extensionless functionality is similar to what's described in this article:

  
  

  http://www.codeproject.com/KB/aspnet/extensionless.aspx

  
  

  Particularly when I look at the following code. I do get proper 404 errors IF the URL contains a period. Otherwise I get a page with a 404 error header but no content (blank page). Of course the whole point of extensionless URLs is that there are no extensions, so this approach seems questionable to me:

  
  

  31:             if( requestedFile.IndexOf('.') > 0 )

  32:             {

  33:                 // There's some extension, so this is not an extensionless URL.

  34:                 // Don't handle such URL because these are really missing files

  35:             }

  
  

  I need to get this site running, so for now I'm using the IIS URL Rewrite module, which works OK (download from iis.net). I got the rules from one of your competitors in the link below (sorry). Apparently their built-in extensionless URLs are also based on 404 errors and they have some issues too, so they provided this alternative:

  
  

  http://blog.keithpatton.com/2009/04/18/IIS7+Extensionless+Urls+And+Kentico+CMS+40.aspx

  
  

  One advantage of the URL Rewrite module is that I can use my own custom errors, which the sf404.aspx solution doesn't seem to allow.

  
  

  Reply

• Armysniper Intermediate

  Posted on Dec 20, 2009 (permalink)

  When I originally posted above I was going to suggest using the URL Rewrite module or the rewrite module metioned in the Scott Guthries' ASP.NET blog. I am going to use the URL Rewrite module as I would prefer my server handle this and not my code if I can get away with it. Let me know how it works for you.

  Reply

• Richard

  Posted on Dec 21, 2009 (permalink)

  Georgi from Telerik told me that this problem was fixed in 3.7 SP2. I had already upgraded to that version using the installer but the instructions are not clear (wrong I'd say) about the necessary steps to upgrade the individual projects.

  
  

  I found the new DLLs in /ProjectManager/App_Data/EmptyProject.zip/bin. I copied those and overwrote the corresponding DLLs in the bin directory in my project. 404 errors are now working using sf404.aspx. Unfortunately the 404 error that results from this method always states that sf404.aspx is the file that couldn't be found (if the request was for an extensionless URL). I think that would confuse users of the site so I believe I will use the IIS Rewrite Module instead.

  
  

  I also copied the changes over from the web.config in the empty project. It might be a good idea for Telerik to run the Visual Studio Format Document command on this file if we're supposed to manually diff it with our files to get the updates - the majority of the 89 differences I found were just spacing. Many instances of /> without a preceding space, for example.

  
  

  Reply

• Georgi Georgi

  Posted on Dec 22, 2009 (permalink)

  Hello Richard,

  You are right that the requested url is always sf404.aspx, but we have changed that for the upcoming service pack. It will be released in the first days of January.

  We have taken care for the upgrades for our next major version - the upgrade process will be fully automatic. 

  Regards,
  Georgi
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Reply

• Adam

  Posted on Jan 19, 2010 (permalink)

  Hi Guys,
  
  I'm running SF 3.6 on IIS 7.
  
  I tried the following suggested steps and they didn't fix the 404 issue:
  
  1. Leave this <cms defaultProvider="Sitefinity" pageExtension="" as it is.
  2. Open IIS and map a custom error page for the 404 error handling like this /[YourProjectName]/sf404.aspx
  
  The entire site breaks when doing step #1 even after adding step 2.
  
  (I get "Thank you for visiting our web site. Please return soon for updates.")
  
  Basically, I just want the page group to not throw a 404 if the extension is not in the url:
  
  http://wellness.rmhp.org/partners/RMHMC
  should forward to
  http://wellness.rmhp.org/partners/RMHMC.aspx
  or http://wellness.rmhp.org/partners/RMHMC/default.aspx
  
  Please advise. Thanks!
  

  Reply

• Adam

  Posted on Jan 19, 2010 (permalink)

  Also, is there a special reason why the IIS default document functionality doesn't work for subfolders/pagegroups in Sitefinity? I'm suprised this hasn't been fixed yet, since it's such a basic piece of functionality for websites running under IIS.
  
  
  

  Reply

• Georgi Georgi

  Posted on Jan 21, 2010 (permalink)

  Hi Adam,

  I am not sure why this is not working for you - it looks fine on my end.

  Could you please try to use the another approach for using extensionless url - adding a wildcard mapping in IIS. This way, all requests will go to Asp.Net and therefore Sitefinity. The only thing you should have in this case, is to leave the pageExtension to empty string. 

  Let me know about the results. 

  Regards,
  Georgi
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Reply

• Adam

  Posted on Jan 21, 2010 (permalink)

  Hi Georgi,
  
  Thanks for your help, but I ended up using a customized solution based on this link http://msmvps.com/blogs/omar/archive/2007/04/29/serve-extensionless-url-from-asp-net-without-using-isapi-module-or-iis-6-wildcard-mapping.aspx, which seems to give me greater control.
  
  Are there any plans to get IIS default documents working for Sitefinity in the future?
  
  thanks
  
  

  Reply

• Georgi Georgi

  Posted on Jan 22, 2010 (permalink)

  Hello Adam,

  We have scheduled improvement over the handling of default documents, and url paths for our next major release. Hopefully we will able to find a complete solution which works in all cases. 

  I am glad that you were able to find a solution that works for you. 

  All the best,
  Georgi
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Reply

• Richard

  Posted on Mar 2, 2010 (permalink)

  Any update on when the service pack for 3.7 that improves extensionless URL handling will be released?

  Reply

• Ivan Dimitrov Ivan Dimitrov

  Posted on Mar 2, 2010 (permalink)

  Hi Richard,
  
  We are going to release a SP in the middle of March 2010, but it will not include optimization for Extensionless URL. We will rewrite the code for the next major release (4.0).
  
  Sincerely yours,
  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.

  Reply

• Richard

  Posted on Mar 15, 2010 (permalink)

  This is disappointing. Based on an earlier message in this thread I was expecting the fix in January and I delayed rolling out my site. I guess I'll have to use the IIS URL rewriter instead.

  
  

  Telerik - please try to be better about feature announcements in this forum. I do like knowing what's coming up in future releases but when you say that feature X will be available in release Y and it really doesn't come until a year later that hurts your credibility and makes it difficult for your users to plan. I've seen posts from 2007 promising features that haven't made it into the product yet.

  
  

  Perhaps you could have a page with a roadmap for the product and just refer people to that page. Also, I just looked at your PITS system for issue tracking. Sitefinity isn't listed, will it be added to that system? I see the issue tracking system is a beta, since the information is from Q3 2009 I wonder if it's really being used.

  Reply

• Georgi Georgi

  Posted on Mar 16, 2010 (permalink)

  Hello Richard,

  Thanks for your feedback.

  I agree with everything said by you. We are working on some internal changes which will allow us to have extensive roadmap (for your information, we have it now for the 4.0 release - http://www.sitefinity.com/asp-net-cms-features/roadmap.aspx). We are also working on integrating Sitefinity features/bugs with PITS - which is already showing the Q1 2010 items since yesterday.

  Apologies for any inconvenience on behalf of the team.

  Sincerely yours,
  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.

  Reply

• Jon

  Posted on Apr 2, 2010 (permalink)

  Was this released? The Mid-march update? I need help with extensionless URLs

  Reply

• Georgi Georgi

  Posted on Apr 2, 2010 (permalink)

  Hi Jon,

  We have released SP3 some weeks ago. If you have any specific questions on the extensionless urls, please let us know. 

  The user manual was also updated with this release - you will find some helpful information about the extensionless urls inside - http://www.sitefinity.com/documents/UserManual_3_7.pdf

  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.

  Reply

• Jon

  Posted on Apr 2, 2010 (permalink)

  I created a new thread to address this issue in 3.7.2.  Thanks

  Reply

Home / Developer Network / Forums / Sitefinity Older Versions (3.x): Developing with Sitefinity > Extensionless URLs in Sitefinity 3.6