Tag Info

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


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

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

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


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

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


1

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


1

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


1

A category is a predefined Term Set that is made in the term store management.


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


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

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


1

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


1

Try following: <SharePoint:UserField id="modifiedFieldCtrl" ControlMode="Display" FieldName="Author" runat="server"/> <SharePoint:FieldValue FieldName="Version" runat="server" ControlMode="Display" DisableInputFieldLabel="true"/> Custom Form Does Not Display "Created By" value


1

If you have an approval process set up for your wiki pages already then you should be able to go to whatever task list you're using with the approval process (Workflow Tasks or Tasks generally). In that you will see who has approved or rejected what and when they did it.


1

In case someone is interested in this discovery, I found a sort of workaround. By chance I have a Publishing Site and I have noticed it has the Page libraries "PAGES" and "Site Pages". The latter created by activating the publishing features. In Site Pages it does not work, but it works in the library called Pages. Why is that, I have no idea. You would ...


1

Site settings / Look and Feel / Navigation. Check Global Navigation and structural navigation


1

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


1

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


1

If you add a metadata column to a wiki library, the data can be changed by anyone with Edit rights in the wiki library. It shows as a field below the wiki content area. The wiki library can also be put into datasheet view and the new column data can be edited in bulk.


1

I would recommend that this be done in a wiki. You could also look at leveraging this to help users find your content and have this point to the wiki: https://www.nothingbutsharepoint.com/sites/eusp/Pages/press-f1-sharepoint-help-is-on-the-way.aspx



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