25

Let me see if I can explain pages in SharePoint without making you even more confused. The difference between the different kind of pages very much depend on whether your view is as developer or as end user. As you're refering to MSDN I'll start with the developer view. SharePoint Pages from a developer point of view From a developer point of view there ...


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


12

It could be achieved with HTTP Redirect in IIS using IIS URL Rewrite module. This module allows to create various rule actions including redirect and request abort. For your scenario i recommend this option because this should redirect the request faster as the redirection happens as soon as the HTTP request received by IIS. Configuration Let's describe ...


8

First create your User Control and publish is to SharePoint. Then you register a tag for your control <%@ Register Tagprefix="MyControls" Namespace="KM.MyControls.MyControl" Assembly="KM.MyControls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=<Your token>" %> Then you can reference your User Control <MyControls:MyUserControl ...


8

You can use a standard HTML redirect with a wait period of 0: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Redirecting...</title> <meta http-equiv="REFRESH" content="0;url=http://www.yoururl.com"> </head> <body> </body> </html> Changing the ...


7

Make sure you put the user control into a subdirectory of {SharePointRoot}/Templates/ControlTemplates Put a Register element at the top of you page-layout <%@ Register TagPrefix="MyOwnPrefix" TagName="MyUserControl" Src="~/_controltemplates/MyProjectName/UserControl.ascx" %> and the refer to it where you need it like: <MyOwnPrefix:MyUserControl ...


7

SP.File.checkOutType property gets a value that indicates how the file is checked out of a document library Get file checkout type via REST $.ajax({url: "/_api/web/getFileByServerRelativeUrl('" + pageUrl + "')/checkOutType", headers: { "Accept": "application/json; odata=verbose" }, success: function(data) { if(data.d....


6

There are a few things that control this in site settings --> navigation. Managed Navigation -- use a term set for navigation Add new pages to navigation automatically -- a new item is added to the termset for each new page Create friendly URLs for new pages automatically -- This is what you're concerned about - the page shows up in the URL without the ....


5

I prefer not to create sub-sites for navigational structure alone - mainly because it is hard to change the structure again. But you actually have some good alternatives when you are willing to create a custom navigation data source. Below are two options that will also not require you to create folders in your Pages library. They also make it harder to ...


5

You can use the Client Object Model to get a reference to the file and then use the checkOutType property to see if it has been checked out. SP.File.checkOutType property


5

They're both working, thanks! I've found another way, a little faster because it doesn't need to call the server back again, but it can only to determine if the file is checked out by the current user, not by a generic user. I've found a way to achieve this, tested on Sharepoint 2013. Just add the following script inside a script webpart after putting ...


5

As a workaround try to rename yourhtmlpage.htm to yourhtmlpage.aspx then it will be displaying in the browser.


5

When a page is checked-out, the check-in and publish works as follows. Check-in: Increments the page version. The new version is visible only to users who have Full Control access and above. Publish:: Increments the page version by check-in automatically and visible to users who have Read access and above.


4

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


4

Hi Take a look at this tool, http://spcrew.com/blogs/lists/posts/post.aspx?id=18 it makes use of swapping page layouts. has been very helpful


4

Please have the following steps closely followed to create a custom richtext control inside your page layout and have it display with chrome. Create a custom content type a) Go to site settings > Galleries > Site Content Types > Create > followed by the screenshot as mentioned below Save the content type and you will be redirected to the newly created ...


4

If you're using SharePoint 2010 you can use List validation: Make sure your Page layouts include "Scheduling Start Date" Go to the Pages library Select List settings in the Library tab of the Ribbon Select Validation Settings Enter a formular like =[Scheduling Start Date]>TODAY() Enter an appropriate user message like "Page must be scheduled into the ...


4

Wiki page is like wikipedia pages. We allow user to edit the pages. Application page is the page which we can use the same page in different site collections or websites. Suppose if we want to show custom error page with nicely designed interface in each of our site collection then we can create an application page and give the redirect url to that ...


4

Without code On library click Create new view based on for ex. All items. Check columns you want to view and sort it how you like. Under Filter click Show items only when the following is true Approval Status --- is greater than --- 0 << this is for all unpublished(Rejected, Pending, Draft) Click OK For Published view create one more view with ...


4

The answer to this question is: No, it is not possible to create another library with the same functionality as Pages on a publishing site.


4

Your speculation is correct, the example provided in the question is intended for creating a wiki page and not enterprise wiki publishing page. Since you mentioned in your question JavaScript Object Model (JSOM), the below example demonstrates how to create enterprise wiki page via JSOM in SharePoint 2013. How to create enterprise wiki page using ...


3

I would suggest the use of native policies (like in our case the expiration policy) that you can attach to a specific content type and trigger an action / workflow when the policy is met. In this case it will be when an item's age is reached. (eg : http://technet.microsoft.com/en-us/library/cc262112%28v=office.12%29.aspx) What I've been doing for a customer ...


3

I think that the simplest way is to use custom web part. This web part should be added to the default.aspx and checks users. If the user belongs to the needed group the web part redirects this user to a different page.


3

I believe you need to goto site actions -> site settings -> page layouts and site templates -> then their is a radio subsites can use any site templates


3

Here are a few more differences I've encountered when working with both Wiki Pages and Web Part Pages, from a more practical standpoint: Wiki Pages Can place web parts inline with text and freely drag and drop them anywhere, including, for example, within cells of an HTML table, providing a means for very precise layout. Can choose from 8 "Text Layouts", ...


3

Perhaps you can change the Welcome page to subsite homepage. To do this Go to Site Settings > Look and Feel -> Welcome Page


3

Maybe you can try this script? The script takes three parameters, the old or current page layout name, the new page layout name and an optional –all parameter which will traverse all the sites of a site collection. # Description: # Update the layout page for all matching pages of the current page layout # Checkout, Change layout, Check-in pages in a site ...


3

I had the same issue on a Publishing Page Libary. I set the toolbar to No Toolbar on the AllItems.aspx page. Removing the toolbar causes the page to stop processing. Browse to the AllItems.aspx page and edit the page > edit web part > check tool bar type. Set to Full Toolbar and save. This should resolve the issue.


3

There are various ways: // Stop Caching in IE Response.Cache.SetCacheability(System.Web.HttpCacheability.NoCache); // Stop Caching in Firefox Response.Cache.SetNoStore(); or you could use the @Output property: http://msdn.microsoft.com/en-us/library/ms178606(VS.80).aspx http://msdn.microsoft.com/en-us/library/hdxfb6cy(v=vs.80).aspx Here you can find all ...


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