From d44733d3bd80d4c5dd8cf60b7107a0004c5c3fa8 Mon Sep 17 00:00:00 2001 From: "http://jmtd.livejournal.com/" Date: Sun, 22 Aug 2010 09:42:20 +0000 Subject: no need for rebuild --- doc/todo/edit_form:_no_fixed_size_for_textarea.mdwn | 2 ++ 1 file changed, 2 insertions(+) (limited to 'doc') diff --git a/doc/todo/edit_form:_no_fixed_size_for_textarea.mdwn b/doc/todo/edit_form:_no_fixed_size_for_textarea.mdwn index 577c3dad8..8721277aa 100644 --- a/doc/todo/edit_form:_no_fixed_size_for_textarea.mdwn +++ b/doc/todo/edit_form:_no_fixed_size_for_textarea.mdwn @@ -40,3 +40,5 @@ browsers emulate it. [[done]] --[[Joey]] Wouldn't it be possible to just implement an integer-valued setting for this, accessible via the "Setup" wiki page? This would require a wiki regen, but such a setting would not be changed frequently I suppose. Also, Mediawiki has this implemented as a per-user setting (two settings, actually, -- number of rows and columns of the edit area); such a per-user setting would be the best possible implementation, but I'm not sure if ikiwiki already supports per-user settings. Please consider implementing this as the current 20 rows is a great PITA for any non-trivial page. + +> I don't think it would need a wiki rebuild, as the textarea is generated dynamically by the CGI when you perform a CGI action, and (as far as I know) is not cooked into any static content. -- [[Jon]] -- cgit v1.2.3 From ff73f44f88e294fc4b9d0cb0396457537fd4a7aa Mon Sep 17 00:00:00 2001 From: "http://thewordnerd.info/" Date: Sun, 22 Aug 2010 17:42:13 +0000 Subject: --- doc/forum/Can__39__t_get_comments_plugin_working.mdwn | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/forum/Can__39__t_get_comments_plugin_working.mdwn (limited to 'doc') diff --git a/doc/forum/Can__39__t_get_comments_plugin_working.mdwn b/doc/forum/Can__39__t_get_comments_plugin_working.mdwn new file mode 100644 index 000000000..06b7fdd84 --- /dev/null +++ b/doc/forum/Can__39__t_get_comments_plugin_working.mdwn @@ -0,0 +1,7 @@ +I feel like I must be missing something. + +My blog is based on Ikiwiki, and uses /yyyy/mm/dd/title/ for blog posts. Because I use the plugin that generates index pages for subdirectories, I have to use /????/??/??/* to identify posts and avoid missing the index pages for years, months and days. + +I've enabled the comments plugin, but no matter what I do, I can't seem to make the comment form appear on my posts. I've removed the entire site and have rebuilt. I've set the pagespec to /????/??/??/* and ./????/??/??/*, but neither seems to work. I don't see any output, or anything else to indicate that pages aren't working. + +Are there any other plugins that need to be enabled for this to work? I think I've locked things down such that anonymous users can't edit by enabling signinedit and setting a lock, but this may be blocking the ability to comment (though I don't recall seeing anything in the docs about needing additional plugins.) -- cgit v1.2.3 From 5de07f59be82aeb7b4935fc134e023628eddb49c Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnbe6oB_ecFtNYII1JN3zSggwUPUdOb8jI" Date: Mon, 23 Aug 2010 03:08:01 +0000 Subject: report hard coded paths. --- doc/bugs/Highlight_extension_uses_hard_coded_paths.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/bugs/Highlight_extension_uses_hard_coded_paths.mdwn (limited to 'doc') diff --git a/doc/bugs/Highlight_extension_uses_hard_coded_paths.mdwn b/doc/bugs/Highlight_extension_uses_hard_coded_paths.mdwn new file mode 100644 index 000000000..1b9cb2e2d --- /dev/null +++ b/doc/bugs/Highlight_extension_uses_hard_coded_paths.mdwn @@ -0,0 +1 @@ +The [[plugins/highlight]] plugin hard codes some paths up the top of the plugin. This means that you need to edit the ikiwiki source if you have highlight installed in a non-standard location (e.g. if you have done a user-level install of the highlight package). -- cgit v1.2.3