X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/4aae0841e5f1ad7ef26ef8f0ede5dca0b2ac6a24..a5f3c2e1d163d915fcd88b0e74e8958519733204:/doc/index/discussion.mdwn?ds=sidebyside diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index f70040abc..e86d08ffb 100644 --- a/doc/index/discussion.mdwn +++ b/doc/index/discussion.mdwn @@ -188,40 +188,71 @@ Moved to [[bugs]] -- [[Joey]] ---- -# Textile Plugin +# Access Keys -It was trivial, but I put together a plugin that uses the Textile markup -language, which I find to be the most superior of the various options for -that sort of thing. Where or how do I submit it for inclusion? +Would anyone else find this a valuable addition. In oddmuse and instiki (the only other +wiki engines I am currently using, the edit, home, and submit link tags have an +accesskey attribute. I find it nice not to have to resort to the mouse for those +actions. However, it may not be something everyone appreciates. Any thoughts? +--[Mazirian](http://mazirian.com) -> You can post it to [[plugins/contrib]]. --[[Joey]] +> Maybe, although it would need to take the critisism at +> http://www.cs.tut.fi/~jkorpela/forms/accesskey.html into account. ->> Thanks. I tried using the "Add new post" form there, but apparently made a [mess of things somehow](http://ikiwiki.kitenet.net/contrib/textile___40__third-party_plugin__41__.html). Sorry about that. +>> Thank you for that link. Given that the edit link is the first thing you tab to +>> in the current layout, I guess it isn't all that necessary. I have had a +>> a user complaint recently that Alt-e in oddmuse was overriding his access +>> to the browser menu. ->>> No problem, the contrib form had the wrong rootpage setting. I've fixed ->>> it up and moved it to the right place. A copyright statement would be ->>> nice. +---- -> How does one go about making a markup language added by means of a plugin, the default markup language. In other words, I would like the index page to be written in Textile. -> If I include a index.txtl (where txtl is the extension I have assigned to be handled by the textile plugin), ikiwiki will ignore it and make a new index.mdwn. +# Editing the style sheet. ->> Sounds like a bug; it should be configurable via `default_pageext`, but ->> I suspect that currently if there are two competing files with different ->> extensions that make the same page, they fight it out and some random ->> one "wins" ->> ->> Until I fix that, you can avoid the one from the underlay directory by ->> setting `underlaydir` to point to an empty directory. --[[Joey]] ->> ->> Ok, fixed (in svn), it will now prefer files in the srcdir over files ->> in the underlaydir that build the same page, no matter what extension. +It would be nice to be able to edit the stylesheet by means of the cgi. Or is this possible? I wasn't able to achieve it. +Ok, that's my last 2 cents for a while. --[Mazirian](http://mazirian.com) ->>> Thanks, Joey, much appreciated. --[Mazirian](http://mazirian.com) +> I don't support editing it, but if/when ikiwiki gets file upload support, +> it'll be possible to upload a style sheet. (If .css is in the allowed +> extensions list.. no idea how safe that would be, a style sheet is +> probably a great place to put XSS attacks and evil javascript that would +> be filtered out of any regular page in ikiwiki). --[[Joey]] -# Access Keys +>> I hadn't thought of that at all. It's a common feature and one I've +>> relied on safely, because the wikis I am maintaining at the moment +>> are all private and restricted to trusted users. Given that the whole +>> point of ikiwiki is to be able to access and edit via the shell as +>> well as the web, I suppose the features doesn't add a lot. By the +>> way, the w3m mode is brilliant. I haven't tried it yet, but the idea +>> is great. -Would anyone else find this a valuable addition. In oddmuse and instiki (the only other -wiki engines I am currently using, the edit, home, and submit link tags have an -accesskey attribute. I find it nice not to have to resort to the mouse for those -actions. However, it may not be something everyone appreciates. Any thoughts? ---[Mazirian](http://mazirian.com) \ No newline at end of file +---- + +# Disable build/install requirement on PerlMagick + +Some installs of PerlMagick require X11. I tried to first disable using "img" by using "--disable-plugin img" +in the Makefile. But still failed. My workaround was to remove "img" from the bundle in IkiWiki/Plugin/goodstuff.pm +before building. What is the recommended way to install ikiwiki without "img" support? --[[JeremyReed]] + +> I've fixed this in svn so plugins in goodstuff can be disabled. --[[Joey]] + +---- + +# Documentation for banning users? + +The [[todo]] page says admins can ban users. Where is this documented? I search the source and found +set\_banned\_users() which led me to the CGI "preferences" form for the admin. Now logged in as an admin (as defined in my setup configuration), +I see the field for this. But no details on how to use it. From the source it appears to be a space-delimited list of usernames. (I didn't test yet.) + +Can you please provide a [[banned_users]] documentation about "banning" users function linked from the [[Features]] page and maybe [[security]] page and linked from the "preferences" for the admin? +(I don't do this myself as I am unsure about this and still reading the code about banning users.) + +---- + +# Documentation for locking pages? + +The [[features]] page, the [[todo]] page and the [[usage]] manual page say pages can be locked and only the admin can edit locked pages. +Where is locking pages documented? ... A moment later, from searching source I found this is configured via the preferences for the admin +and that links to [[pagespec]]. + +Can you please provide a [[page_locking]] doc about locking pages linked from the [[features]] page and elsewhere? And have that link to [[pagespec]]? +(I don't do this myself as I am unsure about this and still reading the code about locking pages.)