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.


5

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


5

Man, this took me an embarrassingly long amount of time to figure out, so don't feel bad. But if you go to the library settings for your enterprise wiki, and open up the settings for the categories field, you'll notice that you need to actually assign it a managed metadata termset before you can have users enter items into it. Some instructions: My ...


4

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


4

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


4

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


3

you cannot paste the images into sharepoint pages directly, Images cannot be rendered as HTML so cannot be pasted. You have to upload the images into SharePoint then insert it on the pages /places you want. Or you can try 3rd party tool for this. http://www.kwizcom.com/sharepoint-add-ons/SharePoint-clipboard-manager/overview/ or http://www.telerik.com/...


3

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


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

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


3

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


3

There isn't a need to develop anything, this functionality is readily available with out of the box features. In your wiki library, you create a view grouped by your page type, it would look like this, no need to use totals like I had mentioned, the grouping takes care of this for you: Configure the view to include the desired columns. When expanded, it ...


2

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


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

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

Enterprise Wiki: enable the Publishing Feature for the Site Collection Create a page layout based on the Enterprise Wiki Page In SPD, edit the properties of the tag PublishingWebControls:RichHtmlField (turn on the Properties panel) There's a whole raft of properties that you can toggle from TRUE to FALSE to allow/disallow Fonts, styles, links, etc. Save ...


2

Switching between SharePoint Online (Plan 1) with Yammer and Office 365 Enterprise E3 made no difference. Copied formatted text from Word 2013 was pasted in a new Enterprise Wiki page. Every formatting pasts correct with formatting information. Header 1 in Word is Header 1 in the Enterprise Wiki page, bold is bold, italic is italic and so on. Everything ...


2

You can take advantage of browsers ability to paste base64 encoded images into editable content. But since sharepoint's editor strips base64 images you can use a dirty trick to store image contents to hidden placeholders that don't get stripped and then render images back from these placeholders on page load. There are pros (it does the job, its easy to use ...


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 SPFile object has a ForwardLinks and BackwardsLink 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 -...


2

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


2

I would recommend that you just set individual permissions for any pages that require it. The best method is to create security groups in SharePoint, disinherit the parent permissions on any relevant pages, and then specify the security groups that can access and edit the pages. To do this, Go to any wiki page and then click Page to open the ribbon menu ...


2

I have tested in SharePoint RTM and SharePoint with July 2017 CU (15.0.4945.1000), but cannot reproduce your issue. Here are my test steps and results: Open an Enterprise wiki site and create a term set using “Create Term Set” option in the navigation settings page. Open Term Store Management Tool to check the term set. The “Available for Tagging” option ...


2

I would not hesitate to use the designer, not a single day goes by where I don't use it during work (SharePoint consultant). I don't see why you would be using it for wiki's though, but for workflows most definitely.


2

I can only partially answer your question. I can't speak to the questions surrounding the managed metadata columns or metadata navigation, but I can try to clear up some of your confusion over indexed columns and the list view threshold. The way to manage large lists is to create a view that has a filter using an indexed column that will return less than ...


2

I too can reproduce, but the only workaround is not to use OOB validation. The only alternative I can think of is to use JavaScript. Put something like the following in a script editor web part on the new and edit forms: <script type="text/javascript"> function PreSaveAction() { var input = document.querySelector("input[id^='ExpireDate_']"...


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

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.


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