Tag Info

New answers tagged

0

I found out where the problem was: during the deployment the CONTENT TYPE of the layouts was changed from PAGE LAYOUT to file. Changing that, the page layout appears again into the available page template.


0

PageLayout does not expose property that stores absolute url, use PageLayout.ServerRelativeUrl property to construct full url of page layout. Option 1 You could utilize SPSite.MakeFullUrl method to return the full URL for the specified server-relative URL of page layout, for example: $site = Get-SPSite $siteUrl $web = $site.RootWeb $pweb = ...


1

For reference to others, I had this exact same issue. I was getting it in within a Console application on a specific environment, where I copied Publishing Pages from one site collection to another, iterating over a list of sources and destinations. My utility also copied web parts, and for some reason I thought I had to Fake the SPContext (Google it, your ...


0

I would create a custom page layout for that. Then create the 200 pages and configure the fields (the propertise of the pages) that the page layout uses to do the queries. Do the queries either with a Search WebPart or a Content Query WebPart.


0

I would just use Content Query Web Part with custom XSL template to get the desired look and feel. In CQWP you can define the actual query, including pointing it to show items from your new list. Edit \Style Library\XSL Style Sheets\ItemStyle.xsl and copy existing template, rename your copy (change name and match properties) and modify the HTML it provides. ...


1

I think the issue is the value your retriving is not getting it at the correct moment first time round. Thats why on the second postback it would get the correct item value and its loaded within the context properly. have you tried calling the method out of the page load event? so at bottom code just do showStatusAlert(); instead. or use this method ...


0

check-out then check-in the page layout and the master pages , and i publish them as majot verisons and now the page layout is working well. –


0

After much research and crawling through the internet I came across this article: http://blogs.msdn.com/b/uksharepoint/archive/2011/04/04/provisioning-web-parts-to-a-page.aspx There are many articles like this but in the beginning of the article it explains my issue quite succinctly: Embed references to the web parts directly in the mark-up of the aspx ...


1

On a teamsite for instance - do the following: Activate the following features: Site Collection Features - SharePoint Server Publishing Site Features - SharePoint Server Publishing ~ Navigate to the page library (Pages) ~ Create a new page ~ Set the new page as the welcome page of your site ~ Delete the SitePages library From now on, you will fully use ...


0

You have to activate the SharePoint Server Publishing Infrastructure Site Collection Feature and after that you can activate the SharePoint Server Publishing site (web) feature. This will create the necessary libraries (Pages library) inside the current web and you should be able to select a page layouts (for pages residing inside the pages library). I ...


1

try using the below script in CEWP: <a onclick="modalcall()" href="#">Add New Item</a><script type="text/javascript"> function modalcall() { SP.UI.ModalDialog.showModalDialog({ url: "NewForm.aspx", title: "New Item", //allowMaximize: true, //showClose: true, dialogReturnValueCallback: ...


0

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


1

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


0

Having reflected the assembly that provides the SetAvailablePageLayouts, I can confirm that all it is doing is setting the "__PageLayouts" web property (and pushing this update to child webs). As such using CSOM to set the property should be sufficient. I assume that the GUID is the UniqueId of the page layout in _catalogs/masterpage gallery.


0

A publishing layout is meant to provide a framework for page content. By its very nature, the layout elements are static and only the content controls can be manipulated by the user, i.e. adding text, images, links, etc.. Although web parts can be integrated into a page layout, the web part's settings will be static and not customisable. You may want ...



Top 50 recent answers are included