Revision [8275]

This is an old revision of SuggestionBox made by ank208.neoplus.adsl.tpnet.pl on 2005-05-18 10:09:08.

 

suggestion box

Last edited by ank208.neoplus.adsl.tpnet.pl
Wed, 18 May 2005 10:09 UTC [diff]


feedback is welcomed and appreciated. use the form or edit this page.

please help to keep this page readable: add new entries at the top (right below the form) and add a header!

>>

bugs vs. feature suggestions

please post issues/bugs to the appropriate page:


issues often asked for
>>

Fill in the form below to send us your comments:






 


generate id in forms; allow class

i know we've dicussed this multiple times but could not find an actual suggestion; i've made it into a semi-spec.
every form really should have an id (attribute) to provide a 'hook' for styling (and javascript, if desired). we have a ""formopen()"" method in the core that should be used to generate the opening form tag (and its counterpart ""formclose())"" - but this method does not generate an id nor accept a parameter to create one. it should be able to do both:
in addition, some forms really need to have a class attribute (as well); the button-form for the grabcode handler is a good example: if you have a number of forms on a page that all should have the same styling, a class would provide the 'hook' rather than the id (which should still be there). so the ""formopen()"" method should also:
--javawoman

hiding anonymous host/ip from non-administrators

on the wiki i run, it is not desireable for the ip/hostname of anonymous users to be displayed to just anyone. i've made a small modification to hide the ip/hostname of anonymous users to users that (a) are not administrators, and (b) not themselves. in handlers/page/show.php, around line 80 you can find:
print("\t<div class=\"commentinfo\">\n-- ".$this->format($comment["user"])." (".$comment["time"].")\n");
i modified this to:
if ($this->isadmin() || $current_user == $comment["user"] || $this->loaduser($comment["user"]))
{
    print("\t<div class=\"commentinfo\">\n-- ".$this->format($comment["user"])." (".$comment["time"].")\n");
}
else
{
    print("\t<div class=\"commentinfo\">\n-- anonymous#".str_pad(dechex(crc32($comment["user"])), 8, "0", str_pad_left)." (".$comment["time"].")\n");
}
and in actions/recentlycommented.php:
if (!$this->loaduser($comment_by)) $comment_by .= " (unregistered user)";
was changed to:
if (!$this->isadmin() && $this->getusername() != $comment_by && !$this->loaderuser($comment_by))
{
    $comment_by = "anonymous#".str_pad(dechex(crc32($comment_by)), 8, "0", str_pad_left);
}
and in actions/recentcomments.php:
if (strlen($comment["comment"]) > 120) $comment_preview = $comment_preview.".... ";
after this add:
if (!$this->isadmin() && $this->getusername() != $comment["user"] && !$this->loaderuser($comment["user"]))
{
    $comment["user"] = "anonymous#".str_pad(dechex(crc32($comment["user"])), 8, "0", str_pad_left);
}


you will probably need to also update the xml handlers and the history page handler, but right now anonymous users cannot edit pages on my wiki. (actions/recentchanges.php, handlers/page/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
    • amp;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
      • amp; 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

  • amp;see also wikkawithphpbb --javawoman


documentation

documentation on the site here seems . . . fragmented i think is the best word. admin features are the example i'll use cuz it was my big hurdle. at this point i've only been able to find that the account created at install is the admin, and as site owner i should give access to that account to the people that i want to admin the site. is there more to it than this?

  • amp;you can add usernames to the admin-list, if you don't want to share the admin-account. specify multiple wiki names separated by commas e.g: jsnx, hendrikmans, cooljoeadmin in the wikka.config.php in "admin-users" (see configurationoptions). admins can see, edit and delete any page, even if they are set to private.

searching for "admin features" yeilds over 100 entries. there's nothing in categorydocumentation detailing admin features, and the page wikkafeatures mentions several admin features that have neither further explanation nor links.

  • amp;will be changed, but not today :)

on top of all this, searching acl reveals
one page that just mentions acl more in passing. the page with category instructions is also a little under informed. you'd think that after following 2 step instructions that it'd work.

  • amp;i think you mean aclinfo and wikicategory? if you have questions about a documentation-page, please leave a comment about that on the page. we can only make it better if we know what is not understandable. remember that this is a wiki :)

