Tag Info

Hot answers tagged

12

Actually, almost all the SharePoint wiki markup is provided through the GUI (on the ribbon). So, there is no special SharePoint wiki syntax, except [[links]] syntax. where can I find the documentation? When you create standard "Team Site", where is a page with tips on wiki markup, which mention [[ command to create internal links. The url of this page ...


7

This is a tough one. It's unreasonable to expect that the SharePoint team would be able to build a better wiki than people who only build wikis. They're not going to build a better blog engine than people who specialize in building just a blog. So the "SharePoint wiki is better than XYZOpenWiki" argument is probably one you are going to lose. I think you ...


6

I'm not aware of changes to the wiki "language" used in SharePoint 2010. The user interface has certainly improved. For example typing the [[ characters will present a drop-down menu of available items to choose from (see this post by Michal Pisarek). If there are certain language features you are looking for, please update your post with more details.


5

You can add as many web parts to a wiki page as you want. You can use either the Text Layout button (on Ribbon) to do things like split the page up into multiple columns. If that doesn't give you granular enough control then add a table (use Insert > Table) with 1 row and 2 cols and add the web parts into the cells.


5

If I understand the question, you are looking for a client-side editor, rather than using the editor in-browser. I don't think there is one - you are stuck with either the in-browser editor that comes out-of-the-box or a third party one such as Telerik. The Telerik editor used to be widely used in the 2007 version of SharePoint, but in 2010 the built-in one ...


5

Sharepoint wikis are just not enterprise worthy. We gave a lot of feedback to Kevin Davis, the former PM for wikis, about how poor they were. I was excited they were taking feedback about the feature but it seems that none of the suggestions the community made got rolled into the product. If users need a robust wiki, then trying to pigeon hole them into ...


5

You can also use the two together. I played around with the SharePoint Connector for Confluence when it was in beta about 3 years ago and it looked pretty solid. I was able to get the benefits of the Confluence wiki from within SharePoint through some web parts (the SharePoint 2007 wiki was horrible) while also being able to use SharePoint for what it is ...


5

The community kit for SP - Enhanced Wiki Edition on CodePlex has a wiki which provides custom wiki markup and tokens.


5

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


4

I'm lifting the answer I wrote for a similar question on Stack Overflow, since it seemed reasonably well-received there: We run into this topic all the time, and the first question I have taken to asking people is "Why do you need a wiki"? Almost always the answers are things "ease of editing", "multiple contributors", and "Word is to heavyweight". Very ...


4

I think that Live Writer still doesn't work with SharePoint Wikis directly. There are some rather unpleasant workarounds in this old thread http://stackoverflow.com/questions/11462/sharepoint-wikis if you want to give them a try. p.s. I found that with a quick Bing. I knew it was out there somewhere, but still...


4

Unfortunately, I think that the answer is "no". I've also answered your other thread about using Live Writer, which I don't believe is possible; I just tried to set it up again, and it still doesn't work. Live Writer is built for blogs. EDIT: SharePoint is a Web-based application, so that's the editor: the browser. You can enhance SharePoint to work better ...


4

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" $list.RootFolder.Update() The page you set it to should exists otherwise it choose the ...


4

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


4

If you can drop a Content Editor web part into the page you can add an anchor and some javascript into the web part that looks like this: <a href="javascript:history.length&gt;0?history.back(): window.location = &#39;http://yoursitehere.com&#39;;">Go back to previous page.</a> Just replace "yoursitehere.com" with your own site page ...


3

I create my own "Category" column and set the type to "choice". Specify my choices, and all set! You can then leverage that to build a "Table of Contents" grouped by Category (as long as pages can only be part of 1 category). There's a great HowTo here: Link One step further (if you want to allow others to be able to add more categories without giving them ...


3

When getting "An unexpected error has occurred" you should check the ULS logs in SharePoint. The error page will (in SharePoint 2010) contain a correlation id (a guid) which is unique for the particular request and error. This correlation id is also used in the ULS logs. You can find the ULS logs in the {SharePoint Root}\LOGS. Search for the correlation id ...


3

Not with wikis (haven't tried) but I did get it to work with a Blog site. Just a matter of putting the javascript packages into a document library and referencing them within a content editor web part. Had to edit the HTML for a blog post that had code in, right enough.


3

MOSS 2007 provides a WIKI template for collab portals. You can also use a WIKI page library to store your pages. If you want to enhance the usability check this site. Try this resource http://www.bitsofsharepoint.com/Site/Wiki.aspx


3

This error occurs if you still have a list instance based on the list template which is obviously uninstalled together with this Wiki you mentioned. So deleting the list instance before removing the wiki solution should solve the problem.


3

If you have SharePoint Designer installed, you should be able to use it to create a custom page layout with more WebPart zones. When I did it, I believe I used this site: http://www.mssharepointtips.com/tip.asp?id=940&page=2. The site shows a MOSS2007 site, but I believe it worked for 2010 as well.


3

I think you're asking the wrong question, or at least, you need to be able to answer "Why?" or "What's Confluence not giving your users?" before you start planning how to convince them. Is the technology better? Will faries give you 3 wishes if you move to SharePoint? Do organisations running SharePoint have better Feng Shui? Calendars, announcements, etc. ...


3

If you have a bunch of users that are super-geeky Wiki-markup power users, there is nothing in SharePoint your are going to give them that will make them happy. OTOH, if you have people (in my experience there are lots more of these) using Confluence as a basic knowledge management tool, you could probably point to things like a more friendly editor in ...


3

It is possible to create a custom layout for wiki pages in MOSS 2007, however there is a major drawback: pages created using the layout will be unghosted, which can lead to major performance problems. We encountered this problem on a project a couple of years ago, and one of my coworkers describes the issue here. You are basically stuck between ...


3

Here you have a list of what is included and what is not included when saving site as template: Save a SharePoint site as a template NOT INCLUDED IN USER SOLUTION WSP Publishing pages and publishing sites And Enterprise Wiki is publishing template: Sites and site collections overview Template Enterprise Wiki Purpose ...


3

This might be something to look into (note: I have no experience with the product). Bamboo Wiki Publisher http://store.bamboosolutions.com/pfi-159-wiki-publisher.aspx


3

I found a working example at 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.


3

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


3

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 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 (unghosted). If you simply want to remove the ...


2

You can create sub-sites for your publishing portal that are not publishing sites using the stsadm command: stsadm.exe -o createweb -url http://path-to-publishing-site/subsite-name -sitetemplate -title For more information, see here: http://sharepointhillbilly.com/archive/2009/07/09/creating-a-sub-site-of-a-publishing-site-that-is-not.aspx.



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