Tag Info

Hot answers tagged

7

The log file should get you the path that SharePoint unsuccessfully tries to resolve. Try adding "~sitecollection" first in the ScriptLink like: <SharePoint:ScriptLink language="javascript" name="~sitecollection/custom/jquery-1.10.2.min.js" runat="server" Localizable="false" /> but this will only work inside the "the_new_osce_portal" Site ...


7

Since respond.js is a presentational script, its placement within your HTML can dramatically impact page performance and execution time, especially on less capable browsers with slower JS engines. This module takes the guesswork out of placement and puts the script where it will be most effective. Optimal location is in the head after your CSS but before ...


6

I would not advice to edit the Seatle.master. Instead I'd advice you to just take a copy of it and rename + edit the copy. In that way, in case anything goes wrong, you still have a solid fallback masterpage. Why some may advice to edit the html version, that is to support the Design Manager - But that method is primarily opinion-based. Regarding your ...


6

You can copy any of the existing MasterPage's html file (I hope you have already figured that out) and go to Site Settings -> Design Manager -> Edit Master Page Now click your copied MasterPage and at the top-right you can see Snippets.. This is newly introduced in SharePoint 2013 and further explained here Now if you click Search Box, this will give you ...


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


5

There are custom SharePoint CSS classes that you may need to overwrite to change the colour of the hovering. Using IE developer tools I found that the two classes you're looking at are .ms-welcome-hover and .ms-siteactions-hover the welcome hover class obviously being the top bar for the page. This code in your custom CSS should change it to a blue ...


5

If all resources for the branding marked (MasterPages, CSS, JS) as Ghostable or GhostableInLibrary then it looks like they where stored in the content database. The files will be directly loaded from the feature directory. They are not as long as you don't modify those files directly inside of SharePoint. If you then update your solution the files will be ...


5

In the 2nd statement you should have used the site collection specific TOKEN as in: <SharePoint:Scriptlink runat="server" Name="~sitecollection/Style Library/[YOUR SITE]/PathToJqueryLib/jquery-1.10.2.min.js /> The issue with your 3rd (also known as Client-Side JavaScript library reference) is that such constructs do no recognize token-based ...


4

Add class="noindex" to your footer <div> See Control Search Indexing (Crawling) Within a Page with Noindex


4

Scriptlink is typically reserved for JS files deployed to the file system. The ScriptLink will always look in /_LAYOUTS/1033 for the scripts. http://tommdaly.wordpress.com/2010/12/16/scriptlink-vs-whats-the-difference/ Just change it to the typical script src="/sites/Intranet/Style Library/JS/jquery-1.10.2.min.js" syntax or copy the JS files to the ...


4

Inside the current site's Site Settings, navigate to Site Collection Administration > Site Collection Features. Activate SharePoint Server Publishing Infastructure if it's available... if it's not, you may be using SharePoint Foundation. Navigate to Site Actions > Manage Site Features, and activate the same feature (which should now be visible. Return to ...


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


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


3

Looks like you are missing the content type property in your element file, and possibly more: http://blogs.msdn.com/b/bobgerman/archive/2011/01/31/packaging-master-pages-and-page-layouts-with-visual-studio-2010.aspx


3

Starter Master Pages is a great resource for learning about SharePoint 2010 master pages and a good starting point for SharePoint 2010 branding projects From _starter_publishing.master <!-- s4-ca is the main body div --> <div class="s4-ca"> <div class="s4-notdlg"> <!-- links for I like it and Tags and Notes ...


3

Why would you not use the fact that _catalogs is a virtual directory in SharePoint and reference it like this: <scrit type="text/javascript" src="/_catalogs/15/masterpage/Display%20Templates/Filters/Filter_Default.js"> </script> (notice the slash at first, and the 15 telling Sharepoint to look at the 15 hive instead of the 14 hive from 2010) ...


3

