Tag Info

Hot answers tagged

7

Adding to iambriansreed's solution, you can put the comments in Literal controls around the SPSecurityTrimmedControls to prevent SPD from adding the extra rubbish. For example: <asp:Literal runat="server" text="&lt;!-- "/><SharePoint:SPSecurityTrimmedControl PermissionsString="EditListItems" runat="server"><asp:Literal runat="server" ...


7

The short story: Usually you'll set the master page as both default and custom master page, the most common exception being a very customized master page for publishing which can't be used for ordinary pages in which case you'll only set it as custom master page. The full story: When creating pages in SharePoint your main options for setting the ...


5

As Sig suggested there are some changes to the way IE9 handles javascript from previous versions. I found my answer in /_layouts/1031/init.js in the function ProcessImnMarkers() (Ironically, a function you want to overwrite as empty if you actually WANT to hide the IM Presence stuff). Here is the original code of the function: function ProcessImnMarkers() ...


5

I would advise against this...I would also advise against having an exact copy of the coreV4.css file. Having both these files is going to beef up the load times and increase the needless amount of code the browsers need to go through. Change your CSS registration to the following line. I also always add it after the CoreV4.css not that it makes a ...


5

After long investigation I found solution. It is both SharePoint and IE 8 specific problem. IE 8 loads styles in different order, than IE 10. In IE 8, after my custom css, class .ms-core-needIEFilter was loaded. The class has gradient inside. I added to my custom CSS following code: .ms-core-needIEFilter #suiteBarLeft { background-color:transparent; ...


5

Try adding the path, as you have done in Name also, in After. Or since you have the css files directly in the 15, remove the path from the Name property. First option: <SharePoint:CssRegistration runat="server" ID="Custom2" Name="/_layouts/15/Custom2.css" After="/_layouts/15/Custom1.css" /> Second option <SharePoint:CssRegistration ...


5

You will need something like this: <Module Name="Masterpage" Url="_catalogs/masterpage"> <File Path="Masterpage\mynewmasterpage.master" Url="mynewmasterpage.master" Type="GhostableInLibrary" Level="Published" ReplaceContent="TRUE"> <Property Name="Title" Value="My New Masterpage" /> <Property Name="UIVersion" Value="15" ...


4

The easiest and cleanest way to do this is wrap the control with html comments: <!-- <Sharepoint:SPSecurityTrimmedControl runat="server" Permissions="CreateSSCSite"> --> <SharePoint:CssLink runat="server" Version="4"/> <!-- </Sharepoint:SPSecurityTrimmedControl> --> If the user meets the permissions then it returns: ...


4

The line <Property Name="QueryPromptString">$Resources:MyResourceFile,ResourceKey</Property> wokrs fine for me. I think that you should check your resources file. This file should contain ResourceKey which you tries to use in this property. If you use correct resource file and key, the search control displays text depends on the site language. ...


4

Since your master page is now unghosted (= customized = not anymore retrieved from the file system), you'll have a newer version. You can roll back to a previous edition (v1.0 as provisionned by MS) to put you back in a working state. Go to {Your-Site-Collection-Url}/_catalogs/masterpage/Forms/AllItems.aspx, select the v4.master, history and roll back to a ...


4

I believe the only difference is their page layout and navigation. Seattle is what we're used to from 2010, and Oslo is new, moving the left nav to the top, and removing the top navigation all together. Oslo has a wider layout for your content.


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

Append /_layouts/changesitemasterpage.aspx to your site URL. You will get the option you are looking for.


4

These links are loaded dynamically using the delegate controls so you wont' find these link in master page. To hide these links, add the following to your css file referenced from your master page (suggested) or add it to your master page. <style type="text/css"> #Suite_MainLink_ShellMail, #Suite_MainLink_ShellCalendar, #Suite_MainLink_ShellPeople, ...


3

You should be able to create your own control inheriting from Sharepoint:SPSecurityTrimmedControl and override RenderBeginTag and RenderEndTag to do nothing


3

This works! (DropDownList)this.Page.Master.FindControl("myDropdown");


3

I would highly recommend you to start with the Starter Master Pages project by Randy Drisgill over at codeplex - http://startermasterpages.codeplex.com/. In my openion its the best starting point to create a custom master page in SharePoint 2010...


3

The trickiest part of this is making sure the brand gets used for all new mysites created from this point on. To do so you need to make sure your branding conforms to a key prerequisite. Is your brand packaged up in a visual studio .wsp and can it be applied to a given site collection by activating one or more features? If so then you can apply it to all ...


3

There is a out of the box content placeholder containing the site name that can be placed inside your masterpage. I believe Randy has it included in the block of content placeholders at the bottom of the page, and you can just bring it up to where you want it. <asp:ContentPlaceHolder id="PlaceHolderSiteName" runat="server"/>


3

Insert <SharePoint:ProjectProperty Property="Title" runat="server"/> into the masterpage where you want it. Or if you want it like the default v4.master with a being in the PlaceHolderSiteName ContentPlaceHolder as a link, then use <asp:ContentPlaceHolder id="PlaceHolderSiteName" runat="server"> <SharePoint:SPLinkButton runat="server" ...


3

A simple PowerShell script would do it. There's a MasterUrl and CustomMasterUrl property on the SPWeb object, so you could just do something simple like Get-SPSite | Get-SPWeb | % {"Site: " + $_.Url + " Master: "+ $_.MasterUrl} to list out the master for every web.


3

Customizing Meeting Workspaces is not as straight forward as one could expect unfortunately (both SP2007 and SP2010). First of all you cannot use Web Templates or Custom Site Definitions because Outlook often will be the one creating the sites using web services, and it is only aware of the OOB site definitions. As i stated in comments elsewhere, feature ...


3

Hi custom master page is site master page used for publishing pages only and default master page is system master page, to know more please leaf through this article http://rehmangul.wordpress.com/2009/12/15/master-pages-in-sharepoint/


3

If your custom master page has the same ContentPlaceHolders as the default one then you can use PlaceHolderAdditionalPageHead this is where a lot of the standard SharePoint pages add meta tags


3

Since you cannot access the site's normal, web-based UI: Use SharePoint Designer 2010 and in the Site Objects navigation menu on the left, select Master Pages. Right click your v4.master and either reset to a specific version or edit it to make the required changes. Something is going to have to give. There is no magic spell that can fix the issue. You will ...


3

To use Client OM, you need a reference to SP.js For production: <SharePoint:ScriptLink Name="sp.js" runat="server" OnDemand="true" Localizable="false" /> For development purpose: <SharePoint:ScriptLink Name="sp.debug.js" runat="server" OnDemand="true" Localizable="false" /> Moreover, there is also another way to declare it using the ...


3

Go to Site Settings . Under Web Designer Galleries click master pages and page layouts. Look for your master pages version history. Then reload to the which version you want.


3

Go to your site/_Layouts/ChangeSiteMasterPage.aspx and set the System master page as V4.master (I assume you're working in SP2010), to apply the default look and feel for pages like viewlsts.aspx, site settings and so on.


3

Medes, Don't remove the PlaceHolders from MasterPage, bad bad practice! As they are used by SharePoint internally to place content accordingly on the pages... Below URL gives the list of Default Content Place Holders and information that is kept into them [It is for SharePoint 2010, but I hope not much changes are there]: Working with content placeholder ...


3

To do this properly, leave corev4.css alone and define your own custom CSS file that includes only the CSS classes that you want to override. CSS loads in order so as long as your custom CSS is loaded after corev4, your styles will be applied. Since your new file includes only the CSS classes that were modified, it will also be much easier to manage than ...



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