Tag Info

Hot answers tagged

6

Hardcoding is never a nice solution! Look in to the SuiteBarBrandingDelegate control: Elements.xml: <?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <!-- SuiteBarBrandingDelegate (the top-left "SharePoint" text on a page) --> <Control ...


4

Sharepoint needs some controls that are defined inside the master page or it will NOT render your master page. I suggest to refer to the following project: http://startermasterpages.codeplex.com/ to have a template where you can start to work


4

MasterPage is allowed deployed at site collection scope. If you want to set your masterpage as default masterpage below are the common methods: Write code in a feature receiver. Through Powershell commands Through UI (SharePoint Publishing Infrastructure and SharePoint Publishing feature needs to be activated to do this.) Through SharePoint designer. Now ...


3

Add the ms-dialogHidden class to your outer div, it will hide the content in dialogs: <div class="ms-dialogHidden" style="background-image:url('/Style%20Library/lfr/header.jpg');background-position:left; background-repeat:repeat-x;height:147px;"></div> For more, see here: ...


2

Remember that Application pages are just normal .aspx pages, nothing SharePoint specific. So you can just remove the DynamicMasterPageFile property from the <%@ Page %> tag. Just remember to add html, head, body now that a masterpage is no longer dictating the html structure.


2

You should have a line similar like this in your .aspx <%@ Page Language="C#" AutoEventWireup="true" CodeBehind="CreateCollabWeb.aspx.cs" Inherits="Something.Layouts.CreateCollabWeb" DynamicMasterPageFile="~masterurl/default.master" %> Here you can point to a different master page: <%@ Page Language="C#" AutoEventWireup="true" ...


2

It is NOT a good practice! ASP.NET master pages allow you to create a consistent layout for the pages in your application. A single master page defines the look and feel and standard behavior that you want for all of the pages (or a group of pages) in your application. You can then create individual content pages that contain the content you want to ...


2

If it is a Publishing web site then you can use SetInherit so that subsites will inherit the custom master page. Example: SPWeb web = SPContext.Current.Web; PublishingWeb publishingWeb = PublishingWeb.GetPublishingWeb(web); publishingWeb.CustomMasterUrl = "/_catalogs/masterpage/mycustom.master"; publishingWeb.CustomMasterUrl.SetInherit(true, true); ...


2

I do believe Site Collection scope is correct for a masterpage feature. The problem is, you cannot force subsites to use this masterpage (even though there's an option to reset all subsites in the UI). EDIT: If it's a publishing web you can do this, look at @Nadeem Yousuf's answer You will have to iterate over all the current SPWeb subsites and set their ...


2

It appears that this has to do with IE9, IE10, IE11 document standards for the client's browser. The problem is in the pickerdialog.master. As the People Picker is using the pickerdialog.master file, you need to add the following line in the head element. meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" Find the pickerdialog.master file in ...


2

If you have to show/hide parts of the Ribbon based on permissions then SPSecurityTrimmedControl is the ideal way to do it even if you are on SP 2013. You can use ViewListItems permissions to hide the Ribbon from users with Read Only permissions. See this http://msdn.microsoft.com/EN-US/library/ms412690 for all possible types of Permissions which can be used. ...


1

If this is 2013 the path should be: <%@ Register TagPrefix="uc0" TagName="LanguageChecker" Src="/_controltemplates/15/Project/UserControls/LanguageChecker.ascx" %> So, remove the ~ and add /15 to the Src. Your user control should be added to the Mapped folder CONTROLTEMPLATES in VS


1

I'm indebted to this exchange Publish missing in Sharepoint Designer 2010 where @webdes03 explained: "SharePoint Server Publishing Infrastructure" must be activated on the site collection and the actual subweb you're working with, it is set in both places (two separate features, one in Site Collection Features and one in Site Features). All looks good ...


1

Edit the page in Advanced Mode (from Sharepoint Designer). If the button "Advance Mode" is grayed, you need to enable "Enable Detaching Pages from the Site Definition". You can find this setting on the site in the section "SharePoint Designer Settings" (http://site-name/_layouts/15/SharePointDesignerSettings.aspx)


1

This post describes common cases. In you case you should use something like this <SharePoint:CssRegistration ID="CssRegistration1" Name="/_layouts/15/SFS.Ashok.Refer/Styles/site-visualwp.css" runat="server" After="corev15.css" />


1

SharePoint specific SharePoint provides the _spBodyOnLoadFunctionNames array. When the body is loaded, the onload event handler executes each function whose name is contained in this array, for example: _spBodyOnLoadFunctionNames('funcName'); function funcName() { //... } jQuery Specify a function to execute when the DOM is fully ...


1

You will need to use feature stapling to apply master page to newly created site collections. Feature Stapling has two features. A "Stapler" feature which staples another feature to the site definition and the "Staplee" feature which will be stapled See more at http://www.mssharepointtips.com/tip.asp?id=1065 ...


1

Did your colleague made any customizations to the farm? Use F12 developer tool to determine what element is causing the color. Branding issues that may occur when upgrading to SharePoint 2013


1

Remove master page reference from your site first, than place this sample code to try it out <html> <head> </head> <body> <form runat="server"> this the the policy page <br /><br /> <input onclick="close_window()" type="button" value="Close" /> <asp:Button ID="Button1" ...


1

How did you apply the composed look? In the browser, you select the masterpage independently of the colors. (The Site Layout dropdown in the left column.) Perhaps you didn't actually change the selected master? In code, the ApplyTheme() method does not switch the masterpage. It only applies the color and font scheme. The Composed Looks list is actually ...


1

Scope of masterpage feature should be set to 'Site'. You need to set the Reset all sub sites option for the masterpage to be applied to the sub sites.But also the sub sites will inherit the new master only if Site collection feature "SharePoint Server Publishing Infrastructure" is activated and in the sub sites the site feature "SharePoint Server Publishing" ...



Only top voted, non community-wiki answers of a minimum length are eligible