Tag Info

New answers tagged

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 ...


0

I am using PeoplePicker with HTML5and CSS3, this is my function to inizialie it and get the value: Use the function initializePeoplePicker to inizialize the picked. The argument is the DIV id. To get the value of the picker, use the fucntion getUserInfo(). function initializePeoplePicker(peoplePickerElementId) { Create a schema to store picker ...


0

To hopefully add a bit more value to this thread, it should not be necessary to edit the page in SharePoint Designer to set the master custom.master to overcome your problem - if you do you will open up another can of worms whereby a banner is displayed at the top of each page you have modified which reminds users that "The current page has been customized ...


0

looks like your directly inserting javascript (inline scripting),, dont think its on the masterpage but rather the layouts page that both masterpages reference! dont worry... ive done it when adding some inline script to layouts page and it throws this error: solution: goto web application web.config file.... open up in word document and look for: ...


0

There are a lot of changes between the v4.master (2010) and the seattle.master (2013) Maybe the most relevant is the suitebar and the ribbon bars. All of the features from the 2010 are present in the 2013 version, however some of them could be hidden like the breadcrumb, you can read more about in the link bellow. ...


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 ...


0

it should be within the masterpage, and not the rendered html but rather aspx ;) <SharePoint:AjaxDelta runat="server" id="DeltaSuiteBarRight" CssClass="ms-core-deltaSuiteBarRight" BlockElement="true"> <SharePoint:SPSecurityTrimmedControl runat="server" AuthenticationRestrictions="AuthenticatedUsersOnly" EmitDiv="true"> ...


0

I would add some delegate controls in your masterpage and then create some user controls that fill in the content for that delegate control. Then you can create some features that turn on or turn off what user control is being used in the delegate control. This also enables some code behind in your user controls. See this link for more information. ...


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)


0

I have written a feature that when activated at the Site Collection Settings, will inject the jQuery library into the Masterpage using a delegate control. That way you can add the library on a site by site basis. Bismarck


-1

You can load the jquery library within each web part. We experienced the same problem and this was the only solution that worked. The master does not load until after the web parts have loaded.


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 ...


0

Use _spBodyOnLoadFunctionNames.push("FunctionName");


0

One solution is to turn off the MDS feature. But check this link for other solution


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: ...


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


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. ...


0

If you're overriding the CSS for anchor links, use the following CSS in order (LV-HA) to override it globally. Ex. a, a:link {text-decoration:none;} a:visited {text-decoration:none;} a:hover {text-decoration:underline; background: none repeat scroll 0 0 #FFF2A8; color: #4472B9} a:active {text-decoration:none;} a:hover, a:active { outline: 0 none; } ...


0

Go to Site Collection administration settings -> SharePoint Designer Settings. Made sure all the boxes are checked .


0

Put a SiteLogoImage control in your master page and hardcode its LogoImageUrl property. The hardcoded logo can be overridden on an individual site by going to Site Settings > Title, Description, and Icon. <SharePoint:SiteLogoImage ID="logoImage" runat="server" LogoImageUrl="/_layouts/images/siteIcon.png" />


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 ...


3

b. You can remove this in Master page: <SharePoint:DelegateControl id="ID_SuiteBarBrandingDelegate" ControlId="SuiteBarBrandingDelegate" runat="server"/> Instead paste needed text. Use Microsoft Sharepoint Designer to do this.


0

Got the solution: Along with default master and custom master we can set the site logo as well. web.MasterUrl = webAppRelativePath + "_catalogs/masterpage/testmaster.master"; web.CustomMasterUrl = webAppRelativePath + "_catalogs/masterpage/testmaster.master"; web.SiteLogoUrl = webAppRelativePath + "Style%20Library/HD_Internal_Images/testmaster.png";


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 ...


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


-1

Check if the .aspx page is added within: Site Settings -> Master pages


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" ...


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 ...


1

You may have a look through this post.


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 ...


0

I found the issue. There was a custom css enabled in the masterpage setetings in site settings.


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


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" ...


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 ...


0

You have below options: OPTION 1: Use a custom user control where you get the UPS property & based on the value register a script using ScriptManager.RegisterStartUp or some other way based on whether you are using Update panels in your control. Basically you have to do below in the script file/function: using JQuery get the top bar HTML ...


2

You can use jQuery for this.use the below script to add class in the user control. $(document).ready(function(){ var className='class1';//here write logic for deciding the classname . $('div[id*="new-div"]').addClass(className); });


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" ...


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 ...


0

Is the publishing feature enabled at the site collection level? A publishing site normally starts at the site collection level and that is also where the Style Library should live, which holds files that apply to all sites in the site collection. A publishing site uses page layouts and other things that are also defined at the site collection level, not in ...


1

The master page won't be removed automatically. You will need to write the code in the feature deactivated event to delete the mater page from the _catalogs library.



Top 50 recent answers are included