Suggestion Box

• Categories
• (Technorati) tags & related
• Internationalization/Localisation
• Date/Time
• Wikka Exporting/Importing, PDF-Export
• Optimization
• Table of contents (TOC)
• Section Editing
• Spam (and related issues)
• Tables
• TemplateSystem
• Workarounds for uncommon problems

• UserMap

Language support

Highlight text searched in a page

Wikka markup inside tables

Is There a way to consolidate a bunch of page updates (the actual content that is) onto one page?

Static HTML for offline browsing

Link en- and disabling in respect to user rights

Edit comments displayed by user rights

Please provide a way to add formatters, that don't get placed in '<div class = "code">'

Note on edit, mandatory field

Question: note?

Order of comments

Own comments editing

versioning of attachments

Making PageIndex go faster

Single-click restore of previous versions

Signature

Preview

Generate ID in forms; allow class

Accesskeys for the footer functions

Exclude certain CamelCase words from formatting

Import WikiPedia database

Color Formatting

Separation of Wakka class from wikka.php

Save Pages to PDF Format

showing comments

Local links

RSS options

wikiwyg

Google Sitemap

Clearing ACLs

Online editing of mindmaps would be great

%% in code blocks: a possible workaround

How to format code to get two % characters without space together?

Robot Friendly Pages

Sending 403 headers

The access-key for "re-edit

LinkTails

Search within the textbox

Numbers as page names?

Improved code for error messages in Action() method

Language files

mod_rewrite idea (.htaccess)

Create rewrite rules on install

Suggestions to be checked/migrated to the tracker

making user uploaded images more useful

Automatic conversion from HTML to WakkiWiki syntax

• Try out http://diberri.dyndns.org/html2wiki.html∞ (Won't work with tables yet). --NilsLindenberg

Files Management

Automatic summary

Improving Wikka

Login using retrieved password

• Charlotte, you are correct in that the code doesn't work as is. We are working on splitting up the whole (confusing) login/usersettings form into separate actions and forms; logging in with a "temporary" password should then not only be separate, but also force the user to immediately choose a new password since sending a password by email is inherently insecure. Until we have that in place in a future release, your workaround is a good one (I came up with the same ;-)); but it's up to you to decide how acceptable it is in your application to let the user continue to login with an emailed password. --JavaWoman

Hiding anonymous host/IP from non-administrators

Storing the IP-address for registered users

• Last known IP or every IP they ever connect from? I'd be willing to store one last known IP per user. - JsnX
  • Last known IP please :) Thanks. - Sam
• I'd suggest adding *two* distinct fields to wikka_users: Last Login IP/Hostname + Last Login Time - DarTar
  • I was also thinking of a way to ban users directly from the wiki (much in the same way as referrers are added to the blacklist of spammers). This might turn out easier to implement than a user deleting action (which was one of the ideas discussed here) - DarTar

Global Access Control Lists

Integration into existing site

plus more on non-wikiname formatted usernames

• I am interested in doing something very like this as well. I would like to integrate wikka into an existing phpBB site. I don't mind if my users have to log in twice - but I really don't want them to have 2 seperate usernames/ passwords. Therefore ideally I would like the wikka to use the usertable from phpBB... Has anybody else done something like this? -- KiltanneN
  • One solution that I've used is to set up a registration page that registers the user into both the bulletin board and the wiki user tables. I've then removed the registration screens from each of the two. Users can then log into either of them using the same username and password. Of course, this only works when registering "new" users...one would have to write a script to copy existing users from the bulletin board into the wiki user tables for current users. --GmBowen
    • Not a bad idea - but breaks down for password changes and also name changes... I am going to try and build what I have described. I will make notes over here: UseThephpBBUserTable -- KiltanneN

• See also WikkaWithphpBB --JavaWoman

Pages linking to nonexisting pages