this page is another example. i started reading it the other night looking for something specific but by the time i finished reading it, i had about 6 different things i felt like commenting on. it's so long tho that i felt my comments would be missed so i didn't bother. rather than piled on one after the other, after a certain age, each of these subjects should be broken off to their own page in a categorysuggestionbox and listed here. (i mean this is a wiki and space isn't necessarily at a premium) this would make it easier to find and contribute to a specific topic. if a search produces this page as a result, the initial impression is that the search was really messed up hitting "suggestionbox" with my search terms.

anyway... the suggestion? organizing documentation should be the priority. this site looks quite nice. it's a shining example of how wikka works when beat into perfect shape. but the site i installed looked and acted nothing like this...

  • amp;yes, we can and should organize the documentation better (and some other parts of this wiki). we will move it to a new subdomain (see documentationlanguagelinking) and after that we can bring it in better shape. but don't forget that this is a wiki and you have the right to participate :) --nilslindenberg
    • amp;does this mean that if i go ahead and make a "category suggestion box" and split this pages into seperate doco's that it won't step on people's toes? i think this would be good and don't mind doing that bit of work - but don't want to annoy too many people [espec. seeing as i am quite the newbie here...] -- kiltannen
      • amp;i say; simply start and wait for the reactions. thats how i do it, most of the time ;) --nilslindenberg



pages linking to nonexisting pages

as movielady pointed out somewhere, it could be usefull to see if there are pages linking to a non existing page (for example when you have renamed the page and have to update the links).

the following solution just prints out the links, without any other text ("the following pages link here") - which should be better placed in the backlinks action.

change in handlers/page/show.php the lines with if (!this->page) to:
  1.     if (!$this->page)
  2.     {
  3.         print("<p>this page doesn't exist yet. maybe you want to <a href=\"".$this->href("edit")."\">create</a> it?</p>");
  4.         print $this->action("backlinks")."</div>";
  5.     }

  • amp;what's the </div> for? i see no opening <div>. --javawoman
    • amp;it closes the <div class="page">. --nilslindenberg
      • amp;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
        • amp;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.
          • amp;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


sending 403 headers

(related to the
search engine results inflation item below)

for pages to which the user has no read-access, do you think it might be feasible/interesting to send - along with the
you aren't allowed to read this page message - a http header like the following:
 header('http/1.0 403 forbidden');

-- dartar
  • amp; oh, and maybe 404 headers for missing pages (which would help prevent se from spidering links to non existing pages)? -- dartar


numbers as page names?

i'm curious about the wikka convention that numbers cannot be page names. i'd like to be able to create "date page" (e.g. 2005-02-26) for notes and journaling, so this is a feature i'd definitely suggest.

btw, doing something along the lines of "journal/2005-02-26" or "journal_2005..." wants to create an external link.

thx, robertdaeley
  • amp; agreed, we should drop this restriction. numbers in page names might also be useful to use wikka as a wikipedia:bliki bliki engine, i.e. a hybrid blog/wiki software which is drawing increasing attention in the socialsoftware social software community. robert, take a look at this user-contributed plugin, which allows creating a calendar with single pages for days: jwcalendarwithpagecreation -- dartar


configurable name for wikka engine

i think it might be interesting for many of our users if we gave the possibility - in the install/upgrade wizard - to
rename the engine from wikka.php to something else (for instance, index.php). this might be useful in cases where rr are off and the user wants to avoid long urls: http://www.mydomain.com/wiki/wikka.php?wakka=homepage can then become http://www.mydomain.com/wiki/?wakka=homepage. the name should be specified as an option in wikka.config.php, for instance

 &quot;wikka_engine&quot; =&gt; &quot;wikka.php&quot;, 


this option might also allow using different engines (say, different versions of wikka.php) on the same installation.
-- dartar


search engine results inflation

i have recently installed wikka on my personal website. everything works fine, except that the textsearch link in the page header (which i masked through css - i don't want to hack the code) produces dozens of search results that i really don't want to be cached on google. same story applies to the revisions and history links that are cached on search engines: this is what happens in the case of our main server. i'd also would like to avoid default wiki pages (like sandbox, mypages, usersettings etc.) to be crawled and cached (simply setting acls to !*-!*-!* won't do the job). maybe we should think of a way to allow the user to decide
what kind of content of her wikka-powered site should be spidered by se and what content should not. -- dartar
  • amp;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

