15

SharePoint 2013 In 2013 you can use design manager for generating web-part zone snippet. To insert a Web Part zone snippet Browse to your publishing site. In the upper-right corner of the page, choose the Settings gear, and then choose Design Manager. In Design Manager, in the left navigation pane, choose Edit Page Layouts. Select the name of the page ...


14

Add <SharePoint:FieldValue FieldName="Title" runat="server"/> for Page title or <SharePoint:ProjectProperty Property="Title" runat="server" /> for Site title in one of the ContentPlaceHolders in the PageLayout, for the body in the <asp:Content runat="server" ContentPlaceholderID="PlaceHolderMain">


10

Wael actually had the correct answer. Here is the gist of what needs to be done for packaging a Page Layout: Using Visual Studio, you can create a new Module and add your page layout to that file. Then, in the elements.xml file for that Module, here is what I typically use: <Module Name="PageLayouts" Url="_catalogs/masterpage"> <File Path="...


9

Try using !important after your rule to override the inline style: #s4-titlerow{ display: none !important; }


9

I fixed it after wasting frustrating hours on this ! Its quite easy but doesnt make sense. Just add the HTML 4.1 (not HTML 5 - it wont work) char encode tag to the additional pagehaed placeholder, and it works like a charm. Make sure that you've tried the other solutions, may it's the result of a combination. Fact is, that it is already included in the ....


9

You can't change the .master file when it's bound like this, you can only edit the .html file. It will re-generate the .master when you save the .html. This is due to the Design Manager packet in SP2013. Here's the MSDN article on this feature set: http://msdn.microsoft.com/en-us/library/office/jj822363(v=office.15).aspx


9

The issue is that you should copy seattle.html which will auto create a .master page for you, and there is a link between the files. To resolve the issue, create a copy of seattle.html Now you have both a seattle_copy(1).html and seattle_copy(1).master. Next rename seattle_copy(1).html to for example test.html. A pop-up appears asking you to update pages ...


8

Add the following snippet: <WebPartPages:WebPartZone runat="server" Title="TestZone1" ID="TestZone1"> <ZoneTemplate></ZoneTemplate> </WebPartPages:WebPartZone> It works.


7

If you have deployed the CSS file to the Style Library or an Assets library, make sure it is checked in as a major version and approved. It could be possible that your page layout is not published and approved as well. This is the typical symptom when an asset is not approved, it works fine for admins but not general users.


7

Open in new tab is only supported in Publishing URL field. You are using the basic URL field. You need to use PublishingWebControls:RichLinkField. This will give you the "open in new window" option. Cheers!


6

The promoted links default size is 150x150 pixel. But you can always have bigger/smaller pictures and then manipulate the CSS for the promoted links if you want bigger/smaller tiles. Change the default tile size in Sharepoint 2013 Edit Add this to the bottom of the CSS before closing the style tag. .ms-tileview-tile-content img { width:100px!...


6

Since the control has a CssClass Property, you could manipulate the target attribute using JQuery. For example (not tested): <SharePointWebControls:UrlField ID="UrlField2" FieldName="Link Button" runat="server" CssClass="item-link" /> And on the JQuery side: $(function() { $(".item-link").attr('target', '_blank'); });


5

I was facing the exact same issue and resolved it by setting ReplaceContent="true" in the element.xml file of the module as below <File Path="MasterPageModule\MyMasterPage.master" Url="MyMasterPage.master" Type="GhostableInLibrary" ReplaceContent="TRUE" Level="Published"/> Also you can get it here https://blog.lekman.com/2013/06/page-layouts-and-...


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

I think this still holds true, http://blog.brianfarnhill.com/2008/10/showing-the-date-modified-date-on-a-page-layout <PublishingWebControls:LastModifiedIndicator runat="server" /> or <SharePoint:FieldValue FieldName="Modified" runat="server" id="modified" ControlMode="display" />


5

Since AdditionalPageHead is a Content Place Holder, you can use respective asp:Content control as shown below: <asp:Content runat="server" ContentPlaceHolderID="PlaceHolderAdditionalPageHead"> <!-- Add stuff here --> </asp:Content> You can add more Content Place Holders anywhere in the MasterPage and use them in the Pages.


5

How to update Page Layout for a Page via CSOM (JavaScript) function updatePublishingPage(pageUrl,properties) { var context = SP.ClientContext.get_current(); var site = context.get_site(); var web = context.get_web(); var pageFile = web.getFileByServerRelativeUrl(pageUrl); var pageItem = pageFile.get_listItemAllFields(); context....


5

How about something like this: <script type="text/javascript"> _spBodyOnLoadFunctions.push(function(){ ExecuteOrDelayUntilScriptLoaded(showStatusAlert, "sp.js"); }) function showStatusAlert(){ var ctx = SP.ClientContext.get_current(); var web = ctx.get_web(); var list = web.get_lists().getById(_spPageContextInfo.pageListId); var ...


5

Option 1 How to add/upload publishing page layout via CSOM in PowerShell: [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client") [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client.Runtime") Function Get-ClientContext([string]$Url,[string]$UserName,[string]$Password) { $SecurePassword = $Password | ...


5

What you have described in your question is not called a site template , it's called a page layout as shown below : So To create a page layout follow the mentioned steps below Browse to your publishing site. In the upper-right corner of the page, choose the gear icon, and then choose Design Manager. In Design Manager, in the left navigation pane, choose ...


5

I think your issue is using for(let i = 0 syntax. It has not worked very well in IE < edge: https://stackoverflow.com/questions/39159669/let-statement-in-loop-doesnt-work-as-expected-in-ie


4

Thanks Robert! I am banging my head on the wall for this! Basically you don't have to add a code just to show the ribbon by default. Just go navigation and tick NO to show or hide command ribbons. According to the error that i got below, it is referencing to a script outside our domain. Webpage error details Message: Script error Line: 0 Char: 0 Code: ...


4

In site settings there is a section to select what page layouts are available on that site. You can set this to inherit or choose specific page layouts. That would be the first place to check.


4

Yes, there is. In the list go to List Settings > Form Settings and tick "Use the default SharePoint Form". If you keep the option "Delete the InfoPath form from the server" unticked, you can later switch back to the IP form. If you tick that option, it will be gone for good.


4

A page layout adds controls to the page. The page itself is constructed dynamically, so it cannot be edited in SharePoint Designer. You can edit the page in the browser and add a Content Editor Web Part into the page body. You can then link that CEWP to a file with javascript, css or html. This is the usual workaround to inject custom elements into a page ...


4

I guess this will do the trick.. But I haven't tested it. $site = get-SPSite http://mysite.com $web = $site.RootWeb $pweb = [Microsoft.SharePoint.Publishing.PublishingWeb]::GetPublishingWeb($web) $pPages = $pWeb.GetPublishingPages(); $pLayouts = $pweb.GetAvailablePageLayouts() foreach ($pPage in $pPages) { if ($pPage.Layout -eq $pLayouts) { ...


4

This might classify as more of a work-around than a solution, but I used the guid of the view as the webpart id. I decided to look into the content database to see how views are stored. In the stored procedure proc_CreateView I found that views are actually stored in the AllWebParts table with the ViewId inserted into the tp_ID column. So I added the ...


4

In the master page there is a place holder for the additionalpagehead . Make sure the jQuery reference Comes before that. that way the jQuery reference will be processed first


4

Probably the most simple option would be just to hide List View Toolbar Open the page in Edit Mode Go to XLV web part properties and specify Toolbar Type: No Toolbar That's it. P.S. Of course, you could accomplish the same task using CSS or JavaScript , but what for..


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