This article covers how to configure your Telligent Connect for Sitecore 2.6 installation so that it directs users to other Sitecore pages when content is accessed in a widget, instead of directing them into your Telligent-based community.
This feature only applies to Telligent Connect for Sitecore 2.6 and, previously, to Telligent Connect for Sitecore 2.5.
You need to have read and configured your site to use contextual URLs as described in the Working with contextual URLs in Sitecore article.
Turning Auto-Redirect on and off
If this installation of Telligent Connect for Sitecore is new, Auto-Redirect is turned on by default. However if, you need to turn it on or off, you do so by accessing the Sitecore content editor and navigating to System > Modules > TelligentEvolution > Configuration. Locate the Telligent Evolution section and check the box next to Generate Sitecore Urls (or uncheck it to turn it off).
Set up your Routes
In order for the Auto-Redirect feature to work, you must first set up and configure all of the routes that pertain to the content you are using.
Routes are the way Telligent Connect for Sitecore deciphers information from a Web URL. Telligent Connect for Sitecore uses wildcards at specific positions in a URL to hold dynamic pieces of data such as:
- group IDs
- application keys
- post keys
These pieces of data are used to retrieve the content they are associated with. You can learn to set up routes in your installation by referencing the article Working with contextual URLs in Sitecore.
Configure Url definitions
As the routing system uses the current URL to extract pieces of information, the definition system uses a target item to inject dynamic pieces of information into the URL being redirected to.
Start by navigation to System > Modules > TelligentEvolution > Urls > Definition in Sitecore. You will have to repeat this process for every entry in each child item in this folder if you want to use this feature.
For this example, we are just going to set up the blog post definition:
Under definitions, open the sitecore_v2_blogUrls item. This item contains all the supported URLs for blogs.
Click the BlogPost field to open the DropTree of items and select the item that will be your blog post page from the tree.
Note: This is the page where all widgets referring to a blog post will send your users to within Sitecore. This item must also be included in a valid route, as discussed previously. Thus in this example, the blog post item we chose must be included in the BlogPostRoute item set.
Save the Item and publish. Note: You may need to recycle your application pool for this to go into effect, so you should set as many of these as possible before doing so.
The following table explains what each field represents in terms of URL.
||This item represents your blog home page (needs to be included in the BlogRoute).
||This item represents your blog post page (needs to be included in the BlogPostRoute or BlogPostIDRoute).
||This item represents a group home page where you may list blogs for that group or all posts from the group's blogs (needs to be included in GroupRoute).
||Same as Blog, but this route only expects a numeric blog Id and is not used directly (needs to be part of BlogIDRoute).
||Same as BlogPost, but this route only expects a numeric blog post Id and is not used directly (needs to be part of BlogPostIDRoute).
||This would be a Forum landing page (needs to be part of the ForumRoute).
||This would be a group landing page meant to display all forums in a group or an aggregate thread list (needs to be part of the GroupRoute).
||This would be a thread landing page (needs to be part of the ThreadRoute).
||This is where a user would start a new thread (needs to be part of ForumRoute).
||This is where a thread gets edited (needs to be part of the ThreadRoute).
||This is where you edit a thread's reply (needs to be part of ForumReplyRoute).
||This is where a user replies to a thread when using rich editing (needs to be part of ReplyToForumThreadRoute).
||This is where a user replies to a thread reply when using rich editing (needs to be part of ReplyToForumReplyRoute).
||This is where a user is sent to report abusive content in a forum (needs to be part of ReportAbuseRoute). Note: this is not used in release 2.6.
||This is where a user is sent to view a forum reply (needs to be part of ForumReplyRoute).
||This is where a user is sent when a forum is moderated and the post is delayed (needs to be part of ForumRoute).
||This represents a group landing page (needs to be part of GroupRoute).
||This is a group landing page where you would list media galleries or an aggregate list of gallery files (needs to be part of GroupRoute).
||This is the page where a user would view a gallery post (needs to be part of MediaRoute).
||This is the page where a user would view a gallery, usually a list of its media (needs to be part of GalleryRoute).
||This is the page where a user would edit a gallery post (needs to be part of MediaRoute).
||This is the page where a user would create a new gallery post and upload a file (needs to be part of GalleryRoute).
||This is the page where a user would view a slideshow of gallery posts (needs to be part of GalleryRoute).
||This is the same as Media but for ID-only based URLs and is not used directly (needs to be part of MediaRoute).
||This represents a user profile (needs to be part of UsernameRoute)