Hot answers tagged

6

The type of pages available by default (wiki vs. article and web part pages) is the primary difference. Since wiki pages in 2010 allow for web parts to be inserted, many people are now choosing enterprise wiki sites over publishing sites. The only big thing you lose with wiki sites over publishing sites are page layout templates. Wikis have some basic ...


5

To add what John said, Publishing sites are better when you are doing a .COM public facing site, when you need more publishing controls, more control over who can author, edit & publish, and when you want to enforce a specific look & feel & brand.


3

I have the same issue. I followed Ashish's directions but the Managed Metadata service was already checked. Going to my site's settings, editing the Wiki Categories column, under 'Term Set Settings' the options are greyed out and under 'Use Managed Term Set' is says 'The required feature is not enabled for this column type'. After some Googling it turns ...


3

My first thought was also for a Wiki site. When you get up to 2010 you get some added value in that you can use enterprise tags for the pages and users would also be able to leave notes/comments using the social features if you are using the Server version. The second option and something I did frequently in previous versions of SharePoint was a FAQ list ...


3

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


3

How to create a Wiki page via CSOM /// <summary> /// Create Wiki page /// </summary> /// <param name="pagesList">Wiki Pages list</param> /// <param name="pageName">Wiki page name</param> /// <param name="pageContent"></param> public static ListItem CreateWikiPage(List pagesList, string pageName, string ...


2

This means your Web Application is not taking services of "Managed Metadata Services" service application. Go to Central Admin -> Manage Web Application --> Select your Web app --> Select Service Connections and make sure you have Managed Metadata service available and Checked. If it is not available you need to configure a proxy so that that service can be ...


2

For SharePoint 2010 you could create a custom action to add a button to the ribbon which opens a new page to paste you source code into. Once the user closes the window some Javascript wraps the code into the pre tags and inserts it at the position of the cursor. UPDATE: You could use combination of the zoombldr.aspx page (used to edit the HTML source) and ...


2

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 Publishing feature needs to be enabled on site collection level and site level Go to site contennt and structure, and you can select one wiki page and move it freely to another folder.


2

This forum had another answer: How do I add categories to Wiki pages? basically check to see if column [wiki categories] has a term set tied to it.


2

For technical documentation, a wiki is much better, as you can easily interlink documents, add customization, and create a much better user interface. Word documents can be frustrating for technical documents especially for code snippits and things like API's. Wikis can handle code and structured formatting while word / pdf documents are well...documents. ...


2

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


2

There is a reason for this process. When you use an Enterprise content editor such as the Wiki portion of SharePoint (or Article pages for publishing sites) it is supposed to become a repository of all the items, text and multimedia and thus making it reusable. By placing it and coding it in an asset library (or image library) you are de facto making it ...


2

The short of it is you can't with workflow, they operate after the item has been added or changed. You need to use an event receiver to do that if you want to perform some operations before the item is saved. You would want to look at the ItemUpdating event, since you want to do it as part of the edit operation.


2

The SharePoint Server Publishing Infrastructure feature provides publishing functionality at the site collection level, Provides centralized libraries, content types, master pages and page layouts and enables page scheduling and other publishing functionality for a site collection. SharePoint Server Publishing feature provides publishing functionality at ...


1

This isn't set at the library level, it's set at the site level. Site Settings > Page layouts and site templates and add the layout to the page layouts list and seperately set the New Page Default Settings to your template.


1

The problem lies as you are updating Title with Name, the .aspx extension is also getting appended. Try updating the page name to something else and if it works then do a string manipulation in the workflow so that .aspx doesn't get included when you are copying the Name to Title. Please share your results for the solution, maybe I can help you better if it ...


1

Audience is not equal to Security! Audience on pages is mainly for showing / hiding the page from for example the current navigation, users will still be able to find and edit the page through links and site content for example


1

Looking at the call stack, and with the help of ILSpy to inspect the SharePoint code, we can see that: Your code fails at CreateParentFoldersForFile CreateParentFoldersForFile is called by CreatePagePage.NewPageItemSave. The only call to CreateParentFoldersForFile from CreatePagePage.NewPageItemSave is as follow: ...


1

No there is nothing like this ootb. You might be able to rig up something that takes input from when they create the page title and leverage search to pull back a list of possible matches, just like how the stack exchange sites work.


1

The SPFile object has a ForwardLinks and Backwards link property that contain SPLinkCollection that you may be able to query. Add-PSSnapin Microsoft.SharePoint.Powershell -ea 0; $web = get-spweb '<url>' $list = $web.lists['Pages']; foreach($file in $list.items){ $links = $file.ForwardLinks; foreach($link in $links){ if($link.url ...


1

You can create a custom permission level that does not allow deleting. You'd essentially copy contribute and deselect the delete option. This solves point 1. For point 2, there isn't really anything that handles this. Item level security settings on lists comes close, but it isn't fully what you need and isn't available in libraries. You'd probably need to ...


1

Try going to default.aspx. If it shows up, you can then set it as the default home page. Edit: Since that doesn't work, since that doesn't work. Go to Site Settings and go to the Page Layouts and Site Templates Settings link. In the Page layouts section, add (Welcome Page) Blank Web Part Page and any other page layouts you may want. Go to your Pages ...


1

I much prefer using a team site and use existing site features and apps to get the same effect that a specialized site template gives you, excluding the very specialized things like records center, video portal, etc. You said it yourself, mobile is key, they both methods create content the same way, both can have mmetadata navigation and filtering, and the ...


1

John, I found a few helpful links on comparing the two options. I think the most important difference you may want to consider is the metadata implementation. The library option looks to be more restrictive. While you can manually add metadata to Wiki Page Library, you can’t add the fields to the text layouts. This means users would have to edit the ...


1

I hear all the reasons why SharePoint doesn't support this, but this feature is currently the difference between our users using the SharePoint wiki and not using it. It is a shame too, because it has lots of benefits, but there are no benefits if no one uses it. In Office 365, both the OneNote and Outlook web applications now support pasting images in the ...


1

If the move is between same server Activate the site collection feature SharePoint Server Publishing Infrastructure. Go to the Site Settings page of the desired site which the Wiki Page libraries locate on, Click on Content and structure shows up under Site Administration. Select the page and use content menu to move the page to another library Different ...


1

This message will show when we edit the properties of a page no matter which library / wikis we upload it to, it seems to be by design. If you have any webpart on the page, once you click on it, it will give you control to perform maintenance on the webpart i.e. Close, Reset. Delete etc. To remove that i think you need to Customized the EditForm.aspx.


1

Here is what I found You change home page to new name SharePoint set site home page = new name Tries to change the name of actual file I believe step#2 should have been done after #3 or there should be a rollback mechanism


1

It depends on how you set up your managed metadata, since both ways are possible. Using enterprise keywords enables a tagging system where users can select existing keywords or create new ones. It's similar to tagging a question here, where you select existing tags or, if you have 300 reps, create new ones if they are needed. Keywords have no hierarchy, so ...



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