PLEASE  do use firebug when you try to decode the sharepoint template!

Customization Corev4.css-

and if you can`t find the part from corev4.css, which could be saved in server at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\template\layouts\1033\STYLES.

ms-rteElement-H1B   =   Headline of each document page

ms-quickLaunch{padding-top:5px;} = quicklaunch navigation

.s4-ql ul.root > li > .menu-item = the first navigation root

.s4-ql ul.root > li > ul >li > .menu-item  = the second quick launch root

.s4-ql ul.root > li > ul >li > ul> li > .menu-item  = the third quick launch root

body #s4-leftpanel-content= left side body border

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\template\layouts\1033\STYLES

CSS line 6994

.ms-rte-layoutszone-inner

{

word-wrap:break-word;

border:0px solid transparent;

margin:0px;

padding:10px;

overflow:hidden;

}

SearchBar:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\1033\STYLES\Themable\SEARCH.CSS

.s4-search input.ms-sbplain =search input column

Customize Search Bar—do follow post from Eric Overfield:

SharePoint 2010: Create a Custom Search Box

– March 31, 2011Posted in: SharePoint

 

You will want to find the existing OOB Basic Search feature. By default, that is found in the following location in your SharePoint 2010 server:

  1. http://s2.wp.com/wp-content/themes/pub/inove/img/blockquote.gif); background-color: rgb(244, 245, 247); border-style: dashed; border-color: rgb(204, 204, 204); background-position: 3px 3px; background-repeat: no-repeat no-repeat; ">C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\OSearchBasicFeature
  2. Create a new subdirectory in the FEATURES directory, in our case, we will name it OSearchBasicFeatureCustom, i.e.
    http://s2.wp.com/wp-content/themes/pub/inove/img/blockquote.gif); background-color: rgb(244, 245, 247); border-style: dashed; border-color: rgb(204, 204, 204); background-position: 3px 3px; background-repeat: no-repeat no-repeat; ">C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\OSearchBasicFeatureCustom
  3. Copy all of the contents from the OSearchBasicFeature directory to the OSearchBasicFeatureCustom directory.
  4. Open the feature.xml file found in the OSearchBasicFeatureCustom directory in a text editor and replace the GUID element with a new GUID. The quickest way to get a new GUID is to open Visual Studio and go to Tools->Create Guid.Also change the Title and Description elements while you are at it.
  5. Open the searchArea.xml file found in the OSearchBasicFeatureCustom directory in a text editor and change the ID element to a unqiue value like SmallSearchInputBoxCustom.
  6. Make other changes to the properties found in the searcharea.xml file. As an example, say that you would like to hide the scope. You would update the property:
    http://s2.wp.com/wp-content/themes/pub/inove/img/blockquote.gif); background-color: rgb(244, 245, 247); border-style: dashed; border-color: rgb(204, 204, 204); background-position: 3px 3px; background-repeat: no-repeat no-repeat; "><Property Name="DropDownMode">HideDD_useDefaultScope</Property>

    Would you like to change the Search button? No problem, use:

    http://s2.wp.com/wp-content/themes/pub/inove/img/blockquote.gif); background-color: rgb(244, 245, 247); border-style: dashed; border-color: rgb(204, 204, 204); background-position: 3px 3px; background-repeat: no-repeat no-repeat; "><Property Name="GoImageURL">/Style Library/go.gif</Property>
  7. http://s2.wp.com/wp-content/themes/pub/inove/img/blockquote.gif); background-color: rgb(244, 245, 247); border-style: dashed; border-color: rgb(204, 204, 204); background-position: 3px 3px; background-repeat: no-repeat no-repeat; ">                <Property Name="FrameType">None</Property>
    		<Property Name="DropDownMode">HideDD_NoScope</Property>
    		<Property Name="TextBoxWidth">315</Property>
    		<Property Name="ShowAdvancedSearch">false</Property>
    		<Property Name="QueryPromptString">Search for People or Content</Property>
    		<Property Name="SearchBoxTableClass">search-box</Property>

    Just change the url to match your search button.

    For a reference all the different properties you can change, check out this list from Microsoft:

    http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.portal.webcontrols.searchboxex_properties.aspx

  8. Once you have made these changes and saved the xml files, it is now time to start the SharePoint 2010 Management Shell so you can install and enable the feature.
  9. Run the following commands in the SharePoint 2010 Management Shell:
    http://s2.wp.com/wp-content/themes/pub/inove/img/blockquote.gif); background-color: rgb(244, 245, 247); border-style: dashed; border-color: rgb(204, 204, 204); background-position: 3px 3px; background-repeat: no-repeat no-repeat; ">Install-SPFeature OSearchBasicFeatureCustom Enable-SPFeature OSearchBasicFeatureCustom -Url http://www.yoursite.com/

    Replace http://www.yoursite.com with the actual url of your SP site.

  10. Even though the new feature is a farm feature, I sometimes got an error:
    http://s2.wp.com/wp-content/themes/pub/inove/img/blockquote.gif); background-color: rgb(244, 245, 247); border-style: dashed; border-color: rgb(204, 204, 204); background-position: 3px 3px; background-repeat: no-repeat no-repeat; ">Enable-SPFeature : Feature 'OSearchBasicFeatureSPT' (ID: 66a7a44f-c33d-48de-8a4 f-d60960849895) is already activated at scope 'http://www.yoursite.com/'. At line:1 char:17 + Enable-SPFeature >>>> OSearchBasicFeatureSPT -Url http://www.yoursite.com/ + CategoryInfo : InvalidData: (Microsoft.Share...etEnableFeature: SPCmdletEnableFeature) [Enable-SPFeature], DuplicateNameException + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletEnableFeature
  11. My Suggestion to get around this is to disable, then re-enable the feature:
    http://s2.wp.com/wp-content/themes/pub/inove/img/blockquote.gif); background-color: rgb(244, 245, 247); border-style: dashed; border-color: rgb(204, 204, 204); background-position: 3px 3px; background-repeat: no-repeat no-repeat; ">Disable-SPFeature OSearchBasicFeatureSPT -Url http://www.yoursite.com/ Enable-SPFeature OSearchBasicFeatureSPT -Url http://www.yoursite.com/
  12. The feature should now be ready to be used. Open your site, in our examplehttp://www.yoursite.com, in SPD.
  13. Open you masterpage, by default found in the /_catalogs/masterpage directory, named default.master.
  14. Edit the default.master file and look for the following code:
    http://s2.wp.com/wp-content/themes/pub/inove/img/blockquote.gif); background-color: rgb(244, 245, 247); border-style: dashed; border-color: rgb(204, 204, 204); background-position: 3px 3px; background-repeat: no-repeat no-repeat; "><div id="search-box"> <asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server"> <SharePoint:DelegateControl runat="server" ControlId="SmallSearchInputBox" Version="4"/> </asp:ContentPlaceHolder> </div>

    You only need to replace the ControlId property with the ID you set in the searcharea.xml file. In our example:

    http://s2.wp.com/wp-content/themes/pub/inove/img/blockquote.gif); background-color: rgb(244, 245, 247); border-style: dashed; border-color: rgb(204, 204, 204); background-position: 3px 3px; background-repeat: no-repeat no-repeat; "><div id="search-box"> <asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server"> <SharePoint:DelegateControl runat="server" ControlId="SmallSearchInputBoxSPT" Version="4"/> </asp:ContentPlaceHolder> </div>
  15. Save, Check In and Publish as required. That’s it!
  16. After it is been used, we can go to
  17. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\1033\STYLES\Themable\SEARCH.CSS to decorate it again!! under .s4-search input.ms-sbplain.

About Lei

I am an IT specialist with over 10 year experience - years on Automation, on-Premise or Azure.

I am happy to develop however never want be a full time developer. Only do what I have to do. If it has to be PowerShell,HTML, PHP, CSS, C#, VBS or JS, front end or backend, so be it, doesn't matter!

Spent years with Windows, SCCM, SharePoint, SQL and Exchange servers. For last several years, I have been actively working under On Premise > Azure environment.

THERE IS NO WAY BACK!!!

Current Certificates:
    Microsoft® Certified-
  • -Enterprise Administrator
  • -Database Administrator
  • -SharePoint Administrator
  • -Administering and Deploying SCCM 2012
Red Hat Certified Technician
ITIL V3 Foundation - Practitioner

Working on Azure Certificates now and hopefully they can stop upgrading their questions one day! GIVE ME A BREAK!

Contact Lei

Name *
Email *
Comments *

Traffic since 10/08/2016

Today13
Yesterday83
This week637
This month1933
Total416293

Visitor Info

  • IP: 54.221.73.186
  • Browser: Unknown
  • Browser Version:
  • Operating System: Unknown

Who Is Online

1
Online

2017-12-17

Login