See how Microsoft Consulting Services can help you
Contact Microsoft Services
Contact The SharePoint Guys
Apply for a job at Microsoft Consulting Services
MCS Solution Dev
The Deployment Guys
MSDN UK Newsletter
MSDN UK Team Blog
TechNet UK Newsletter
TechNet UK Blog
Include an additional search control adjacent to the standard search box on a Meeting Workspace site, but not show any search controls on system pages (as is the default).
The Meeting Workspace masterpage MWSDefaultv4.master includes the ContentPlaceHolder with id="PlaceHolderSearchArea" to display the standard search box.
You might expect that if you modify the masterpage to include another control that it would display, however, the default.aspx page in the Meeting Workspace site includes this ContentPlaceHolder and it includes the standard search box. This means that it will replace the contents of the placeholder from the masterpage.
There are a couple of options to resolve this, depending on your requirements.
This solution, as a workaround, only requires an update to the MWSDefaultv4.master (or alternatively creating a new masterpage based on this one), and no change to any other files. The side effect though is the search box will now appear on the system pages (like Site Settings).
1. Copy the asp:ContentPlaceHolder with id=PlaceHolderSearchArea
2. Set Visible=False on the original (a common technique to make sure you don't break things that have a dependency on the existence of particular placeholders)
3. Change the id on the copy to something else
4. Put the custom control after the delegate
The end result should be something like this:
<asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server" Visible="false">
<SharePoint:DelegateControl runat="server" ControlId="SmallSearchInputBox" Version="4"/>
<asp:ContentPlaceHolder id="PlaceHolderSearchAreaCustom" runat="server">
<span> Or </span><div>MY CONTROL HERE</div>
This option fixes the root cause by removing the content placeholder that is preventing the masterpage customisation from displaying correctly.
This post was co-authored by:
Christopher WalkerSharePoint ConsultantChristopher.Walker@microsoft.comLinkedIn
James KempSharePoint Architecture Consultant James.Kemp@Microsoft.comLinkedInBio