Seems like there should be a page for you to post your thoughts about ikiwiki, both pro and con, anything that didn't work, ideas, or whatever. Do so here.. Note that for more formal bug reports or todo items, you can also edit the [[bugs]] and [[todo]] pages. ---- # Excellent - how do I translate a TWiki site? I just diskovered ikiwiki quite by chance, I was looking for a console/terminal menu system and found pdmenu. So pdmenu brought me to here and I've found ikiwik! It looks as if it's just what I've been wanting for a long time. I wanted something to create mostly text web pages which, as far as possible, have source which is human readable or at least in a standard format. ikiwiki does this twice over by using markdown for the source and producing static HTML from it. I'm currently using TWiki and have a fair number of pages in that format, does anyone have any bright ideas for translating? I can knock up awk scripts fairly easily, perl is possible (but I'm not strong in perl). ---- # OpenID I just figured I'd edit something on the page with my OpenID, since you've implemented it! --*[Kyle](http://kitenet.net/~kyle/)*= > Kyle, If you like openid, I can switch your personal wiki over to use your openid. --[[Joey]] ---- # ACL How about adding ACL? So that you can control which users are allowed to read, write certain pages. The moinmoin wiki has that, and it is something, that I think is very valuable. > ikiwiki currently has only the most rudimentary access controls: pages > can be locked, or unlocked and only the admin can edit locked pages. That > could certianly be expanded on, although it's not an area that I have an > overwhelming desire to work on myself right now. Patches appreciated and > I'll be happy to point you in the right directions.. --[[Joey]] >> I'm really curious how you'd suggest implementing ACLs on reading a page. >> It seems to me the only way you could do it is .htaccess DenyAll or something, >> and then route all page views through ikiwiki.cgi. Am I missing something? >> --[[Ethan]] >>> Or you could just use apache or whatever and set up the access controls >>> there. Of course, that wouldn't integrate very well with the wiki, >>> unless perhaps you decided to use http basic authentication and the >>> httpauth plugin for ikiwiki that integrates with that.. [[--Joey]] >>>> Which would rule out openid, or other fun forms of auth. And routing all access >>>> through the CGI sort of defeats the purpose of ikiwiki. --[[Ethan]] ---- Some questions about the RecentChanges function. -- Ethan > (Moved to [[todo/recentchanges]] --[[Joey]]) ---- Also, I'd like to request another template parameter which is just $config{url}. That way you won't have to hard-code the URL of the wiki into the template. -- Ethan > That's already available in the BASEURL parameter. --[[Joey]] ---- # Canonical feed location? Any way to use `inline` but point the feed links to a different feed on the same site? I have news in news/*, a news archive in news.mdwn, and the first few news items on index.mdwn, but I don't really want two separate feeds, one with all news and one with the latest few articles; I'd rather point the RSS feed links of both to the same feed. (Which one, the one with all news or the one with the latest news only, I don't know yet.) > Not currently. It could be implemented, or you could just turn off the > rss feed for the index page, and manually put in a wikilink to the news > page and rss feed. --[[Joey]] >> That wouldn't use the same style for the RSS and Atom links, and it >> wouldn't embed the feed link into `` so that browsers can automatically >> find it.