Moving forward, bug reports and enhancements will be reported and tracked at the SourceForge project site. You should use the SourceForgeTrackers.

This website's content

• SiteWorkItemSourceCodeInSeparateNamespace -- This doesn't belong at SourceForge tracker, however deleting it didn't seem appropriate at the moment [CalvinHertel 2004-10-11].

Suggestions waiting to be turned into separate topics

• TitleOnlySearch - try finding WikiTalk pages related to String functionality - certainly can't use the search term "string"
• WikiFeatureRequest: LinkedFederations -- DavidOrnstein
• It is not clear what the request is here, please elaborate. -- StuartCelarier
• WikiFeatureRequest: Display page title with spaces between the words
• This appears to be the case. Has the request been fulfilled? -- StuartCelarier, 1 June 2004
• This does not appear to be the case to me. I see SuggestedEnhancements as the page title (not the heading on the page itself. Looking inside the <title> HTML tag. -- 28 Sept. 2004
• Improvements to TopicName handling
• It would be useful to know if a plural for refers to the same topic or not as the singular form. For example, to quickly let people know that FlexWikis isn't going to tell them about all of the FlexWikis around here, it could like this FlexWiki s (without the space).
• It would be great if TopicNames accept letters as definided in not-English languages (áéíóúñ) -- EdgarSanchez
• cookie-based entryfield on edit page for who made the change?
• PluralsAndSynonyms.
• Change the template page layout to use something other than a Div -- when using browser history to back up through pages, the returned-to page is always back at the top, rather than scrolled down to where it was when we left it. I didn't see NoScrollbarRule in WikiLore to indicate that content under a TopicName should be kept to a single screenful.
• InterWiki macros
• WikiDefectNewlineInConstantCompilerError
• Include core FlexWiki pages, perhaps a small FlexWiki ContentBase, in the install package. These pages should be things that all wikis will have: FormattingRules, OneMinuteWiki, VisitorWelcome, etc. -- JohnMorales
• Allow hierarchical page names relative to its parents. So if I'm on the home page and I enter #FooBar (notation up for discussion), then that actually gets saved as Home.FooBar even though the link displays FooBar. I thought of this while using OneNote and thought this would make round-tripping between FlexWiki and OneNote possible if and when they open up the OneNote file format or expose an XML API. -- DavidCornelson
• Add support for Code Highlighting using something such as http://weblogs.asp.net/tjohansen/archive/2004/03/11/87867.aspx
• When a page is renamed, the resulting displayed page contains no links to take you anywhere in the wiki. There are no side panels, etc., either. At least the list of updated pages should be treated as wiki links so you can navigate out of there. As it is, you have to hit Back in the browser twice to get to someplace useful. -- StuartCelarier
• See FlexWikiV2RenamePageUpdate and 1057397.
• Dates on the RSS feed are about seven hours behind. I'm posting this at 5pm and it'll show up as 10am.
• It would be nice for the RSS feeds and newsletters to have the content (diffs?) in them
• Want users to be able to set their preferences (especially, their prefered home namespace); this is the final step in eliminating the reason to actually run the software just to have your own wiki
• Should be able to move a page (to a different namespace)
• Should namespaces have a visual identity (icon, colors, etc.)?
• All topics list (want to be able to see all topics) -- should include descriptions and keywords - and other properties? Would be nice to have this unified for search, all topics and recent changes.
• map windows user aliases to wiki full-names
• WikiClassPages -- Support for documenting classes.
• Some of these "macros" would be nice: http://fox.wikis.com/wc.dll?Wiki~WikiMacros. I particularly like the fading New tag. -- GearyEppley
• Get all request throught ASP.NET ISAPI and rewrite urls so that http://wikiserver/topic/subtopic/page is equivalent to http://wikiserver/default.aspx/topic.subtopic.page -- JoseAS
• Another fun "feature" of using Div here is that the width of the content pane varies based on the type of markup in the content. Makes it fun to watch the kinetic contrast of the white content pane adjacent to the black menu bar.
• Move image, icon, emoticon files to subdirectory? -- DavidCornelson
• Export selected topics to a Word document. I picture an embedded WinForm control that allows you to drag/drop sort and indent all of the wiki topics (or selected ones) and then export to a Word Document. This could possibly turn into a collaboration with SharePoint Portal Server. -- DavidCornelson
• Shouldn't spaces work for lists? I noticed you have to use tabs in here. -- DavidCornelson
• It would be nice to have some auto-generated pages that would show log-file stats, especially redirects. It would also be nice to be able to show them at the bottom of a page.-- MikeSchinkel [2004-07-19]
• When using the Page Viewer Web Part in SharePoint to host a FlexWiki page, only the bar on the right with the buttons shows up -- the content from the page is missing.
• Database backend instead of file store -- JasonDossett
• Version Control System backend (for example Subversion) -- TanelHiir
• It would be nice to have a IWikiData interface that would be supported by both a file store backend and a database backend and make it configurable via the config file. -- BryantLikes
• Integration with SharePoint (This might be another project altogether. Maybe the suggestion is to refactor out the wiki 'engine' as something redistributable.) -- JasonDossett (in discussion with MattWright about this)
• Web services and\or automation API to programmatically modify the Wiki -- JasonDossett
• Not allow _ContentBaseDefinition files to show up in search. -- JohnMorales
• Fix links with popup descriptions that are on the right hand side of the page to show up to the left of the mouse cursor and show up on screen, rather than force a scroll to the right. -- RonRichardson
• Package FlexWiki functionality as a DotNetNuke module. -- JimBolla
• +1 -- EdgarSanchez
• +1 -- KhurramAziz
• List wiki pages that reference the current page in the sidebar. (can either catch these in http referrer, or update list each time other pages are updated) -- Lewis Moten
• For ExternalWikis, display something instead of just blank, which looks as if there aren't any yet. See StopWords at OpenWiki, where any word on the page is excempt from being a WikiLink anywhere else in the -- MarkCidade
• Add panel to list all wikis if administrator added additional folders for them, along with the description of each one. --Lewis Moten
• Allowing customisation of the interface e.g. in an intranet environment, the entire "Logoff" box is not needed. -- ThomasWilliams
• This could be done by adding a key in the config file, and then testing for the key value in the DoPage() method of "SafeMode.aspx.cs" where the check for "User.Identity.IsAuthenticated" is carried out. Limited customisation can also be done by removing the <About> item in the file "NamespaceMap.xml". -- ThomasWilliams
• To have some sort of adding security features about who can edit and save on topic. Otherwise a lot of garbage will appear. If a user create a topic, even if there are a lot of history to the topic, the user will be able to administer what eventually will appear on that topic deleting all unnecessary changes, sort of acting as an editor.-gigi

• Auto complete on the header so as you start to type it would list your pages and narrow them down as you type

Making Changes Yourself

Note that the best way to ensure that this stuff happens is to be part of DevelopingFlexWiki.

Closed issues

• WikiFeatureRequestAccessToPropertyValues