Skip to main content

Using jQuery validation plugin with fields in a jQuery UI .dialog()

One issue I ran into while using the jQuery UI library along with the jQuery validation plugin in an ASP.NET page is that when the dialog is created, it's moved outside of the page's main form.  jQuery validation requires all fields to be validated to be inside a form, so fields in the dialog won't validate, plus if you need to have server-side controls inside of that dialog, there's not a lot you can do to move the dialog or the form. (If you don't have any server-side controls in the form, read skip further down for an alternate solution) Nested forms aren't allowed, and ASP.NET throws an error if you put server-side controls outside the main form.  An easy (albeit hacky) solution I found was just to move the dialog and its overlay back inside the form tag after creation:

    open: function (event, ui) {
        $(".ui-widget-overlay").prependTo("form"); //moves the overlay
}).parent().appendTo("form"); //moves the rest of the dialog

Obviously this is highly dependant on the the "ui-widget-overlay" class name in particular, which could change in future releases of jQuery UI so don't just go copy/pasting this example in a few years and telling me it doesn't work.  This also assumes you don't have any other things to validate outside of the dialog, otherwise you're going to have to use a different solution.

Alternate solution:

As mentioned above, this only works if you don't have any server-side controls inside the dialog.  It's pretty obvious in retrospect so I was debating even mentioning it, but I was confused about this at first so perhaps I can help save someone else a little time!  This issue arose because I needed to add another dialog, and of course putting them both inside the same form made them trigger validation events on both dialogs together, so nothing was ever valid!

Solution: move all dialogs outside of the main form tag, and add a form tags inside of each dialog. Validate each form separately, then post the information to a webmethod using AJAX.  That's it!


Popular posts from this blog

Using Log4Net to use both event log and a rolling log file

Here's the config section, note that the applicationNameproperty in the EventLogAppender needs to be the same as the event source in the windows event log that you want to log to.  If the event source doesn't exist, that appender won't work.  In this particular project I create that during install using WiX (which is covered in another post)

    <appendername="RollingLogFileAppender"type="log4net.Appender.RollingFileAppender">      <filevalue="log.txt" />      <datePatternvalue="dd-MM-yyyy" />      <appendToFilevalue="true" />      <locationinfovalue="false" />      <rollingStylevalue="Size" />      <maximumFileSizevalue="1MB" />      <maxSizeRollBackupsvalue="10" />      <staticLogFileNamevalue="true" />      <layouttype="log4net.Layout.PatternLayout">        <conv…

Using WiX to create an event source during install of a .NET framework project

Edit: so I guess I wasn't the only one confused with this stuff, as it's been my most popular post by far!  If I've helped you out or saved you some time, please let me know in the comments :)

In order for this to work, you have to add references to WixUtilExtension and WixNetFxExtension to your WiX project.  Once that's done, add this inside a <Component> element:

<Util:EventSourcexmlns:Util=""Name="EVENTSOURCEGOESHERE"Log="Application"EventMessageFile="[NETFRAMEWORK40FULLINSTALLROOTDIR]EventLogMessages.dll" />
Obviously replace EVENTSOURCEGOESHERE with your event source name.  NETFRAMEWORK40FULLINSTALLROOTDIR is a property set by the WixNetFxExtension which stores the path to the .NET framework v4 directory, but you can replace this with the corresponding property for the directory containing the relevant EventLogMessages.dll file.  So if you're using the .NET framewo…

Umbraco Deployment Checklist

This is primarily aimed at deploying from Visual Studio to an Azure Web App + Azure SQL database, feel free to skip bits that aren't relevant if you're doing other things.

Prerequisites for developing locally:
Visual Studio (obviously)
Ensure IIS URL Rewrite module is installed using web platform installer (other downloads from MS documentation don't seem to work)

Set up Azure:
Make a new SQL Database in Azure, take note of the server name, database name, admin login and admin password.  If you already have a server and resource group, automate with Powershell as shown below (you'll need to replace the param values):
New-AzureRmSqlDatabase -DatabaseName "UmbracoDatabase" -ServerName "TheServer" -ResourceGroupName "Whatever" -Edition "Basic"
Add your IP to the Azure SQL db firewall so Umbraco can connect to it later when running locally
Create a new Azure web app, either manually or via Powershell:
New-AzureRmWebApp -ResourceGroupName…