Is it possible to configure Group and Profile pages to not require /default.aspx in their URL

Support

Support
A public community space for Developers, IT Professionals, Architects, and System Administrators to engage and help each other, share knowledge and best practices, find product documentation and Q&A, and discuss technology oriented topics.

Is it possible to configure Group and Profile pages to not require /default.aspx in their URL

This question is not answered

We have many group and profile pages on our Telligent Community 6.1 site, and the way Telligent is currently configured, the profile pages and home pages of each group require "/default.aspx" at the end of their URL. For example, a group's home page might be www.site.com/groupname/default.aspx and a profile page might be www.site.com/personname/default.aspx

Is there any way to configure Telligent so that it would not require /default.aspx to be appended at the end of profile and group URLs? Currently, if a site user goes to www.site.com/groupname, they receive a 404 page. We would like them to be redirected to the actual home page of the group if default.aspx is left off, and the same for profile pages.

All Replies
  • rewriterules.zip

    You may want to try adding url rewriting rules. Verify you have URL Rewrite installed in IIS, you will need to access the web.config file from your Telligent Evolution site and prepare it for the rewriteRules.config file.

    1. Locate the path to your Evolution site's Web folder.
    2. Open the web.config file for editing.
    3. In system.webServer add the following:
      <system.webServer>
      	<rewrite>
      		<rules configSource="rewriteRules.config" />
      	</rewrite>
      </system.webServer>
    4. Add the attached sample rewriteRules.config file to Telligent Evolution's Web folder. (You may need to adjust it to fit your requirements)
    5. Restart IIS.

  • I tried adding the <rewrite> node to the <system.webServer> section of the project's web.config file, but Visual Studio informs me that <rewrite> is an invalid child element of <system.webServer>.  

    I do have URL Rewrite installed in my local development environment's copy of IIS.

  • That is correct, it's not part of system.webServer but it is a part of IIS. If you manually add a rule in IIS Manager you'll notice that it adds the rule in system.webServer as well.