1. it often takes too much time to check if a wiki has changed and what has changed. in the case of wikkawiki one has to check recentchanges as well as recentlycommented. a combined page would be more convenient - richard
  • amp; hope you have a large screen: sowhatarethenews --christianbarthelemy


generate page from an external database

as described in dynamicpagegeneration i'd like to create a mailling-like system to fill in pages containig custom fields with data from an external database or a simple table. this could be done through a few actions or by writing a new handler.
this idea can be extended to an inline editor to add/remove/edit entries in this external table if wikka store creditentials with write access in its own tables.
the main goal is to integrate data from an existing knoweldge base in a wikka based documentation repository.

dotmg insists about favicon.ico and robots.txt

please add the following two lines to ./.htaccess
rewritecond %{request_uri} !=/favicon.ico
 rewritecond %{request_uri} !=/robots.txt
 rewriterule ^(.*)$ wikka.php?wakka=$1 [qsa,l]
this will prevent /favicon.ico and /robots.txt from being redirected to wikka.php?wakka=favicon.ico
with these 2 lines, we don't have to modify wikka.php as suggested in favicondotico --dotmg
  • amp;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

create a table which maintains a mapping between wikka categories and an associated predefined icon graphic. when the directive {category_icon} is used the category's icon is dropped into the page at the location of invocation. -karmatester

  • amp; 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
    • amp; 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
    • amp; some more at iconsinwikka -- christianbarthelemy


automatic table of content generation

a table of contents {toc} directive is replaced by an ordered list of defined headers in the wiki page. this makes it easier to navigate pages which are very long like this one. -karmatester
  • amp;have a look at tableofcontentsaction for some ideas about creating a toc (automatically or triggered by an action...) --javawoman


wikka markup inside tables
- i think it would be nice if you could use wikka markup (""
bold, italics, underline, etc."") inside of tables. - richardterry
  • amp;richard, thanks for the feedback. it is on my agenda to look at another solution for tables. my plan is to allow straight html table syntax after running it through the "safehtml" checker. but i need to check that there are no security risks with this first. also, i'll take a peak at your suggestion too. -- jsnx
  • amp;check out my proposal for an extended tableaction which does provide this. (tableaction is intended as a preliminary solution until we have table markup.) --javawoman


robot friendly pages


right now (1.1.6.0), if a non-existant page is requested, the wiki returns status code 200, which will cause the page to be indexed by search engine spiders. it'd probably be better to return 404 (not found) or 410 (gone) or include robots exclusion meta tags in the pages that don't exist. --barkerjr
  • amp;ah, maybe this is why a now non-existent page that i deleted 2 months ago is still getting 50hits or so a day from the porn/vicodin/viagra sites that linked to it (don't ask me why...it was a completely inoccuous page)...at least according to the referrers database table. --gmbowen
  • amp;see robotfriendly. --dotmg


kant-en-klaar code blocks


a micro-idea before going to bed. we all know it's a bad idea to copy code blocks from the formatted version of a page.
if i want to test some freshly posted code, here's what i have to do:
  1. open a /raw version of the page;
  1. scan the page for the chunk of code i want to save (this can be pretty difficult on long source pages with no syntax highlighting);
  1. open a text editor;
  1. copy the code block;
  1. paste it in the text editor;
  1. save the file.

wouldn't it be nice to have at the end of each code block a small link pointing to a handler allowing the user to download the code block with the right name and the right extension just
with one click?

see grabcodehandler for a first proposal -- dartar


security verification test from wikini

on the top of most page handlers, the wikini developers have:
// vérification de sécurité
if (!defined(&quot;wikini_version&quot;))
{
die (&quot;accès direct interdit&quot;);
}

i'm not sure what exactly this does, can anyone enlighten me; and if it is a good idea, then it should considered for wikka too... --ianandolina
  • amp;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


mod_rewrite idea (.htaccess)

(the following was copied from a comment on modrewrite -- javawoman)
hi, i discovered that the default .htaccess included did not work for my setup up. i needed to include ""rewritebase"" /directory/ as well since wikka is installed in a subdirectory. i hope this helps anyone having trouble getting wikka to work.
-- h-67-102-97-191.mclnva23.covad.net (2005-02-11 04:49:37)
the installer
correctly deduces the base path for the configuration; it could conceivably also detect if it's sitting in a subdirectory, and if so, dynamically change the .htaccess file and include the correct ""rewritebase"" statement to take care of this. --javawoman


separation of wakka class from wikka.php

i use wikka as wiki engine of my page.
imo, the wikka.php file is too big to be one single file. i suggest that we separate the wakka class into new file, say wakka.class.php
and then in the wikka.php, e.g at line where the wakka class previously located, simply we put:
include ('wakka.class.php');

-- din
  • amp;din, this is a very good idea. i fact, the idea had crossed my mind already, but thanks for the reminder. :) indeed, a class belongs in a file of its own. --javawoman
    • amp;maybe a folder called classes? the handlers/page/diff has a bunch of classes inside, too. --nilslindenberg
      • amp;with my current proposed structure on wikkacodestructure, it would go into the library folder; classes that are shared, into library/common. i prefer a functional separation rather than one based on coding format. --javawoman


