74
Vote

CKS: Enhanced Wiki Edition

description

Update: CKS:EWE 2.0 Beta 2 has been released!
https://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=CKS&ReleaseId=8087
 
Proposed features:
  • 2-3 custom page templates (e.g. FAQ, Employee Handbook)
  • Support for custom wiki markup syntax/tokens such as " bullet", "-strikethrough-, etc.
  • Page specific section titles/bookmarks and autogenerated TOC
  • Web part that shows orphaned pages (i.e. those without any inbound links)
  • Web part that shows blank pages ranked by highest number inbound links
  • Web part that shows the pages ranked by hits/popularity
  • Support for public discussions on each wiki page [already in Alpha]
  • Support for private (admin only) discussions on each wiki page [TENTATIVE]
  • Sectional editing [TENTATIVE]
  • Physical page relationships (e.g. page tree, subpages) [TENTATIVE]
  • Tool for importing content from other wikis and applications

file attachments

comments

yaoge wrote Apr 25, 2007 at 9:44 PM

Auto generated TOC and sectional editting will be very helpful. Physical page relationship (page tree) can also be helpful for providing alternative views to the pages in the wiki space.

wrote Apr 26, 2007 at 10:29 AM

jofran wrote Apr 26, 2007 at 10:33 AM

It would be great if folders for the wiki-list could be enabled. That way, you can set specific rights and notifications for an entire namespace (folder). The auto generated TOC could be derived from the folder-structure.

wrote May 1, 2007 at 5:57 PM

wrote May 1, 2007 at 5:57 PM

wrote May 2, 2007 at 1:51 AM

lawrenceliu wrote May 9, 2007 at 4:14 PM

