• 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

• 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

• 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

"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

• 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

markup of diff pages

• 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

Add page link & other suggestions

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

Disable CamelCase

Rename Pages

• Yeah, so I found this... RefactorWiki which supposedly does exactly that (I haven't tested it personally) - JonathanMitchem

Star Rating System

• LuxiO, what criteria would you suggest for such a ranking system? --BrianKoontz

• BrianKoontz, first i think that the rating system should have an extra table in the main database so that every item we want rate should have a unique identification number. Then we manipulate this extra table from an internal action... maybe? --LuxiO

• That sounds like a suitable approach...but my question is, how would users be expected to "rank" a page? Are we looking for a measure of suitability, quality or aesthetics, or maybe popularity? Is it really possible to assign a relative ranking to pages with dissimilar content? --BrianKoontz

• It would depend on the use of the wikki... for example, Rant This Space! is purely for entertainment and therefore people would be encouraged to vote based on how entertaining the page was. In a corporate setting it might denote importance, or relevance to the project. Then the home page could display a list of all pages with 5 stars, and new members would know to read them first. Icons other than stars could also be used.