inherit acl from 'parents'

create a page and when creating a page from there, give the option to copy the acl of the first page.
should pages be linked in some form to some documents given the fact that wikka is flat, not hierarchic.
forthelazy - chatlog and summary.
-- freeknl
  • amp;imo the acl system has to be dumped and/or renewed/rewrittem to accomodate usergroups..
  • amp;i have been thinking of presenting a modification that will actually implement this user managment system ..
  • amp;having privileges for each page is making userprofile-specific-features on wikka efficiently non-existant.
  • amp;the ability to create custom usergoups ( aka levels, profiles etc. ) would enable the addition such features
  • amp; ( ip/hostname display , access to special parts of the wiki and such .. ) -- georgepetsagourakis
see also hierarchiesandinheritance for some background --javawoman


paragraph instead of line-breaks

(copied from whatsnew -- dartar)
why is it that the formatter creates line breaks instead of paragraphs? i've been trying to figure out a way to get wikka to do this, but it may be nice for there to be some sort of option in a future release. paragraphs tend to be more useful for doing css formatting.
-- scumble

+1 &#8212; semantically, wikka's current lack of proper paragraphs and liberal sprinkling of line breaks is really undesirble. i made a hack-mod on my wakka some time ago in formatter/wakka.php (just after the preg_replace_callback):

$pattern2 = &quot;/^(\040|\t)*(?!&lt;|\040)(.+)$/m&quot;; //matches any line with no &lt;element&gt; (and variable leading space) - assume a paragraph
$replace2 = &quot;&lt;p&gt;\\2&lt;/p&gt;&quot;;
$text=preg_replace($pattern2,$replace2,$text);

$pattern1 = &quot;/^(\040|\t)*(&lt;(?!hr|(\/|)h[1-6]|br|(\/|)li|(\/|)[uo]l|(\/|)div|(\/|)p).*)$/m&quot;; //matches any &lt;element&gt;text lines not considered block formatting
$replace1 = &quot;&lt;p&gt;\\2&lt;/p&gt;&quot;;
$text=preg_replace($pattern1,$replace1,$text);


i don't know how that will affect wikka (it was designed for my formatting which is different to wikka slightly), and there is probably a much better way to do it (call a post-formatter?), but it is possible using a small modification at least... --ianandolina


save pages to pdf format

(copied from wikkadevelopment --nils)
page output to an adobe pdf file using fpdf.
e-mail this page facility
--jamesmcl


usergroups

