Tag Info

Hot answers tagged

7

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


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


5

You can try this solution: Open your site in SharePoint Designer, check out and open the default masterpage in advanced mode (assume it is seattle.master). Scroll down to ending </body> tag. Add the following block of code above: <SharePoint:ScriptBlock runat="server"> if (typeof jQuery == 'undefined') { document.write('<script ...


5

I'm afraid there is no better solution than to use CSS: To fix the icon in the left corner via CSS is pretty much straight forward because it's no icon is just a character out of the Office 365 icon font. #O365_MainLink_NavMenu{ color: lime; } The small css will turn the icons into lime. (OK it doesn't look nice but shows perfectly how they are ...


4

If you don't apply any particular style to a table inserted in a CEWP, it'll get applied the class ms-rteTable-default. So, instead of what you have done, you can override -in your custom css file- that class: .ms-rteTable-default{ -ms-name:"Tabell - test"; border:1px solid $borderColor; // sass syntax margin: 8px 0; width:98%; } Just make ...


3

Best Practice is to not do it - as Microsoft doesn't support it. "In SharePoint 2013 you cannot uninstall an imported design package, and you should never attempt to deactivate a design package through the solution gallery. If you do, page layout content types are removed and users may not be able to create subsites" Reference: ...


3

The RSViewerPage.aspx is a Out the boxed application page in the _Layouts folder. Application pages, which are also known as "_layouts" pages, are stored in a site's Microsoft Internet Information Services (IIS) virtual directory and support application implementations. Application pages are shared across all sites on the server, whereas a site ...


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

Here's the short version: Create a new blank SP project in Visual Studio. Add a new module and add your master page to this (in your case a copy of the Seattle master page with your changes). Configure this module to deploy to the master page gallery. Add a new feature (site collection scoped most likely) Include the module in the feature Add a feature ...


3

In order to overcome the tedium that ensues at the onset of every SharePoint 2010 design project, I have created a simple snippet of CSS that is intended to reset the SharePoint interface styles to inherit from your default document styles. Take a look at the SharePoint 2010 CSS Reset from Kyle Schaeffer. I didn't test it yet, but it seems to do exactly ...


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.


3

Actually the AdditionalPageHead delegate control is the way to go. To keep things simple I've wrapped the below code into the ASCX, but it would be better suited in an assembly deployed to the GAC. <%@ Control Language="C#" compilationMode="Always" %> <%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" ...


3

In SharePoint the "page" is actually inside of a DIV and the window really never scrolls... The content inside that DIV does scrolls (unless you have a customized branded site). So although your code will work on a standalone HTML page, it will not in a standard Sharepoint site (2010 and above)... See the solution I posted here to a similar question. ...


2

If I where you, I would try to ignore that warning and replace <div class="ms-rtestate-field">Page Content field value. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. ...


2

Two things; firstly, you're not creating a page based on a masterpage. The masterpage is set at the web level, not at the page level. What you're likely seeing is that the page layout you're using for the page doesn't contain any editable regions within SharePoint Designer, thus it wants you to put it into edit mode. Most of the time you're going to create a ...


2

Before considering using a third party tool, think about how often you will use it and if it's worth the additional risks of a third party framework. Not to mention that it will likely add unused code to the SP which will have an impact on the performance. If you only want a few layouts just do them yourself - it took me a few seconds to alter yours for a ...


2

You can type the url directly for lists folder : https://abc.com/Lists/ListName/NewForm.aspx?RootFolder=RootListName&Type=1&IsDlg=1 Type below url for Document Library folder: https://abc.com/DocumentlibraryName/Forms/Upload.aspx?RootFolder=%2fDocumentLibraryName&Type=1&IsDlg=1


2

That is pretty much the options or manually apply it via powershell etc You are using the SharePoint 2010, you can think about the sandbox solutions using event handler named WebProvisioned. Deploying Branding Solutions for SharePoint 2010 Sites using Sandboxed Solutions Most of the objects in a site are included and supported by the template. There are a ...


2

If this is part of a page layout, you can have a separate stylesheet for edit mode that relaxes your fixed width or removes your branding altogether to make it easier to modify web part properties. You would use an EditModePanel. I've done things like this in page layouts: <asp:Content ContentPlaceHolderID="PlaceHolderAdditionalPageHead" ...


2

This should be possible using AdditionalPageHead delegate control, That we we can avoid editing master Page


2

I think that the best approach in this case is create an app-part which will display your page and add it to a page on your host-web.


2

Branding in SharePoint The best way is to look at some youtube clips or tutorials http://blog.blksthl.com/2013/02/26/a-guide-to-quick-sharepoint-2013-branding/ You could make an composed look. see link below : https://www.nothingbutsharepoint.com/sites/eusp/Pages/Step-by-Step-Create-a-SharePoint-2013-Composed-Look.aspx You can try with this style in ...


2

In the latest version (16.0.3104.1200) of SharePoint Online Client Components SDK available for download currently, Web object exposes AlternateCssUrl and SiteLogoUrl properties: using (var context = new ClientContext(webUri)) { var web = context.Web; web.AlternateCssUrl = web.ServerRelativeUrl + "/SiteAssets/contoso.css"; web.SiteLogoUrl ...


1

At the moment, you would need to use jQuery. However, the Suite Bar in SPO has changed numerous times, so be prepared to make changes in response to those changes. The ability to customize the Suite Bar has been suggested in UserVoice. I suggest you add your vote there.


1

Try the following CSS, worked for me: <style> .ms-acal-rootdiv { margin-left: -8px; } .ms-acal-summary-dayrow > th { border-bottom: none; border-top: none; } </style>


1

If you're on on-prem environment, you can customize the SuiteBar, there's a delegate control for the SuiteBar which you can override. For SP2013 online environment, you'd need to use jQuery to add links to it and CSS for changing color, font and styles.


1

Aside from any API calls, why not just modify the master pages to include some javascript that sets a variable telling which master it is Var master="masters?asps"


1

how you want to detect. there are couple of ways to check which master page is being used. if you don’t have the Publishing feature activated navigate to http://your_server.com/sites/examples/_Layouts/ChangeSiteMasterPage.aspx If you do have the Publishing feature enabled you can go to Master Page on the Site Settings page, under Look and Feel ...


1

You can check browser with javascript as : var is_chrome = navigator.userAgent.toLowerCase().indexOf('chrome') > -1; And you can hide/disable web part as : <script type=”text/javascript”> document.getElementByID('MSOZoneCell_WebPartWPQ4').style.display="none"; </script> MSOZoneCell_WebPartWPQ4 is the id of web part.



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