Autogenerated TOC is in scope. Sectional editing will be tougher but we might be able to implement a template that has two editing areas on the page. The top would be "authoritative" (access limited to a small group) while the bottom would be "community" (open to any authenticated user) -- this would work similarly to how the MSDNwiki (http://msdn2.microsoft.com/en-us/library/ms550992.aspx) works today.

wrote May 12, 2007 at 8:45 AM

wrote May 16, 2007 at 4:37 PM

wrote May 18, 2007 at 4:42 PM

wrote May 28, 2007 at 12:16 PM

stevex wrote May 28, 2007 at 12:17 PM

I'd really like to see the ability to attach a file to a wiki page - mainly images, but any file would be useful. Having files over in a separate document library is awkward.

wrote May 31, 2007 at 5:41 AM

wrote Jun 1, 2007 at 4:24 PM

jxh11215 wrote Jun 1, 2007 at 4:24 PM

I am in accord with the vote for file attachments in wikis

wrote Jun 2, 2007 at 6:13 AM

wrote Jun 6, 2007 at 1:16 PM

wrote Jun 14, 2007 at 6:41 AM

yangxiao wrote Jun 14, 2007 at 6:44 AM

Public dicussions on each wiki page will be very helpful. It's better to make it look like the comments feature of blog.

lawrenceliu wrote Jun 18, 2007 at 7:37 PM

wrote Jun 19, 2007 at 3:44 PM

wrote Jun 19, 2007 at 7:21 PM

wrote Jun 19, 2007 at 8:50 PM

jedgerton wrote Jun 19, 2007 at 11:35 PM

Add a "Printer Friendly" option for each posting.

wrote Jun 21, 2007 at 12:48 PM

wrote Jun 22, 2007 at 8:02 PM

wrote Jun 22, 2007 at 8:51 PM

wrote Jun 25, 2007 at 6:38 PM

wrote Jun 26, 2007 at 2:38 PM

wrote Jun 28, 2007 at 4:27 PM

wrote Jun 29, 2007 at 6:17 AM

greggerca wrote Jun 29, 2007 at 6:09 PM

Importing and Exporting are really important to me as well, but also I have had requests from people that either want to take the wiki with them electronically (PDF or Word) or print it all in one go... If you had a TOC, I guess you could print it in that order. Printing a wiki is a funny concept to me since it's a networked document that has a somewhat arbitrary order.

I would also love to be able to edit wiki pages in something like OneNote and post directly to the wiki. This is how I keep a "backup" copy with me so that I can write stuff on planes. What I found, after someone accidentally nuked my wiki server (which IT "forgot" to back up), was that the OneNote archive I had been keeping was invaluable. While trying to restore it, I found that trying to port content from another wiki into it was not easy either, so copying and pasting was the only way to go in either OneNote or the other wiki.

It would also be nice to be able to point to other MOSS resources from a wiki page easily. If I wanted to link to a blog entry, picture, another wiki, etc. it would be nice to be able to browse and build a link to the resource in question.

For wiki page linking, when you have a huge amount of pages available, it would be good to have a skinny Web part that lists the titles of the pages available while you're editing. Or, maybe it should just be a "WikiSuggest" step in the page publication. Sort of like a preview before publishing. The "preview" step would look for word combinations in your wiki page and suggest links to existing pages already in your library. You should be able to confirm / remove / edit (i.e. point to different wiki page) / test them, re-preview, and then publish.

Thanks,TTFN

greggerca wrote Jun 29, 2007 at 6:10 PM

Importing and Exporting are really important to me as well, but also I have had requests from people that either want to take the wiki with them electronically (PDF or Word) or print it all in one go... If you had a TOC, I guess you could print it in that order. Printing a wiki is a funny concept to me since it's a networked document that has a somewhat arbitrary order.

I would also love to be able to edit wiki pages in something like OneNote and post directly to the wiki. This is how I keep a "backup" copy with me so that I can write stuff on planes. What I found, after someone accidentally nuked my wiki server (which IT "forgot" to back up), was that the OneNote archive I had been keeping was invaluable. While trying to restore it, I found that trying to port content from another wiki into it was not easy either, so copying and pasting was the only way to go in either OneNote or the other wiki.

It would also be nice to be able to point to other MOSS resources from a wiki page easily. If I wanted to link to a blog entry, picture, another wiki, etc. it would be nice to be able to browse and build a link to the resource in question.

For wiki page linking, when you have a huge amount of pages available, it would be good to have a skinny Web part that lists the titles of the pages available while you're editing. Or, maybe it should just be a "WikiSuggest" step in the page publication. Sort of like a preview before publishing. The "preview" step would look for word combinations in your wiki page and suggest links to existing pages already in your library. You should be able to confirm / remove / edit (i.e. point to different wiki page) / test them, re-preview, and then publish.

Thanks,TTFN

greggerca wrote Jun 29, 2007 at 6:11 PM

Sorry for the double post. A parsing error dialog popped up and I thought the submit failed. :( Please delete one of them if you can.

TTFN

wrote Jul 3, 2007 at 11:02 PM

spowser wrote Jul 3, 2007 at 11:13 PM

I would like to throw my vote in for sectional editing and being able to maintain a library of page templates.

I would also like to bring up the current set of editing controls for tables in the MOSS Wiki page editor. I would love the ability to highlight the table and change it's attributes on the fly. For example, changing row/column/table shading, borders, width, height, padding, spacing, etc without having to open up the source. Also, how about a side by side view of the page source and viewable page with the source formated with color coding. I hate having to edit, close, check, go edit again, close check, etc. And if that is implemented, might as well be able to click on the source and highlight the area being edited in the viewable page. I know, I want alot!

wrote Jul 5, 2007 at 5:29 PM

GerhardB wrote Jul 5, 2007 at 5:29 PM

An enhanced WIKI would the greatest thing for MOSS 2007...

wrote Jul 5, 2007 at 6:14 PM

micatcsiro wrote Jul 6, 2007 at 8:30 AM

I would love a quick and easy way to add images sourced locally. At the moment it seems that all you can do is add images which already exist on the internet by specifying their url. To get around this I upload all my images into an Image Library in my Sharepoint Wiki and then copy and paste in the url for each one. Obviously, this is very tedious. I'd prefer to simply click on an icon to insert an image, browser my hard drive, select the image, and click insert. In the background Sharepoint would upload the image (attach it to the wiki page I suppose) and it would appear. If someone knows a way of doing this I'd love to hear it.

spowser wrote Jul 6, 2007 at 7:40 PM

Edit to my post below: I found a control that does exactly what I want in regards to the Editor for MOSS. You can use the control from Telerik that replaces the default editor in MOSS. You can get more details here http://www.telerik.com/products/sharepoint/editor-for-asp.net.aspx

The Telerik editor solves alot of issues with the default editor

wrote Jul 9, 2007 at 10:19 AM

jguiver wrote Jul 9, 2007 at 10:33 AM

I would like to see:(a) Richer editing - in particular the wiki supporting our project has a very heavy equation content. The best way that I can see to include large numbers of equations is to embed a word doc - saved in mht format - as a Page Viewer Web Part, and provide a link to the doc library in which the source page resides.(b) Ability to select from a list of templates for a new wiki page - this has general utility, but, in the short-term, would help to support the type of stop-gap Web Part solution outlined in (a)

wrote Jul 12, 2007 at 8:32 PM

wrote Jul 13, 2007 at 9:55 PM

wrote Jul 14, 2007 at 2:40 PM

DReuther wrote Jul 14, 2007 at 2:46 PM

Easy upload and sizing of images, support of Windows and MAC browsers and 'printer friendly' view for printing would be great.

dominigan wrote Jul 18, 2007 at 12:31 PM

I'd like to see a wiki template with integrated document library. On library with items filtered by current wiki page. Uploads would be added with the current wiki as filtered items. I'm trying to create a knowledgebase that uses captures both wiki text and associated research documents for that wiki topic.

wrote Jul 20, 2007 at 11:19 AM

kilty wrote Jul 20, 2007 at 11:23 AM

templates; TOC; access to other sharepoint sites since navigation is a nightmare, even using tree-view - which is slow, & inconclusive

wrote Jul 20, 2007 at 5:15 PM

Roundand wrote Jul 20, 2007 at 5:28 PM

I'm using the Sharepoint Wiki to create some internal technical documentation, and I'd really like to be able to format my documents at a higher level than just Font - for instance, if I can't have wikitext for CODE I'd certainly like to be able to create and use a Style, with say a monospace font, single-hight line spacing and some kind of highlighted colouring.

wrote Jul 27, 2007 at 8:26 PM

GandalfThePlaid wrote Jul 27, 2007 at 8:53 PM

Attaching any files not just images would be a huge plus. An example would be when placing a diagram in a wiki page that was created by Visio. Yes having the image attached locally to the page keep things tidy and would be wonderful to have, but being able to attach the source Visio document to allow for further editing is handy as well. Time to update the image? Just grab the Visio from the attachments list, generate the new image and update the image attachment. Update was wrong? If the attachments can be versioned just revert the attachments to a previous revision.

jgundy wrote Jul 31, 2007 at 9:11 PM

In addition to the list above, I think these features would be greatly useful:
  • Improved conflict resolution : currently if two users are editing the same page at the same time, the one who submits last has to merge basically from scratch. Some simple tooling, like having both the old and the new page up at the same time could make that easier. Redirect Tag : Often topics go under multiple names. Redirecting to a single page would be better than the hack of having a simple page with just the link. Preview button : Although the wiki is WYSIWIG, you don't know if your links work until you submit the page. It would be nice to have a button that would either render the page or tell you which wiki links point to real pages or not.

wrote Aug 17, 2007 at 4:15 PM

dhollas wrote Aug 18, 2007 at 7:31 PM

We would like to see these features attached to the wiki discussion board -Support for custom wiki markup syntax and/or tokens to create new wiki page [[New Wiki Page]] - Link to a ListItem of Wiki Pages

wrote Aug 21, 2007 at 8:40 PM

wrote Aug 22, 2007 at 11:09 PM

karlo wrote Aug 22, 2007 at 11:16 PM

Please solve the "rich text editor" issue considering also "level 2" browsers as valid contributor to corporate wiki: in my extranet lives also linux, solaris, aix, macosx.... no more ActiveX for Web 2.0 tools!

wrote Aug 23, 2007 at 12:58 AM

MiramarMike wrote Aug 23, 2007 at 1:00 AM

AJAX based would make me and all "my" users sooo happy!All the rest is icing on the cake and we want it!

wrote Aug 23, 2007 at 8:14 PM

nickmiller wrote Aug 23, 2007 at 8:20 PM

Really need section titles, editable sections very nice to have. Regarding the custom page templates....FAQs would be good, also some type of glossary tool (ie. list the <used> alphabet across the top, click on character to jump down to that part of the page.)

wrote Aug 31, 2007 at 3:25 PM

Jrd4444 wrote Aug 31, 2007 at 3:27 PM

Want to see text wrapping for images on the wiki page to allow more creative use of "real estate" and giving users a more easy way of using images on their pages.

wrote Sep 24, 2007 at 12:18 AM

wrote Sep 25, 2007 at 3:28 PM

wrote Sep 26, 2007 at 6:28 PM

kmomorella wrote Sep 26, 2007 at 6:56 PM

Enable wiki for collaborate document development: We are using wiki pages to assign and develop sections of business plans that need to be developed cross-functionally. We need a way to be able to format and paginate the set of pages so that they are readblle as a document would be. We have been looking for ways to move each page into Word and then format it but this is n ot ideal. We are usuing Office 2003. Since the final business plan can be up to 30+ pages long, it is not practical to have all content going into one page. Also, the wiki allows us to secure each section (page) so that only assigned users can change content. Idealy, we would create a template for each section of the business plan that would ensure consistency in formatting between sections and then have a way of consolidating the sections (pages) and adding page numbers and a TOC. We are an east coast world renowned university and hospital and would be happy to be an early tester of the enhanced wiki.

wrote Oct 10, 2007 at 3:56 PM

Dagaric wrote Oct 11, 2007 at 5:05 AM

Where can I find some live demo of this EnchWiki?

wrote Oct 11, 2007 at 4:56 PM

wrote Oct 17, 2007 at 4:05 PM

wrote Oct 19, 2007 at 6:59 PM

wrote Oct 24, 2007 at 9:26 AM

wrote Oct 25, 2007 at 6:10 PM

wrote Oct 31, 2007 at 3:15 PM

wrote Nov 2, 2007 at 12:16 AM

dmann wrote Nov 2, 2007 at 2:23 PM

Beta 2 of EWE has been released and there is a public demo site available:
URL: http://ewe.wssblogs.com/beta2wiki/WikiDemo/Page1.aspx
User: ewe_user
PW: password

-Dave

wrote Nov 19, 2007 at 1:21 PM

jowa wrote Nov 19, 2007 at 3:34 PM

Problems with non-standard-installation:
The files "CreateEWEPage.aspx.cs" and "CreateWebPage.aspx.cs" are containing static filepaths ("System.IO.StreamReader oStreamReader = new System.IO.StreamReader("C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\DocumentTemplates\CKSEWEstd.aspx");
"). In my german enviroment it's called "C:\Programme\Gemeinsame Dateien\Microsoft Shared...". Probably this is the reason why i can't save new Wiki-articles.
Besides EWE looks realy promesing :-) I'm looking forward to what's coming up next.

wrote Dec 5, 2007 at 10:35 PM

wrote Dec 12, 2007 at 9:39 PM

wrote Dec 21, 2007 at 9:52 AM

wrote Jan 3, 2008 at 8:02 PM

wrote Jan 10, 2008 at 3:32 PM

jowa wrote Jan 17, 2008 at 4:39 PM

fixed my problem by using

System.Environment.GetEnvironmentVariable("CommonProgramFiles") + "\Microsoft Shared\web server extensions\12\TEMPLATE\DocumentTemplates\CKSEWE.aspx"

as path

wrote Jan 22, 2008 at 9:32 PM

wrote Jan 28, 2008 at 8:02 PM

et63787 wrote Jan 29, 2008 at 5:19 PM

I would lilke to see an Intelligent Navigation Breadcrumb webpart. As one followed a particular line of logic through a blog, a web part, in my case found in the Left Margin QuickLaunch area, would adapt and adjust revealing the network inbound and outbound links as each page visit occured. A person could then back up by clicking in the navigation.

wrote Jan 29, 2008 at 5:20 PM

wrote Feb 3, 2008 at 6:51 PM

wrote Feb 3, 2008 at 6:52 PM

wrote Feb 3, 2008 at 6:54 PM

wrote Feb 3, 2008 at 6:55 PM

wrote Feb 3, 2008 at 6:57 PM

wrote Feb 3, 2008 at 6:57 PM

wrote Feb 8, 2008 at 8:16 PM

vshamanovsky wrote Feb 8, 2008 at 8:17 PM

Any idea when Enhanced Wiki Edition may RTM? Ballpark date? Half a year a year ?
Thanks! Can't wait.

wrote Feb 11, 2008 at 11:02 AM

wrote Feb 11, 2008 at 7:46 PM

spiderwebwoman wrote Feb 11, 2008 at 11:14 PM

I'm getting a 404 Not Found for the demo at http://ewe.wssblogs.com/beta2wiki/WikiDemo/Page1.aspx Has it been moved?

Kathleen

wrote Feb 17, 2008 at 5:59 PM

resing wrote Feb 25, 2008 at 1:41 PM

I received an error, #20015: Cannot open "CKSWikiCore.en-US.resx": no such file or folder, after installing this EWE Beta 2 on a Development server. Around the same time, a user received an "Unexpected" error in the browser accessing a site without this feature enabled. May be a coincidence, but I was wondering if anyone experienced something similar.

wrote Mar 13, 2008 at 10:34 AM

DReuther wrote Mar 13, 2008 at 8:43 PM

An improved breadcrumb for the wiki would be extremely helpful. Based on the flat storage structure of wiki pages the breadcrumb does not add vlaue to the user. All you get is wikipages : current page, even if the current page is way down in the structure of the wiki. We actually manually create a breadcrumb at the top of each page to help users navigate better.

cjlotz wrote Mar 20, 2008 at 8:39 AM

Printer friendly version of wiki pages will be very helpful.

wrote Mar 20, 2008 at 6:03 PM

wrote Mar 21, 2008 at 9:51 AM

timpaul wrote Mar 21, 2008 at 9:53 AM

Tried accessing the demo site using ewe_user password but recieved an "access denied"

wrote Apr 1, 2008 at 7:28 PM

wrote Apr 3, 2008 at 9:19 AM

wrote Apr 4, 2008 at 8:30 AM

Nils wrote Apr 4, 2008 at 9:53 AM

Hello!
I have been experimenting with a wiki in WSS 3.0 for a year now, A usergroup is edititing aprox. 100 wiki-pages creating a book in swedish about safer workingenviroment.
Later the usergroup, which is comprised of people teaching workingenviroment practises, will choose wikipages and print them making various learning materials for different groups with different needs.
The wikipages are numbered and displayed in a view where the column Wiki-content is activated. You can read the book scrolling down or print the whole thing.
The following functions would improve the usability:
  • send a copy of a wikipage to another library .
  • sort the chosen wikipages in the other library by drag and drop or by changing pagenumbers the same way you can sort columns when creating views,
  • a function that calculates pagebreaks when printing (later as a pdf- or word-document)
  • a function that converts wikilinks to a textstring in the margin ("Read more") and a pagenumber (links to wikipages in the same library converted to pagenumbers, but links to wikipages that are not chosen for printing must be converted to an url).
  • a function that makes a list of the chosen wikipages (a table of contents),
  • a function that makes an alphabetical index of the wikilinks on the choosen pages.
  • a function that converts the imagelinks in the wiki to links to a library with highresolution copys of the same illustrations,
  • a function that creates a pdf- or word.dokument of the chosen wikipages.
I hope my english is better than my knowledge about what is possible in Sharepoint :-), but what's wrong with visions?

There is also an annoying thing in the existing Sharepoint wiki. When two users edit the same document at the same time, one of them will see an errorpage when saving. The instructions on that errorpage will cause the user to loose the text he or she was writing. Please change the text on the errorpage so that the user will not use the link that says something like "go back to the site". The page must instruct the user to press Alt+ Left arrow, press Alt+C on the inserted text and reopen the wikipage for editing.

Nils Östergren
Stockholm, Sweden

woodyola wrote Apr 8, 2008 at 9:27 AM

hi, ive recently installed the CKS:EWE 2.0 Beta 2 and can now enable discussions on the wiki pages but i just cant see the source code toggle! any suggestions?, have tried reinstalls and no errors...also following the steps on the release nots proved tricky as the CKS library option just doesnt exist for me - again any suggestions welcome. cheers

Tarentula wrote Apr 15, 2008 at 2:02 PM

Do you mean that you don't see the CKS:Enhanced Wiki Page Library? I can only see it on the root site of the first site collection, and it's a little frustrating. However if I cut and paste the link to a subweb, it works there as well.

Tarentula wrote Apr 16, 2008 at 6:22 AM

Nevermind my last comment. All I had to do was to enable another feature, besides Wiki Discussion Lists, and that was CKS:EWE Page Library. The strange thing is that it does not have to be enabled in the first site collections root site. But now it's working great!

woodyola wrote Apr 16, 2008 at 11:41 AM

Hi Tarentula, I just dont get that option anywhere that i can see - i know sharepoint isnt obvious sometimes but this i just cant find. When you refer to 'next' to wiki discussions do you mean in the list? I dont have anything extra apart from wiki discussions in there now after the EWE has been installed - am i missing something??

wrote Apr 19, 2008 at 5:14 AM

Tarentula wrote Apr 24, 2008 at 5:25 AM

Hi again, sorry for the late reply. When I troubleshooted this issue I tried out a lot of different things and now I have realised that in order to see the other link (CKS:EWE Page Library) I changed a bit in the "...\12\TEMPLATE\FEATURES\CKSEWELibrary\Feature.xml" file. I changed the attribute Scope from "Site" to "Web" and the attribute Hidden from TRUE to FALSE. Then I probably did an iisreset. There is probably a better way of doing this so if anybody knows about it, please let me know.

wrote Apr 28, 2008 at 5:20 PM

HowardBl wrote May 17, 2008 at 10:44 AM

File attachments in wikis would be great. Is this going to be added at some point?

wrote May 23, 2008 at 3:33 PM

wrote Jun 28, 2008 at 11:54 AM

wrote Jun 30, 2008 at 8:31 AM

Knoerchen wrote Aug 15, 2008 at 12:14 PM

Many thanks to all of you worked to offer the EWE, I implemented it successfully to SharePoint 2007 (WSS3).
One thing can I get the same behaviour like the "old" Wiki Library behaves - like not showing up the file list instead of it showing up the home.apsx file?

jowa wrote Sep 19, 2008 at 10:56 AM

Hi Knoerchen, if you create an article called "default" this will be taken as homepage. But still you will be taken to the listview after editing an article. If you prefere to be redirected to the "default"-Homepage (or any other wiki-page) after editing an article, you can create a new default-View, only showing "Wiki-Content" of the article selected by its name. Afterwords you still get a listview - but just showing the content of one article.

wrote Sep 19, 2008 at 12:19 PM

gildresh wrote Oct 30, 2008 at 3:28 PM

Any news on this project?
Nearing completion?
Dead in it's tracks?
Anything as to a full release?

wrote Nov 28, 2008 at 12:56 AM

Knoerchen wrote Nov 28, 2008 at 9:58 AM

Hi can we still expect a new version coming out or has this project died?

BTW: Thank you for the tipp naming the page default jowa it works as designed :-)