(copied from wikkadevelopment --nils)
yet another idea from me:
usergroups. so i can create a group of users, and just write that group into the acls...
gregorlindner
- take a look at groupmanagement (which doesn't seem to be finished) - or at aclswithusergroups.


"in work" for wikka-pages

(copied from wikkadevelopment --nils)
add a page property, 'status' [?] that can be used to facilitate code development within wikka. imagine a very basic cvs system. a user can change the status to "in use' while considering improvements to the code, and then change it to 'available' when done. this may prevent this scenario:
  • 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.
or
  • another user has to go back through his code and incorporate the changes made by the first user.

  • amp;comments:
  • amp;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
    • amp;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
  • amp;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
  • amp;i agree, it's an important issue (some wakka forks have already addressed the problem of concurrent editing) -- dartar
  • amp;jsnx: if it's purely informational, that's better; i thought the intention was some kind of locking. so you'd have something like:
    • amp;-state: in use | available
    • amp;-timestamp: in use since
    • amp;-note: applies to the in use state only
  • amp;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?
  • amp;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.
  • amp;gmbowen: is yours completely automatic or user-initiated? what happens in the run off to catch the train scenario? -- javawoman
  • amp;(i) it's purely informational, not a "lock&quot;...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

(copied from wikkadevelopment --nils)
add the ability to 'search for all comments by user x'. how this might be useful: i want to find a comment by javawoman
(really?), but i can't remember which page it was on -- she's quite prolific! -- (i admit i'm easily distracted. what am i doing here, now!? :)) so i use this new function to list all of her comments.
  • amp;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
    • amp;agreed. -- jsnx
  • amp;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


(copied from wikkadevelopment --nils)
it would be good if the text-search would be sorted in some way. if i search for example for "gmbowen", a page with the exact match (his userpage) should be on the top of the results. the next results perhaps in alphabetical order? --nilslindenberg


highlight unseen recentchanges

(copied from wikkadevelopment --nilslindenberg)
add fields to the 'users' table [?] to track when recentchanges and recentlycommented were last viewed. then recentchanges and recentlycommented can by modified to highlight new items since the user last viewed the page.
  • amp;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
    • amp;ok. point taken. i was considering doing some form of filtering, but will now only consider higlighting, as requested. -- jsnx
    • amp;i totally agree with jw's point -- dartar


is there a way to include a target in a link, so that the link opens in a new window?
--gregorlindner


signature

(copied from wikkafaq, but perhaps better at wantedformatters? --nilslindenberg)
does wikka support automatic user signatures in pages (not comments)? i need some code so that users don't need to enter their username and time/date when they are working on a page in threadmode. i've searched in the docs, but i could not find anything about this, any ideas?
-- jeroenjansen (2005-01-28 11:35:43)

  • amp; jeroen, there is a hack for automatically adding a user's signature in wakkawiki posted by nickk on his homepage. it should be easy to adapt to wikka. -- dartar
    • amp; dartar, just saw your reply. thanks for the hint! --jeroenjansen


most wikis i have set up have the need for a page containing a list of links. it would be great if wikka could support this in some way - such as providing an easy way of adding links to a configured page. one way of doing this could be a simple java scriptlet that you configure with the address of the link page. then, you mark a link in a web-page, click on the scriptlet, enter a short description and bang - the link is added to the wiki page.
the del.icio.us page offers some user contributed hacks which may be a starting point.

matthewlangham


create rewrite rules on install

copied from comment on wikkainstallation --javawoman
since i installed wikka in a subdirectory under the domain root i needed to add the following to the .htaccess file just under """rewriteengine on""":

""rewritebase"" /subdirectory/

devs, how about writing the .htaccess rules at the same time you write out the wikka.config.php file since you automatically pickup the wiki base location at that point?

-kt
-- karmatester (2005-01-26 06:52:07)


image dimensions


the addingimages image action really needs the ability to specify image height and width. :) --movielady
  • amp;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
    • amp;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
      • amp;noted. more easy suggestions like this, please. :) --javawoman
        • amp; 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
dear all: see my proposal at enhancedimageaction
  • amp; that's great, christian, thank you! --movielady


clearing acls


there should be a button on the acl page to "reset acls to default". what this would do is delete the record for the current page from the acls table. there is a distinction between setting the acls to the sites default values and not having acls defined for a page. if the acls are set and the default values get changed, the page will remain at the set values. however, if no acls are defined, the page will always use the default values.

to help show the distinction, there should be a visual indicator on the acl handler page which states whether the page has acls defined or is using the site's default values. basically, just check for a record in the acls table for the current page, and display a message accordingly. -- jsnx

user registration control
it would nice to have the registration function check to make sure there isn't another account with the same email already registered so that one person doesn't clutter up the db with multiple accounts. (or at least the configurable option to check for only one email/one account.)

