I assume you are talking about the widgets of the built-in modules (News, BlogPosts, etc.) They all inherit from ContentView and have child views in them. Master-detail scenarios are handled by knowing when to load which child view. Let's take the News widget as an example (NewsView class).
It has two child views - NewsMasterView and NewsDetailView. When you put it on a page, the widget itself has to decide whether to render in master or detail mode. It makes this decision based on several factors:
- The ContentViewDisplayMode property
- The current URL
If the ContentViewDisplayMode property is Master, the widget always renders in master mode. It shows all items of the required type (NewsItem). If the property is Detail, the widget always renders in detail mode. The item which is rendered is taken based on the DataItemId property of the detail view definition. If the ContentViewDisplayMode property is Automatic, the widget decides based on the URL.
If the URL segment after the current page corresponds to a URL of an item of the required type (in this case NewsItem), the widget renders that item in detail mode. If it doesn't, the widget renders in master mode.
For more information on how the widgets handle URLs, you can read the following blog posts:
Url Filtering in Built-in Content Widgets
Url Filtering with Multiple Content Widgets per Page
I hope this sheds some light on the master-detail scenarios
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items