The message means that you (or somebody else with permission) have made customizations on the page which deviates from the page template. This is a state of the page called un-ghosted.
If you don't want these customizations, simply click the link "Revert to template" and the page will go back to use its template (ghosted).
If you simply want to remove the ...
Even though this is just a Wiki Page Library the WelcomePage property will work. Here is how you can set it using PowerShell:
$web = Get-SPWeb http://sharepoint
$list = $web.Lists["Second page lib"]
$list.RootFolder.WelcomePage = "How%20To%20Use%20This%20Library.aspx"
The page you set it to should exists otherwise it choose the ...
Difference in General
In wiki page library, people store wiki pages & web part pages (.aspx). It's an interconnected set of easily editable web pages, which can contain text, images and web parts.
In document library, people store documents like .doc, .pdf, .xlsx and etc. You can use a document library to store, organize, sync, and share documents with ...
As mentioned in other answers, SharePoint's wiki includes a ribbon which allows you to do most things. The disadvantage to this is that this information is not encoded in the editable markup. If you prefer your markup to be visible, read on.
Placing double square brackets around content creates a link to a page of that name on the root of the ...
Which will work best to achieve my requirements; to have a wiki site
or to have a blog site OR there is a better approach to follow?.
I would rather have an Enterprise Collaboration Site with Publishing Feature enabled for the requirements mentioned below. It just gives the little extra "room" for managing content. And then as and when required configure ...
I'd say that there is no such thing as "child page". If you need to create a hierarchy, then HR has to be a container. Within this container you would have the default page and then other pages. Just like what SharePoint does with sites.
If for some reason all your pages need to be in the same container, then you cannot expect SharePoint to understand your ...
You need to pass the parameter ControlMode=Edit and DisplayMode=Design to the aspx page if you like to open it in edit mode.
Just replace "yoursitehere.com" with your own site page ...
You did not mention what kind of error occured, but most probably it is related with filename parameter. AddTemplateFile endpoint accepts relative file Url for urlOfFile parameter.
How to create a Wiki page via SharePoint REST API
The following example demonstrates how to create Wiki page via SharePoint REST API.
Since AddTemplateFile endpoint accepts ...
The send to location does not work on wiki pages library, but there is the possibility to move items from one folder to another inside the same site
Note: Publishing feature needs to be enabled on site collection level and site level
Go to Site Settings
Go to Content and Structure
Select wiki pages to be moved with tick box to the left of the page name
There are some samples for uploading a generic file using the [...]/Add REST endpoint:
But Wiki pages need to be added using the [...]/AddTemplateFile REST endpoint:
SharePoint and Confluence are two separate platforms for different purposes which do share similar functionality, are based on completely different technology, and for which can be difficult to move users either way.
Nothing has really changed. SharePoint 2013 does bring more to the wiki world and is making strides towards offering what Confluence has but ...
There is no OOTB capability in SP 2013 that will let you have a table of contents from a selected portion of content, however there are some nifty workarounds available mentioned below you can try it out.
Add navigation table to wiki page
SP 2010 workaround, should be valid for 2013
There should be a 'Page' tab in the ribbon interface. On here is a section labeled 'Manage' that has the following options:
The 'Page Permissions' button allows you to stop inheriting permissions for that page and set your own custom permissions.
Append Web=1 to the url to instruct it where to open.
Of course you have to have all the prereqs in place.
Opens it in Excel Services web page
Opens it in excel
Yes there is difference, Below might be helpful to understand.
Document library can contains documents, it can be any document like office documetnts doc,xls,ppt, js, css, jpg, png etc...any file extension you can think of. Main purpose of document library is to store documents.
wiki library is a kind of document library which contains wiki pages, Wiki ...
I use the following block of Powershell to update an existing wiki page. The tricky bit was the pre-formatted block of 'boilerplate' html in the "ows_WikiField" field that wraps the page content. If the content wasn't wrapped properly in this html, it wouldn't work correctly.
As stated, this block of code updates an existing page. Creating a new page ...
You will need to write a custom import tool with the Client Object Model. If your export is well formatted in XML, it should not be very difficult. You need to import the HTML content of each page into a new Enterprise Wiki page in SharePoint.
That's the short version... In practice, there are a number of things you might want to tweak: parse and replace ...
If this is just a Wiki Library rather than a site then the Welcome Page setting won't help since this affects the whole site.
If you are just looking to have the Wiki Library default to the All Pages view then rename Home to anything else.
If you want the main page to be a specific page you've already created, just rename it to Home.
Automatic redirect based ...
The standard, simplest way of doing this is to use built-in wiki functionality:
Type [[ then wait for the drop-down menu which should show other pages in the same library at the end of the menu 2 options -Lists and Views.
Use keyboard Arrows ↑ and ↓ to select LISTS(very important: DO NOT USE MOUSE as the menu is quite Sensitive)
Press the TAB key. This ...
Ok, I've found the answer. To make Bookmark field visible, SharePoint Server Publishing Infrastructure feature (site collection level) must be activated. To enable this field (after previous step it'll be visible but disabled) SharePoint Server Publishing feature must be activated (site level).
This generally boils down to differences between Word's way of representing a document and HTML/CSS's approximations of such. One of the big areas they differ is indentation - SharePoint does its best to migrate the formatting but it doesn't always work.
There are a couple things you can do about this:
Use another tool to convert the document into HTML/CSS ...
You can use workflows to accomplish this. Turn on Content approval, then create a workflow that has the email and approval elements you require. Here are some resources to help you along:
Get started with workflows in SharePoint 2013
SharePoint 2013 workflow fundamentals
I found a working example at. https://web.archive.org/web/20150710164136/http://spdevlab.com/2013/03/28/creating-wiki-web-part-and-publishing-pages-via-csom-in-sharepoint-2010/. This example worked on the first try without issue.
Another option is to create a OneNote notebook in SharePoint and then let your team use that for a lot of their documentation.
It is synchronized between SharePoint to their local PCs so the content
is available to the team members even when they are offline. Offline updates are sync'd into SharePoint the next time they are online
OneNote's structure is ...
Recently I updated my Add navigation table to wiki page solution to support multiple levels and SharePoint 2013.
The new solution is a configurable jquery plugin and is documented in the blog post Revised: Table of Contents for Wiki Pages
Thanks for the help
This is what I came up with:
Add-Type -Path 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI\Microsoft.SharePoint.Client.dll'
Add-Type -Path 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI\Microsoft.SharePoint.Client.Runtime.dll'