1 Thanks for that one, again, it's great!
3 One minor thing I noticed, seen on <http://www.bddebian.com/~wiki/recent_changes/>:
4 The links to user pages of e.g. *MichaelBanck* or *GianlucaGuida* don't work, as they're
5 being linked to <http://www.bddebian.com/~wiki/user/MichaelBanck>, whereas it should be
6 <http://www.bddebian.com/~wiki/user/michaelbanck>.
8 > I've fixed this.. --[[Joey]]
10 Another one. If you change the *recentchangespage* configuration option, (it seems to me)
11 that the pages from the old hierarchy will not be removed from the disk. But then, changing
12 this should be a rather uncommon thing.
16 > And fixed this, by making it look at all *._change pages, not just
17 > those in a specific directory, when deciding which to expire. --[[Joey]]
19 I've just upgraded to ikiwiki 2.50 with the `recentchanges` plugin enabled, and
20 figured out that I have to turn on `rss` in `ikiwiki.setup` in order to get the
21 recentchanges feed. Now the feed shows up, but the links in the feed go to the
22 change pages, e.g. `recentchanges/change_1700.html`. I can see a `recentchanges`
23 directory created in the working copy, containing files like `change_1700._change`
24 but for some reason they are not getting htmlized and carried over. I can see
25 in `recentchanges.pm` that it explicitly registers an `htmlize` hook for the
26 `_change` type, but something isn't happening. I also see `return if $type=~/^_/;` in
27 `render()` in `Render.pm` so I guess the upshot is I'm not sure how this is
28 supposed to work; is there a bug here or just something I overlooked that I need
29 to turn on? --Chapman Flack
31 > It's a (minor) bug that recentchanges optimises away generating the
32 > change pages, but that the rss/atom feed still links to them. --[[Joey]]