wrote Nov 28, 2008 at 10:00 AM

nightsafari wrote Dec 1, 2008 at 7:03 AM

Hi Dave, I am quit exited with your works. You have done really good job, I guess you are being prepared with all new proposed features; it just guess :) I am working on mediawiki to CKS wiki migration for some time and I was surprised with all available features with CKS wiki. We all will really be more powerful if you announce your proposed features in final version. Number of guys in my contact are very inspired with your job done on CKS wiki beta 2, a human nature they use but which talking mediawiki vs. CKS wiki. We all are just seeking few proposed features like multiple template, section editing, preloaded text. Friend it would be really great if you think for eary launching of this features before making final; Just request :)

nightsafari wrote Dec 1, 2008 at 7:17 AM

By the way what is planned release date for indicated fatures.
Any answer please ?

Knoerchen wrote Jan 5, 2009 at 12:35 PM

Hi, is there any progress to get a new version? Hope the CKS: Enhanced Wiki Edition is still under development?! Please keep on your good work on it.

wrote Jan 12, 2009 at 9:10 AM

JReed wrote Jan 19, 2009 at 8:34 AM

I'm not seeing the "Toggle Markup List" link in the RTE. Is this available with the most recent update or is this yet to come?

wrote Jan 22, 2009 at 5:31 PM