• What's the </div> for? I see no opening <div>. --JavaWoman
  • it closes the <div class="page">. --NilsLindenberg
    • But I don't see an opening <div> - and this closing </div> is within an if clause. So when/where is that div opened, and when/where does it get closed when the condition is not true? Something wrong with the logic here, or you're not showing enough of the logic. --JavaWoman
      • Ok, I was a littler bit short here :) the show handler opens a <div class="page"> before doing anything else (like the "has access"/page is existing check). So it has to be closed (and actually is closed) in every one of the three cases (1. no access to the page 2.pages is not existing 3.pages is displayed). In the official version it is closed after the "create it". I just moved it to have the backlinks inside the page-class (should have written that earlier :) --NilsLindenberg.
        • All right :) I guess the show handler is just sloppily written. If you open a div no matter what conditions apply, then you also close it no matter what, i.e., opened outside the if statement, then close it also outside the if statement. Whatever you do inside the if statement should have no influence at all: if opened, you must close it, no ifs and buts. I guess it's not wriiten like that (yet...). One for the code cleanup list. ;-) --JavaWoman

Configurable name for Wikka engine

 "wikka_engine" => "wikka.php", 

Search engine results inflation

• I think I've suggested before that the SandBox should not be indexed - the way to avoid this would be to add the appropriate meta tag to the page's head. That concept could easily be extended by allowing a WikiAdmin (not the WikiUser!) to define a list of pages where such a meta tag would be inserted. Generating a little text note to the effect for all these pages could also go some way to discourage spammers. --JavaWoman

For Better Overview

• Hope you have a large screen: SoWhatAreTheNews --ChristianBarthelemy
  • Nice one, Christian! While you're at it, you might want to add the RecentComments page (or its content) as well, so you get a better overview of all recent comments and not just pages that have recently acquired new comments. Then you have it all in one place. ;-) --JavaWoman

Generate page from an external database

DotMG insists about favicon.ico and robots.txt

• It can be done more generically by simply preventing rewiting happening when the requested URL matches an existing file or directory:
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_FILENAME} !-f
  
  The first line excludes any directory, the second any existing file (which would include robots.txt and any icon file - you do not necessarily have to use favicon.ico). --JavaWoman

Category Icons

• Karma, we are actually considering the possibility of integrating a set of GPL'ed icons (and the relevant actions/formatters) in Wikka. Stay tuned... -- DarTar
  • You're more than welcome to use our icon action and icons: WikiIcons∞ which were copyleft from here∞. The icons were auto-generated from the SVG versions at various sizes, you can take what you want. Only problem is they are PNG's -great in ANY browser but IE!!! --IanAndolina
    • IE7 does support PNG's, IE6 and IE5.5 support it with a javascript solution, look in SmiliesAction for more on IE, PNG, image actions, icons etc.
  • Some more at IconsInWikka -- ChristianBarthelemy

Automatic Table of Content Generation

• Have a look at TableofcontentsAction for some ideas about creating a TOC (automatically or triggered by an action...) --JavaWoman

Security Verification Test from Wikini

// Vérification de sécurité
if (!defined("WIKINI_VERSION"))
{
die ("accès direct interdit");
}

• This is to ensure that a hacker can't view a page directly, with url like http://wikka.jsnx.com/actions/recentchanges.php∞. If this technique is possible, he (the hacker) can send request to make your wikka site output error strings. But in wakka forks, this will result in handlers "page/recentchanges.php.php" not found, if rewriteengine is on. If else, I' ll test it and I'll tell you. The simplest workaround, if it's the case is to add a .htaccess file at ./actions, .handlers/page directories, with the content : Deny from all. --DotMG

Inherit ACL from 'parents'

• IMO the acl system has to be dumped and/or renewed/rewrittem to accomodate usergroups..
• I have been thinking of presenting a modification that will actually implement this user managment system ..
• having privileges for each page is making userprofile-specific-features on Wikka efficiently non-existant.
• The ability to create custom usergoups ( aka levels, profiles etc. ) would enable the addition such features
• ( ip/hostname display , access to special parts of the wiki and such .. ) -- GeorgePetsagourakis

