The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
Sitefinity 6.2 introduces a hook which lets implement “default” behavior in controllers. You can override the HandleUnknownAction method in your controller in order to decide what to do when an action method is not resolved for a controller - which can occur if you have multiple controllers on one page and a widget that contains a details view. More information about the specifics of this method could be found in the following blog post
Often times widgets in details view will append URL parameters when they handle things like paging. To check whether URL parameters are resolved in cases where we have pages with MVC widgets and widgets in details view mode you could use the following method override in your controllers:
protected
override
void
HandleUnknownAction(stringactionName)
{
if
(!RouteHelper.GetUrlParametersResolved())
{
this
.Response.StatusCode = (
int
)HttpStatusCode.NotFound;
}
else
{
this
.Response.StatusCode = (
int
)HttpStatusCode.OK;
// Implement default MVC widget behavior. For example:
View(
"Default"
, GetModel()).ExecuteResult(
this
.ControllerContext);
}
}
View all posts from Stefani Tacheva on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Let our experts teach you how to use Sitefinity's best-in-class features to deliver compelling digital experiences.
Learn MoreSubscribe to get all the news, info and tutorials you need to build better business apps and sites