wrote Feb 23, 2009 at 3:52 PM

Knoerchen wrote Jun 26, 2009 at 6:55 AM

Hi,

is here any progress on the CKS_EWE? Or is this project dead? When will the next release? As far to now I do not encounter any problems with BETA 2...

Thx and Cheers

Joerg

slfackler wrote Aug 17, 2009 at 6:15 PM

Is there a new version of this or is it still in works? Sounds great.

shiz wrote Aug 26, 2009 at 9:35 PM

is there a way to indicate on a wiki page whether there is existing discussion on the article? People who are interested in discussion don't want to click on discussion and find nothing.

joyceodom wrote May 26, 2010 at 12:07 AM

Is anyone still working on this project? I can really use these enhancements - please keep it coming.
I really need auto generated TOC, sectional editing or wiki page templates, and the ability to export/print multiple pages.

wrote Dec 7, 2010 at 11:34 AM

Anbarasu wrote Dec 7, 2010 at 11:34 AM

I have installed Enhanced Wiki Edition 2.0 Beta 2 in my SharePoint farm. There is an error when the discussion link is click on the Discussion in the breadcrumb. Attached is the error message.

This is only an issue wtih enhanced wiki. Is there a fix to this error/bug?

Anbarasu wrote Dec 23, 2010 at 10:24 AM

We are facing breadcrumb error with Enhanced Wiki Edition 2.0 Beta 2. When click on Wiki discussions list in breadcrumb, it results in error.

Can some one help us here?

Anbarasu wrote Dec 28, 2010 at 4:53 AM

Is some one out there to help us?

Anbarasu wrote Jan 20, 2011 at 8:36 AM

Is there any release in near future?

wrote Feb 22, 2013 at 12:02 AM