How to check whether URL parameters are resolved in pages with MVC widgets

How to check whether URL parameters are resolved in pages with MVC widgets

March 11, 2014 0 Comments

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);
            }
  }

In the code we check whether the URL parameters of page are resolved because there might be a widget in details view mode on the same page and if we want to see the information from this widget we need to make this verification.

If the URL parameters are not resolved error with status code 404 will be thrown. In the other case if the URL parameters are resolved MVC default widget behavior will be displayed.

Note that there is a bug in Sitefinity if the MVC control is rendered before the other control in details mode. Find details of the bug on our Feedback portal. You need to make sure that the MVC control is rendered before the other control in details view mode otherwise neither the MVC widget will be displayed nor the 404 error will be thrown.

Stefani Tacheva

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.

Comments
Comments are disabled in preview mode.
Topics
 
 
Latest Stories in
Your Inbox
Subscribe
More From Progress
d12fcc0bdb669b804e7f71198c9619a7
5 Questions Automakers Should Ask to Improve Asset Uptime
Download Whitepaper
 
SF_MQ_WCM
2018 Gartner Magic Quadrant Web Content Management (WCM)
Download Whitepaper
 
What-Serverless-Means-For-Enterprice-Apps-Kinvey
What Serverless Means for Enterprise Apps
Watch Webinar