Build rich, smart HTML5 and JavaScript apps for any platform, browser or device
Use Angular, TypeScript or JavaScript to build truly native mobile apps
Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
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.
There are three modes for working with MVC in Sitefinity. The difference is that Sitefinity’s MVC support allows multiple controllers on a Sitefinity page versus classic MVC using only one controller. This may cause problems when a controller performs a postback and navigates to an action.
Both controllers are placed on a Sitefinity hybrid page, allowing for MVC widgets and WebForms widgets. FirstController performs a postback, which changes the URL to http://site.com/page/IndexPostBack.
SecondController is not rendered on this URL because the action Load is not available for the route http://site.com/page/IndexPostBack.
Load
To overcome this, I provide a sample of two MVC widgets performing postbacks asynchronously. Refer to the attached sample for the code.
There are two controllers: the first for creating News and the second for creating Events (CreateNewsController and EventsController).
Upon postback, the controllers create Sitefinity Event/News items.
[HttpPost]
public
ActionResult Create(CreateNewsModel model)
{
if
(ModelState.IsValid)
var manager = NewsManager.GetManager();
var newsItem = manager.CreateNewsItem();
newsItem.Title = model.Title;
newsItem.Content = model.Content;
newsItem.Author = model.Author;
manager.SaveChanges();
Dictionary<
string
,
> contextBag =
new
>();
WorkflowManager.MessageWorkflow(newsItem.Id,
typeof
(NewsItem), manager.Provider.Name,
"Publish"
true
, contextBag);
return
Content(MvcHelper.RenderPartialViewToString(
this
"_NewsCreated"
null
));
}
"Default"
, model));
Under normal conditions, the postback redirects to a new route, and in this case, it goes to http://site.com/page/Create. This hides all other widgets since they are unavailable for this route.
The control handles this redirect to another route by performing an async postback. When creating a news/event item, the result of the postback loads two partial views (_NewsCreated.cshtml and _EventCreated.cshtml) through the MvcHelper class.
MvcHelper
public class MvcHelper { public static string RenderPartialViewToString(Controller controller, string viewName, object model) { if (string.IsNullOrEmpty(viewName)) viewName = controller.ControllerContext.RouteData.GetRequiredString("action"); controller.ViewData.Model = model; using (var sw = new StringWriter()) { var viewResult = ViewEngines.Engines.FindPartialView(controller.ControllerContext, viewName); var viewContext = new ViewContext(controller.ControllerContext, viewResult.View, controller.ViewData, controller.TempData, sw); viewResult.View.Render(viewContext, sw); return sw.GetStringBuilder().ToString(); } } } The async postback is performed client-side by the script NewsScript/EventScript.js. //check if Create ActionResult is called $(document).ready( function () { $("#createNews").click( function(){ var model = NewsObject.collectModel(); NewsObject.sendData(model, "/" + CURRENTPAGE + "/Create", "myNewsForm"); } ); }); //perform async POST sendData: function(newsData, destination, resultHolderId) { $.ajax({ type: 'POST', url: destination, contentType: 'application/json; charset=utf-8', data: JSON.stringify(newsData), success: function (result, args) { $("#"+resultHolderId).html(result) }, error: this._syncFailureDelegate }); } }
class
static
RenderPartialViewToString(Controller controller,
viewName,
object
model)
(
.IsNullOrEmpty(viewName))
viewName = controller.ControllerContext.RouteData.GetRequiredString(
"action"
);
controller.ViewData.Model = model;
using
(var sw =
StringWriter())
var viewResult = ViewEngines.Engines.FindPartialView(controller.ControllerContext, viewName);
var viewContext =
ViewContext(controller.ControllerContext, viewResult.View, controller.ViewData, controller.TempData, sw);
viewResult.View.Render(viewContext, sw);
sw.GetStringBuilder().ToString();
The async postback is performed client-side by the script NewsScript/EventScript.js.
//check if Create ActionResult is called
$(document).ready(
function
() {
$(
"#createNews"
).click(
(){
var
model = NewsObject.collectModel();
NewsObject.sendData(model,
"/"
+ CURRENTPAGE +
"/Create"
"myNewsForm"
});
//perform async POST
sendData:
(newsData, destination, resultHolderId) {
$.ajax({
type:
'POST'
url: destination,
contentType:
'application/json; charset=utf-8'
data: JSON.stringify(newsData),
success:
(result, args) {
"#"
+resultHolderId).html(result)
},
error:
._syncFailureDelegate
Stanislav Velikov is a Tech Support Engineer at Telerik. He joined the Sitefinity Support team in April 2011.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.