it should also then be easier (i would think) to use it to essentially ban by email address; if the registration process checked for an email in the user table, found that it was already in use and didn't let the person create a new username, one could use the wonderful aclswithusergroups hack that christian created to make a list of banned users by username. yeah, yeah, folks who want to abuse the system could always create new email addresses on the various free sites, but that's an awful lot of work, and this would at least slow down some of it. --movielady

  • amp;you know how many testusers my wikka already has? *g* this should do the job (this time no config option, sorry jw :)
  • amp;
        function existsemail($email)
        {
            $count = 0;
            $query =    &quot;select count(email)
                        from &quot;.$this-&gt;config['table_prefix'].&quot;users
                        where email='&quot;.mysql_real_escape_string($email).&quot;'&quot;;
            if ($r = $this-&gt;query($query))
            {
                $count = mysql_result($r,0);
                mysql_free_result($r);
            }
            return ($count &gt; 0) ? true : false;
        }
  • amp;place this function in wikka.php right after function userwantscomments(). and change in actions/usersettings.php the following line:
    else if (strlen($password) &lt; 5) $error = &quot;password too short.&quot;;
    to
    else if (strlen($password) &lt; 5) $error = &quot;password too short.&quot;;
    else if ($this-&gt;existsemail($email)) $error = &quot;you already have a username.&quot;;
  • amp;--nilslindenberg
    • amp; lol i can imagine. thanks so much for this - i'll try it out this evening. --movielady

  • amp; speaking of registration control, note to self: make a configuration option to turn off new account registrations. some sites might be private and not want people registering. admin privilege should override this and still show the registration fields in usersettings, to save the admin from having to go into the database manually to add acounts or some other hack. -- jsnx
    • amp; (you saw userregistration by nils? i think it, or something like it, should be standard. mike)
      • amp; doh! i somehow missed that. that's pretty much what i had in mind. nice job, nils! :) -- jsnx
        • amp;thank you. about your admin-adding-user case: that's an addition to useradmin, not for usersettings. --nilslindenberg
      • amp;there's also code around that uses gd & that could be built onto nils' code that generates a "registration password" automatically and outputs it as a distorted graphic image.....the code is intended to befuddle auto spam registers & thus stop open-registration sites from being hit by spam bots that register themselves as users. ultimately, as the bots become more sophisticated i think we'll have to use something like that or else sites like this one (with open registration) will be victimized. here and here are examples of what i mean (i like the simplicity of the first version in the second example). -- gmbowen
        • amp;yes, "captcha" is an old trick - it will keep out some bots (but not all) and it will keep many people out, too, like those who are visually handicapped (not just people who are totally blind - being colorblind may be enough to be defeated by such tricks). add a sound equivalent? well, there are people who are deaf and blind. are we going to deny them access to our wikis? i'm not in favor of making wikka inaccessible when we should be working towards making it more accessible. --javawoman.


rss options


it would be wonderful to be able to choose what kind of rss feed is created for a page. for example, ""