Paragraph instead of line-breaks

• The above code places paragraph tags throughout the page, including within code blocks, which seems undesirable. If \n were treated as markup which wakka.php needs to transform into paragraph tags, code blocks wil not be changed, I think. I'll try it and post the code changes if it works. --PaulP
  • No, that doesn't completely work either. It leaves code blocks unchanged, but keeps text from returning to left margin after indented paragraphs. --PaulP

Usergroups

"In work" for Wikka-pages

• Multiple users see the same code and concurrently start working on changes.
• One user posts his changes.
• Another user posts his changes without realizing that the code had been updated.

• Another user has to go back through his code and incorporate the changes made by the first user.

• Comments:
• Dangerous! Consider the following scenario: user has been hard at work all week, now it's Friday afternoon and there's some time to do an edit or three. User opens each page in a browser tab, marking all three as "in use" and starts to edit them. Clickety-click. Suddenly user realises he has to run to catch the train home. Run! On the train, user realises the three pages are still open in the browser and "in use". "No matter", thinks our user, "it's always quiet during the weekend and I'll get back to it first thing Monday morning. On Sunday afternoon, user plays soccer, as he always does, and breaks a leg, which he usually doesn't do. User is transported to hospital where he has to stay for four weeks. ... A bit exceptional maybe - but what do you do with "dangling in uses" and when (how) are they considered "dangling" in the first place? --JW
  • Good point, but this modification would be only an informational resource to facilitate user communication. Techically, users could still update the page any time they wanted. It would just be a courtesy to hold back if you saw that a page was 'in use.' I didn't mention it above, but I planned to also add a field that would timestamp when the status was last changed. So in your scenario, we would see that the page had been marked as 'in use' for several days and feel free to ignore it. However, this does bring up the idea that it would be good to also have a 'note' box available for updating the page status -- used for comments such as, "should have the code updated within a few hours." Better now? -- JsnX
• I've got code/table changes done that indicate if anybody (other than oneself) opened the page to "edit" in the last 15 minutes. It's on an iteration that isn't "live" right now (it's part of an earlier installation of wikka that we just haven't brought the code forward from yet), but I can make it that way so you can test out the functionality if you want. Since much of our site will be geared towards small teams doing collaborative editing, it was designed so that editing conflicts would not occur. Let me know if you want me to get it installed at a test site. -- GmBowen
• I agree, it's an important issue (some Wakka forks have already addressed the problem of concurrent editing) -- DarTar
• JsnX: If it's purely informational, that's better; I thought the intention was some kind of locking. So you'd have something like:
  • -state: in use | available
  • -timestamp: in use since
  • -note: applies to the in use state only