In SharePoint, the main viewport of the webpage is not the html or body elements. Instead, they use div#s4-workspace, which is meant to take up 100% of the height and width (minus the ribbon). Try adding your overflow-y to this element: #s4-workspace { overflow-y: scroll; }


3

You can assign a master page in the layouts folder programmatically to a site (SPWeb). In PowerShell it would look something like: $site = Get-SPSite "http://yoursitecollection" foreach ($web in $site.AllWebs) { $web.MasterUrl = "/_layouts/15/yourfolder/themaster.master" $web.CustomMasterUrl = "/_layouts/15/yourfolder/themaster.master" ...


3

Your custom master page should NOT be residing in LAYOUTS directories, but instead to inside of a custom feature destined to "GhostableInLibrary". The reason being the performance and the fact that file itself will not be stored in the content database, and hence SharePoint will continue to use a cached copy of the file from the file system until it has been ...


3

You can deactivate "Follow documents" feature in your site to remove Share and Follow links. For SuiteLinks you can comment the following delegate control <SharePoint:DelegateControl id="ID_SuiteLinksDelegate" ControlId="SuiteLinksDelegate" runat="server" /> For others you may need to add css/js, following link should help: SharePoint 2013 Top ...


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

You have the option in the Page layouts and site templates page in New Page Default Settingssection. Select the page Layout that you need to set as default in Select the default page layout For new subsites, Write a feature stapler which sets your desired page layout on default.aspx, while the web provisioning process. or Create a custom web ...


2

It seems the reference term has changed in 2013. You can add the breadcrumbs in 2013 by adding the following snippet to your master page: <!--MS:<asp:sitemappath runat="server" sitemapproviders="SPSiteMapProvider,SPXmlContentMapProvider" rendercurrentnodeaslink="false" hideinteriorrootnodes="true">--> <!--ME:</asp:sitemappath>--> ...


2

I can confirm that it does it in my lab environment with using IE8... Vanilla 2013 install with default 2013 master. I'm guessing it's an IE8 limitation of not being able to process the gradient filter under zoomed condition. I'd probably write a custom CSS class to push a background color separately and see if that takes in scenarios where the gradient ...


2

When you create an AutoHosted App, the remote web is an ordinary ASP.Net web site, not a SharePoint site. This means that the SharePoint "extensions" to MasterPageFile like the special token "~masterurl/default.master" isn't working. You can/should still use a master page on the remote web if you have more than one page, but it'll have no connection to the ...


2

According to the ONET for Community sites it uses a page layout called welcomelayout2.aspx Located at ~SiteCollection/_catalogs/masterpage/welcomelayout2.aspx Full Module for default page: <Module Name="TopicsDefaultPage" Url="$Resources:osrvcore,List_Pages_UrlName;" Path=""> <File Url="Default.aspx" Type="GhostableInLibrary" > ...


2

The path is right, but maybe not the place where you added it in the masterpage. Some questions: If you debug your website, does the script get loaded at all? If yes, you could debug it to get specific error messages. Can you provide the whole <head> of the masterpage? Maybe the location is not quite right. I remember situations, where I needed to ...


2

I prefer using css rather than javascript. In your custom css file put this line to hide the buttons: #RibbonContainer-TabRowRight a[id$="_SyncPromotedAction"] { display: none !important; } #RibbonContainer-TabRowRight a[id$="_share_button"] { display: none !important; } It should work


2

This thread might provide some clarity. Masterpage and CSS are not applied in IE 8 If IE8 is indeed loading CSS in a different order than more modern browsers, you might have to be more specific in your CSS as outlined in the thread.


2

Going to leave this up here for anyone that might come across it as I've just worked out what it is. Settings.aspx overrides the content placeholders that my nav control is in: PlaceHolderTopNavBar PlaceHolderHorizontalNav I've just simply brought the nav control outside of these placeholders and hidden the placeholders (settings.aspx will put the nav ...



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