New answers tagged

0

Not sure if this is also made available for SP2013 on-prem but in O365 it should be possible as this was added to the API some time ago: https://blogs.office.com/2014/08/13/uservoice-driving-improvements-sharepoint-api/. Have a look here for an example: http://mosshowto.blogspot.nl/2015/10/branding-sharepoint-online-javascript.html. Snippet from the ...


3

Rather than using $(document).ready() try this: <script> _spBodyOnLoadFunctionNames.push("ButtonFunc"); function ButtonFunc() { $('.ms-qcb-leftzone').append('<li class="ms-qcb-item"><a href="http://www.google.com">ButtonName</a></li>'); }) <script> If this doesn't work check that the selector $('.ms-qcb-leftzone') ...


0

Try this: To remove: Look for 'PlaceHolderSearchArea' content place holder see if it's present in your custom master page. Move that placeholder to the bottom of the master page where all other hidden content place holders are. Also make sure there are no duplicates. <asp:ContentPlaceHolder ID="PlaceHolderSearchArea" runat="server" Visible="false" ...


0

Check again if you have publish the modified page layout and the correct master page is being referred to. Still its appearing then i will prefer adding a CSS attribute in the master page to hide the small search block.


2

It is not SharePoint Online ... It is SharePoint changing your URIs Cause SharePoint takes hold of all relative URIs Origin is the Publishing code where you can move any hyperlinked page in a SharePoint Libary to another library and SP will change any relative reference in other files Which is fine for ASPX pages and the relative links you have. But ...


3

SharePoint has difficulties dealing with protocol-less URLs. Have you tried changing them to https?


2

Follow below mentioned steps. 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 SharePoint Server ...


1

Firstly I agree with @Aveenav that you should look into the building wsp package, that will follow Sharepoint model, it will place the master page in layouts directory, push it if you connect servers etc. But if you really need to, you can place in the SP library, and call it from there (you can place in the layouts as well but you will have to keep that ...


-1

Try: {your site}/_layouts/15/ChangeSiteMasterPage.aspx Amal's answer didn't have the 15 in it. I don't have enough rep to add a comment to his solution.


0

Instead of using PowerShell, create a WSP package and hookup and event receiver for the feature that sets the master page. That way you can apply same master page to sub sites.


0

Try appending URL /_layouts/changesitemasterpage.aspx


0

Just a workaround if you have access to EventReceivers: Write a WebProvisioned Receiver and set the MasterUrl property of the new SPWeb object to the MasterUrl of your parent (or whatever Web you know of that is using the correct MasterPage).



Top 50 recent answers are included