• Then - would the state apply to the logical page or to a particular version? If the latter, what happens if a page is reverted to that version? What happens to the state when another user goes ahead and edits the page anyway?
• And I still think you'd need some kind of admin function to "clear" dangling in use states that are older than xx minutes/hours/days.
• GmBowen: is yours completely automatic or user-initiated? What happens in the run off to catch the train scenario? -- JavaWoman
• (i) it's purely informational, not a "lock"...it sets a red exclamation mark beside the page name at the top if the "edit" link (or double click) has been used in the last 15 minutes by anybody other than yourself (ii) it's automatic (iii) the "train scenario" can't happen. It doesn't check if "saved" or not, just whether an edit was started in the last 15 minutes. This means that if the person doing the edit hasn't saved in the last 15 minutes when editing then the exclamation mark isn't activated for another user. But, people should save edits every 15 minutes anyways methinks. It's not "foolproof", but was meant to avoid many sorts of common editing conflicts on collaborative documents. It's not a very "big" edit of the wikka code actually. The edit.php script timestamps the most recent version of the page when it is activated, and there's a small addition to header.php that checks when the page is loaded to see if the current time is < 15 minutes from that timestamp & if so shows an exclamation mark. Finally, there's a small linked graphic that "refreshes" the page beside "homepage" and the "edit" link (essentially, it's just a link to the page itself) so a user can check the edit status before deciding to edit it themselves. For server load reasons I decided to not have an automatic check (once every 5 minutes for example) since most people read & don't edit much of the time so it made sense more to encourage people to check edit status themselves. Of course, it would also be possible to have edit.php check to see if the file was edited in last 15 minutes and if so, ask the user if they wanted to continue with their own edit. Hmmm...I'll have to think about that. As it sits it worked pretty well when tested (but remember, I'm into small group collaborative writing tasks....I'm not sure how it would work if the pages were "open" to everyone). It originally took me several hours to write the code myself, but I'm sure it would take JW or DarTar or Jason maybe 30 minutes....and the code would probably be more efficient (I'm not a real coder remember :-( ) -- GmBowen (aka Mike) (I've now provided my code & mods @ [GmBowenRecentEditCheck] for people to play with)

Searching (in) comments

• Yes. And related: an extension of this or the general search function to search by comments content (in addition to page name or page content) would, I think, be also useful. --JW
  • Agreed. -- JsnX
• Nice idea :). For comments by user X (and, why not, mods by user X) we could imagine something similar to Google syntax for site-restricted queries. E.g.: I18n user:JavaWoman. The scope of the query (pages, mods, comments, anywhere) should be settable as a radio button (similar to Google's restrict search options). FYI, Comments by user X, Pages owned by user X and Changes done by user X were already partially addressed by the following action proposals: UserCommentsAction, UserPagesAction, UserChangesAction -- DarTar
  • In general....given the complexity (and utility) of some of the conversations now happening in the comments, I think that we should consider either (i) the current textsearch being expanded to include the comments, or (ii) a separate action be written directed at searching the comments table (possibly an easier route). The latter might mean we consider renaming the search pages to SearchText, SearchTextExtended & SearchComments. [I now realize that this "search comments" feature is a "lost" feature. I realize now that earlier versions of this wiki had the comments stored in the pages table and were therefore searched. When they were moved to a separate table, the ability to search comments was lost. (Update: See my GmBowen directory for a (temporary) solution for this....even separates results for comments & pages into two columns) A separate action to list all comments by a user would also be useful. In a related comment on the comments, and given my arguments about the complexity of conversations in some of the comment threads now, I suggest that we also consider developing code for threaded discussions in the comments....which I think will considerably enrich collaborative efforts (such as we engage in). -- GmBowen

Order of the text-search

Highlight unseen Recentchanges

• If it's only for highlighting, OK, but I'm not waiting for that. If it's for filtering, please no. I quite often trace back several days to re-review pages or comments --JW
  • OK. Point taken. I was considering doing some form of filtering, but will now only consider higlighting, as requested. -- JsnX
  • I totally agree with JW's point -- DarTar
    • Actually, I could imagine separate functionality with filtering being useful on a busy site, but then as, say, UnseenChanges and UnseenComments - in addition to the current "Recent" functionality; that way the semantics of "recent" would not be changed. But I agree it's low priority. --JavaWoman

"target=" in external links?

• Yeap, use this directly within the wikka page you are working on

•  <A href="http://google.com" TARGET="_blank">Google</A> 
• It will show up a normal link Google
• In this case the TARGET="_blank" bit is what does the trick.
• Assuming this is what you were originally after, it has the advantage of no code changes. NickDamoulakis
  • I assume you meant the above code to be put in double quotes like this:

  •  ""<A href="http://google.com" TARGET="_blank">Google</A>"" 
  • Since I use Wikka inside an iframe I need to use target a lot, so I modified the forced links section in wakka.php from:
  • //if ($url!=($url=(preg_replace("/@@|££||\[\[/","",$url))))$result="</span>";
    if (!$text) $text = $url;
    //$text=preg_replace("/@@|££|\[\[/","",$text);
    return $result.$wakka->Link($url, "", $text);
  • To this:
  • //if ($url!=($url=(preg_replace("/@@|££||\[\[/","",$url))))$result="</span>";
    if (!$text) $text = $url;
    if ($pos=stripos($text, ' target=')) {
        $target = substr($text, $pos);
        $text = substr($text, 0, strlen($text)-strlen($target));
    }
    //$text=preg_replace("/@@|££|\[\[/","",$text);
    return $result.$wakka->Link($url, "", $text);
  • I can now do forced links like this:

  • [[http://www.google.com Google target="_top"]]
  • What I don't like is target within imagelinks, the way it is now you have to write like this:

  • {{image url="whatever.gif" link="http://www.google.com" target="target='_top'"}}
  • This would have been better looking:

  • {{image url="whatever.gif" link="http://www.google.com" target="_top"}}
  • /AndreasHeintze

Easy way of adding links

• MatthewLangham, I propose AddLinkAction as solution for adding links on a page in a structured way. I also added (under the Beta section at the end) a JavaScript-link that you need to bookmark to fast add a link in two mouse clicks... (Works with Firefox and IE under XP, still needs testing with other browsers) -- OnegWR

Image dimensions

• I agree that it would be better to have defined width and height in the resulting img element: faster output, and no "jumping" pages. However, PHP can easily derive these dimensions by itself - would that be sufficient or do you think it's also necessary to be able to override the actual dimensions of the image file? --JavaWoman
  • There surely will be users which want to do that. My suggestion (if possible): allow height and width as optional input. If nothing the variables should be filled with the values of the image. --NilsLindenberg
    • Noted. More easy suggestions like this, please. :) --JavaWoman
      • Yes, that exactly, Nils. LOL Lemme get my list, JW. ;) Seriously, though, I really like what you all have done with this wikki, and the multitude of suggestions are only because I'm getting invested in it. *g* I've been sick or I would've worked on the DeleteSpamAction changes sooner so I could feel like I was actually doing more than "I want it to do this!" ;) --MovieLady

• That's great, Christian, thank you! --MovieLady

User registration control

Embed a blurb from a news page into another page?

• I am doing this using the IncludeAction - at least you only update one page (TheNews). --ChristianBarthelemy
  • Thanks, I'll try that out. --MovieLady
    • Did you do anything to get it to add only part of the page being included (for example, down to the first horizontal line)? --MovieLady
      • Nope. I just only keep the news updated in TheNews page so that the whole page is displayed when included. --ChristianBarthelemy
        • Ah well, I'll keep working on trying to figure out a way to do it. *g* Thanks! :) --MovieLady

Logging-out

Backlinks

• Noted - good suggestion. --JavaWoman

User names

• Should not be that difficult? In usersettings.php there is a part where a new user is created. After the mysql query which adds the user to the user-base, another query which inserts the user-page to the pages table is needed. Anybody here whos good in creating mysql-queries? --NilsLindenberg
  • Automatically creating a user page should certainly be possible (easy enough). But while on some Wikis you may have a small group of people regularly contributing, on others many people may register just to post one or two things, and then disappear, never even look at their user page - and you'd end up with a lot of empty pages, all of which will show up in the PageIndex. So it really should be a (WikiAdmin) option to determine whether user pages are automatically created or not. --JavaWoman
    • Excellent point, hadn't thought about that. :) --MovieLady
      • See AutomaticUserPageCreation for a first version. Or test it [http://www.niehle.info/UserRegistration∞ here] And it is of course an additional config-option :) --NilsLindenberg
        • Fabulous! I'll check it out. --MovieLady

if (!$this->IsWikiName($name)) $error = "User name must be WikiName formatted!";

if(false);

echo "You are ".$this->Link($this->GetUserName());

• Good idea, except that having a non-wikiname causes problems elsewhere. For instance, I edited my db by hand and changed a couple of names to non-wikinames, and then one of the users with a non-wikiname forgot (sigh) her password. She tried to request a new one, but the temporary password function wouldn't recognize her username as being valid. And that's certainly not the only place that checks for a valid username. (The automatic sig on comments doesn't show a hotlink to a username if it's not a wikiname, either.) Just FYI. :) --MovieLady
  • I do really want to use non-wikinames (or just turn wikinames off completely somehow). The temp pass and comments can be easily modified, comments can use the same header code above if the user exists. I know many of us are used to wikinames, but it is extremely odd and intimidating to newbies. Thats why Mediawiki dropped all wikinames so not to intimidate anyone and lessen the learning curve. So I hope there is some way to make wikinames an optional thing. --RyanKnoll

List of special actions?

• Have a look at UsingActions which has a current list of available actions. We're working on automatic actions documentation, so that both that list (expanded with short descriptions), and documentation pages for individual actions will pull content from the actions files themselves. (Not for 1.1.6.0, but likely the version after that.) --JavaWoman
  • Thank you! I figured something like that somewhere, but couldn't find it. :) I'm more than happy to help out with documentation if you need help! --MovieLady

Allow spaces in pagetitle

• Wikka already uses the SmartTitle formatter, which displays the highest-level header present in the page (like: ===== This is the main heading) as a HTML title. See for instance the title of FormattingRules. -- DarTar

User-defined formatting rules

• An array in wikka.config.php
• A function defined in a standard place (like ./formatters/wakka_user.php). ./formatters/wakka.php could then call that function, if it exists). Maybe even a flag in wikka.config.php to enable it.

Compile Category action

Compatibility & Installer

Handling the config

Markup for code not to be shown

markup of diff pages

• mark up a deletion with the <del>...</del> tag; since we actually know the timestamp of the change, add that in the datetime attribute (properly formatted);
• mark up an insertion with the <ins>...</ins> tag; same recipe for the timestamp
• then use the stylesheet to render those two in whatever font/coloring you like (even as done now) - but note that most browsers have a default rendering anyway

// deletions
else if ($thing == ""¥¥") 
{
$timestamp = $wakka->GetPageTime(); //hopefully this function returns the right format?
return (++$trigger_deleted % 2 ? "<DEL datetime=\"$timestamp\">" : "</DEL>");
}

Problem: Scrolling in the search - field

Problem: Five Line Breaks

DB Export

Code block formatting

----------------------------------------------------------------
OBJECT_TYPE		  COUNT(*)
------------------ ----------
FUNCTION				   12
INDEX					  55
LOB						 4
PACKAGE					 2
PACKAGE BODY				2
SEQUENCE					9
TABLE					  37
TRIGGER					 6
VIEW						1
9 rows selected
no rows selected
--------------------------------------------------------------------

Various suggestions

Other method to attach files

Installation problem - UTF-8?

Add page link & other suggestions

• It would be Really Nice to be able to have an Add Page link that allows a user to create a new page without having to edit an existing one. (I don't belive this is currently possible, I'm a newbie however) Perhaps this could be achieved via a simple HTML Form that prompts the user for a Page Name, and Category. It would be even better if the Category was selectable (dropdown list) from existing categories. And to top the whole thing off, it would be perfect if it was possible to define Template files (eg. per Category) where by when a user creates a new page of category ABC, the template file for ABC is used as the default page text. This would aid in keeping some kind of consistancy between pages of the same category. (ie. for one thing the correct category definition could be placed in the appropriate location/style). An Add Page link would posssibly be usefull on the standard Category pages, especially as the Category is already known.

• It would be nice if ACLs were somehow inheiritable from their creating pages (Created either the current way or via the above described method)

• Is it possible to define User Groups to simplify editing ACLs also.

• I tried to do something with ACLsWithUserGroups.

• Finally, (although I think I can possibly do this one myself) , On the Editor Page a link to the standard FormattingRules page would be most useful. Especially if it opened in a different window.

• I like the Add Page link idea. It would be really simple to implement, too. Perhaps a text form where you'd enter the page name, which would take you to http://some.host.com/wikka.php?wakka=NewPage/edit, where you would actually create the content. I like it! --KickTheDonkey

Disable CamelCase

Rename Pages

• Yeah, so I found this... RefactorWiki which