Error: Invalid RSS action syntax.
Proper usage: {{rss http://domain.com/feed.xml}} or {{rss url="http://domain.com/feed.xml"}}

""/""

Error: Invalid RSS action syntax.
Proper usage: {{rss http://domain.com/feed.xml}} or {{rss url="http://domain.com/feed.xml"}}

"" could show only the headlines and the update field (current setting), ""

Error: Invalid RSS action syntax.
Proper usage: {{rss http://domain.com/feed.xml}} or {{rss url="http://domain.com/feed.xml"}}

"" could show a blurb of the updated info, ""

Error: Invalid RSS action syntax.
Proper usage: {{rss http://domain.com/feed.xml}} or {{rss url="http://domain.com/feed.xml"}}

"" could show the whole update. --movielady


embed a blurb from a news page into another page?


i currently have no idea how one would approach this, but thought i'd toss it out there for others to think over. i would find it really useful to have an announcement action (maybe ""Unknown action ""news""""?) that i could use which displays only the most recent (configurable) number (e.g. ""Unknown action ""news"""" would show the most recent two entries from the page) of entries from a specific (configurable or static?) page. right now i do this by hand, adding the current announcement to both the front page and the news archive page (so i'll have a history of the announcements), and boy, what a pita! what i'd like to be able to do is just edit the news page and have it automatically update what displays in the news area on the front page. possible, or am i smoking something i need to share? ;) --movielady
  • amp; i am doing this using the includeaction - at least you only update one page (thenews). --christianbarthelemy
    • amp; thanks, i'll try that out. --movielady
      • amp; 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
        • amp; nope. i just only keep the news updated in thenews page so that the whole page is displayed when included. --christianbarthelemy
          • amp; ah well, i'll keep working on trying to figure out a way to do it. *g* thanks! :) --movielady


logging-out

perhaps the installer should tell the user that he will be logged-out (because of the new cookie-names). would be nicer. btw, the /setup directory needs an update (or better the files in it). --nilslindenberg



it would be wonderful to have the option to display the results of the ""AdminDevelopmentDiscussions
AdminDevTodo
AdminWatchList
AdminWikkaWebsite
AndreasTengicki
AutomaticUserPageCreation
CyneBeald
EditHandler
HtmlSpecialChars
NonWikiUserNames
OneYearOld
RyeBread
SpanishLanguage
SpreadTheWord
SuggestionsArchive
SupportingWikka
TemplateSystem
TestHomePage
TestHomePage1
TestHomePage2
TestHomePage3
TestHomePage4
UnOr
URUniqueEMailModule
WelcomeRegisteredUser
WelcomeRegisteredUserFR
WikkaBugsResolved
WikkaDevelopment
WikkaDevelopmentFR
WikkaSpamFighting"" action in columns, similar to what ""The following 30 page(s) belong to SuggestionBox

AdminDevelopmentDiscussions [AdminDevelopmentDiscussions]
AdminDevTodo [AdminDevTodo]
AdminWatchList [AdminWatchList]
AdminWikkaWebsite [AdminWikkaWebsite]
AndreasTengicki [AndreasTengicki]
AutomaticUserPageCreation [AutomaticUserPageCreation]
CyneBeald [CyneBeald]
EditHandler [EditHandler]
HtmlSpecialChars [HtmlSpecialChars]
NonWikiUserNames [NonWikiUserNames]
OneYearOld [OneYearOld]
RyeBread [RyeBread]
SpanishLanguage [SpanishLanguage]
SpreadTheWord [SpreadTheWord]
SuggestionsArchive [SuggestionsArchive]
SupportingWikka [SupportingWikka]
TemplateSystem [TemplateSystem]
TestHomePage [TestHomePage]
TestHomePage1 [TestHomePage1]
TestHomePage2 [TestHomePage2]
TestHomePage3 [TestHomePage3]
TestHomePage4 [TestHomePage4]
UnOr [UnOr]
URUniqueEMailModule [URUniqueEMailModule]
WelcomeRegisteredUser [WelcomeRegisteredUser]
WelcomeRegisteredUserFR [WelcomeRegisteredUserFR]
WikkaBugsResolved [WikkaBugsResolved]
WikkaDevelopment [WikkaDevelopment]
WikkaDevelopmentFR [WikkaDevelopmentFR]
WikkaSpamFighting [WikkaSpamFighting]
"" allows you to do. --movielady
  • amp;noted - good suggestion. --javawoman


language file

i would be nice to see all phrases put into a single file. this would allow to translate the wiki in a few hours without changes every single file.
  • amp;look at dotmgs approach at wikkainternationalization. but at least it should work for languages in the range of the "normal" (ascii?) code. if you are interested, you should start a page in where we can collected the hard-coded sentences (would wait for the .6 relase, anyway). --nilslindenberg
    • amp;the most flexible and powerful way to support i18n is still gettext which is supported by php. if we go in that direction (likely), manually creating a "language file" is needless work since gettext does all that automatically for you. and it supports options for handling plurals and such which simple string-to-string language files cannot handle. the problem is that code needs to be written in a way to properly be able to use gettext, so that translatable strings do contain whole phrases with punctuation and do not contain any html markup (actually this is true for simple laguage files as well). currently our code is not "in shape" for i18n though, so that's the first job we'll have to tackle. --javawoman


user names


is there any likelihood of non-wikiname usernames (e.g. movielady) in the future? it's one of the things i've been asked a lot by the users of the site i use wikka for. (most often heard comment: "but other wikis i've used let me do it!") obviously it's possible to create non-wikiname pages, so why not usernames? (i have looked on the site, but i've probably missed the explanation.)

i also agree with nils that it would be really wonderful if some sort of default user page was created when a person creates an account.
  • amp; 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
    • amp;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
      • amp; excellent point, hadn't thought about that. :) --movielady
          • amp; fabulous! i'll check it out. --movielady

y'all are doing a marvelous job, btw and it is greatly appreciated! :) (i will try to contribute as i can, but honestly, some of the programming is beyond me at the moment.) --movielady

i actually hacked usersettings.php to allow for non-wikinames. just change lines such as 152 and 179 from:
if (!$this-&gt;iswikiname($name)) $error = &quot;user name must be wikiname formatted!&quot;;

to something like:
if(false);

then modify header.php so that the username is wikified. so change a certain line (i modified my wikka so much that i can't give accurate lines) to:
echo &quot;you are &quot;.$this-&gt;link($this-&gt;getusername());

i'm not sure how well this will work in the long run, but it worked for me!
-- mikexstudios
  • amp; 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
    • amp; 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



finally using cvs?

i apologize since this idea has been suggested before, and i believe the developers are working to implement it already. however, with the beta of 1.1.6.0 released, i think it would be a good time now to start using cvs. this allows for better collaboration and as each bug fix or feature is implemented, developers and testers can grab new copies and work out further bugs. in addition, this allows more outsiders to participate in the code development process and not wait as long from the transition of releases.

also, i am willing to help with the cvs migration process if needed and help anyone who is interested in learning how to use cvs.
-- mikexstudios
  • amp;there is a cvs version of wikka at sourceforge. just has to be updated --nilslindenberg
      • amp; the "just was meant as an addition to existing ("of course" would have been better, though :). i just wanted to point out the existing (or better non-existing ;) usage of sourceforge, in case mike does not no. it is obviously to me that you have to integrate it into your development-process, otherwise it would not be out of date (*duck & run* ;) --nilslindenberg
        • amp; hi nils. actually, i did find wikka's cvs repository at sf weeks ago, but i forgot to mention it in my above post. javawoman pretty much echoed my thoughts. we need to actively use cvs/update it constantly as changes are made. i run a project called xcomic that uses sourceforge's cvs a lot, so i have some experience with that. in addition, i recently set something up for my project that i think will be pretty cool if wikka decides to really use cvs: a commit mailing list. anytime someone makes a change to the cvs (modification, addition, or deletion), an automatically generated email will be sent to anyone on the suscribers list detailing the files changed and the areas changed (a diff). in any case, version 1.1.6.0-beta4 should be committed and access should be given to a few main developers. then smaller contributors (like me) can send code changes to the main developers who subsequently commit. --mikexstudios
          • amp;mike, i for one would welcome your insights in using cvs. both dartar and i have some ideas about how we want it set up - but no experience in doing so (in cvs). may i suggest you join our developers mailing list? for this type of thing i think that would be the best medium to discuss thoughs and methods. i like the idea of a commit mailing list. --javawoman


list of special actions?

a complete reference list of all the special actions (e.g. """", ""The following 30 page(s) belong to SuggestionBox

AdminDevelopmentDiscussions [AdminDevelopmentDiscussions]
AdminDevTodo [AdminDevTodo]
AdminWatchList [AdminWatchList]
AdminWikkaWebsite [AdminWikkaWebsite]
AndreasTengicki [AndreasTengicki]
AutomaticUserPageCreation [AutomaticUserPageCreation]
CyneBeald [CyneBeald]
EditHandler [EditHandler]
HtmlSpecialChars [HtmlSpecialChars]
NonWikiUserNames [NonWikiUserNames]
OneYearOld [OneYearOld]
RyeBread [RyeBread]
SpanishLanguage [SpanishLanguage]
SpreadTheWord [SpreadTheWord]
SuggestionsArchive [SuggestionsArchive]
SupportingWikka [SupportingWikka]
TemplateSystem [TemplateSystem]
TestHomePage [TestHomePage]
TestHomePage1 [TestHomePage1]
TestHomePage2 [TestHomePage2]
TestHomePage3 [TestHomePage3]
TestHomePage4 [TestHomePage4]
UnOr [UnOr]
URUniqueEMailModule [URUniqueEMailModule]
WelcomeRegisteredUser [WelcomeRegisteredUser]
WelcomeRegisteredUserFR [WelcomeRegisteredUserFR]
WikkaBugsResolved [WikkaBugsResolved]
WikkaDevelopment [WikkaDevelopment]
WikkaDevelopmentFR [WikkaDevelopmentFR]
WikkaSpamFighting [WikkaSpamFighting]
"", etc.) would be really nice. --movielady

  • amp;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
    • amp;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

allow spaces in the document title and replace it later with "-" to optimize it for search engines.