You can accomplish this goal using either SharePoint Designer or Visual Studio. I prefer to create solutions that are easily redeployable between development, test, and production; therefore, I am going to use Visual Studio to accomplish this. To accomplish our goal, we will create a web scoped feature receiver that adds a Content Editor Web Part containing our jQuery commands to a lists NewForm and EditForm.
I am not going to discuss the setup of the Visual Studio project file. Instead, I will focus on the code required for the solution. This is a boiler plate feature activated event handler that allows any user to activate the web scoped feature. The real work is done within the AddContentEditorWebPart method.
public override void FeatureActivated(SPFeatureReceiverProperties properties)
{
SPWeb web = properties.Feature.Parent as SPWeb;
SPSecurity.RunWithElevatedPrivileges(() =>
{
using (SPSite elevatedSite = new SPSite(web.Site.ID))
using (SPWeb elevatedWeb = elevatedSite.OpenWeb(web.ID))
{
AddContentEditorWebPart(elevatedWeb);
}
});
}
This method creates a list object, then creates a file object for the new form and edit form for this list. Once you have the file, you can create a web part manager object and then add in a content editor web part. The final part of this solution is the XML representation of the web part definition. I great way to get the base Content Editor Web Part XML is to add a Content Editor Web Part to a SharePoint web part page then select to export the defintion.
private void AddContentEditorWebPart(SPWeb elevatedWeb)
{
string listName = "Your list title.";
SPList list = sysWeb.Lists[listName];
string xmlWebPartDef = "This is the XML representing the web part (see example below)";
for (int i = 0; i < 2; i++)
{
SPFile frontPage = null;
frontPage = sysWeb.GetFile(list.DefaultNewFormUrl);
if (i == 0)
{
}
else if (i == 1){
frontPage = sysWeb.GetFile(list.DefaultEditFormUrl);
}
SPLimitedWebPartManager mgr = frontPage.GetLimitedWebPartManager(PersonalizationScope.Shared);
XmlReader xmlReader = XmlTextReader.Create(new StringReader(xmlWebPartDef));
string errorMessage;
var contentEditorWebPart = mgr.ImportWebPart(xmlReader, out errorMessage);
mgr.AddWebPart(contentEditorWebPart, "Main", 999);
}
}
Once you have that XML, you can add in your jQuery call. For our original example, we are trying to add a mask to the Home Phone field. I added my jQuery logic to the CONTENT node near the bottom of this example.
<WebPart xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/WebPart/v2">
<Title>AddMaskedControls</Title>
<FrameType>None</FrameType>
<ChromeType>None</ChromeType>
<Description>Allows authors to enter rich text content.</Description>
<IsIncluded>true</IsIncluded>
<ZoneID>Main</ZoneID>
<PartOrder>99</PartOrder>
<FrameState>Normal</FrameState>
<Height />
<Width />
<AllowRemove>true</AllowRemove>
<AllowZoneChange>true</AllowZoneChange>
<AllowMinimize>true</AllowMinimize>
<AllowConnect>true</AllowConnect>
<AllowEdit>true</AllowEdit>
<AllowHide>true</AllowHide>
<IsVisible>true</IsVisible>
<DetailLink />
<HelpLink />
<HelpMode>Modeless</HelpMode>
<Dir>Default</Dir>
<PartImageSmall />
<MissingAssembly>Cannot import this Web Part.</MissingAssembly>
<PartImageLarge>/_layouts/images/mscontl.gif</PartImageLarge>
<IsIncludedFilter />
<Assembly>Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Assembly>
<TypeName>Microsoft.SharePoint.WebPartPages.ContentEditorWebPart</TypeName>
<ContentLink xmlns="http://schemas.microsoft.com/WebPart/v2/ContentEditor" />
<Content xmlns="http://schemas.microsoft.com/WebPart/v2/ContentEditor"><![CDATA[
<script type="text/javascript" src="/_layouts/1033/jquery.maskedinput-1.2.2.js"></script>
<script type="text/javascript" language="javascript">
$(document).ready(function() {
$("input[title='Home Phone']").mask("999-999-9999");
});
</script>
]]></Content>
<PartStorage xmlns="http://schemas.microsoft.com/WebPart/v2/ContentEditor" />
</WebPart>
There are a couple notes that should be touched upon regarding the data in the CONTENT node. The jquery.maskedinput-1.2.2.js file is not part of the SharePoint installation so I copied that file in the SharePoint hive. The jQuery reference is locating the field by the controls DISPLAY NAME. The mask will be saved as well as the data, so our home phone data will look like 555-123-4567. This content editor web part XML was pulled from a SharePoint 2010 site. The same example will work with a SharePoint 2007 site with one change. The assembly reference should be Microsoft.SharePoint, Version=12.0.0.0 instead.
This is a simple and powerful way of getting jQuery into your SharePoint NewForm / EditForms.
No comments:
Post a Comment