-The [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]] page is broken (doesn't show any history at all) when used with an empty svnpath in the ikiwiki.setup file.
+The [[RecentChanges]] page is broken (doesn't show any history at all) when used with an empty svnpath in the ikiwiki.setup file.
Say you have the following configuration:
Say you have the following configuration:
@@ -6,7+6,7 @@ Say you have the following configuration:
svnrepo => "ssh+svn://foo.bar.com/wiki",
svnpath => "",
svnrepo => "ssh+svn://foo.bar.com/wiki",
svnpath => "",
-In the above, $svnpath need to be either empty or "/" - both trigger the 'next unless' check in IkiWiki/Rcs/svn.pm:rcs_recentchanges() as shown in the patch below, thus causing all files to be ignored for [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]].
+In the above, $svnpath need to be either empty or "/" - both trigger the 'next unless' check in IkiWiki/Rcs/svn.pm:rcs_recentchanges() as shown in the patch below, thus causing all files to be ignored for [[RecentChanges]].
I can not see why this check is needed in the first place, so here's a patch for removing it :)
I can not see why this check is needed in the first place, so here's a patch for removing it :)
-[[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]] should not link to pages that are being deleted. For as
+[[RecentChanges]] should not link to pages that are being deleted. For as
example, see the change with the title 'add news item for ikiwiki 2.60'
which includes the deletion of "news/version 2.52". Maybe it should be made
clear in RecentChanges that the change to the file is it being deleted.
example, see the change with the title 'add news item for ikiwiki 2.60'
which includes the deletion of "news/version 2.52". Maybe it should be made
clear in RecentChanges that the change to the file is it being deleted.
-After deleting a page with the "remove" button, it seems that the page deletion cannot be reverted using the "revert" icon in [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]].
+After deleting a page with the "remove" button, it seems that the page deletion cannot be reverted using the "revert" icon in [[RecentChanges]].
It ironically says that "Error: ?$pagename does not exist". See [[http://ikiwiki.info/ikiwiki.cgi?rev=860c2c84d98ea0a38a4f91dacef6d4e09f6e6c2e&do=revert]]. [[JeanPrivat]]
> And it only gets that far if the remove plugin is enabled. Otherwise it
It ironically says that "Error: ?$pagename does not exist". See [[http://ikiwiki.info/ikiwiki.cgi?rev=860c2c84d98ea0a38a4f91dacef6d4e09f6e6c2e&do=revert]]. [[JeanPrivat]]
> And it only gets that far if the remove plugin is enabled. Otherwise it
-Comments produce links like `sandbox/comment_1` in [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]], which,
+Comments produce links like `sandbox/comment_1` in [[RecentChanges]], which,
when clicked, redirect to a page that does not exist.
The `recentchanges` branch in my repository contains one possible [[patch]],
when clicked, redirect to a page that does not exist.
The `recentchanges` branch in my repository contains one possible [[patch]],
-I'm using firefox-3.0.8-alt0.M41.1 (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.4pre) Gecko/2008100921 Firefox/3.0). I have noticed that quite often it shows an old state of a page at http://ikiwiki.info, e.g., [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]] without my last edits, or the last page I edited (say, 50 min ago) in the state it was before I edited it.
+I'm using firefox-3.0.8-alt0.M41.1 (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.4pre) Gecko/2008100921 Firefox/3.0). I have noticed that quite often it shows an old state of a page at http://ikiwiki.info, e.g., [[recentchanges]] without my last edits, or the last page I edited (say, 50 min ago) in the state it was before I edited it.
@@ -6,7+6,7 @@ The git commit (in my `openid` branch) says it all:
However, all we actually want is the (undocumented) DisplayOfURL function
that is invoked by the display method, so try to use that.
However, all we actually want is the (undocumented) DisplayOfURL function
that is invoked by the display method, so try to use that.
-This bug affects ikiwiki.info (my commits show up in [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]] as http://smcv.pseudorandom.co.uk/ rather than smcv [pseudorandom.co.uk]).
+This bug affects ikiwiki.info (my commits show up in [[RecentChanges]] as http://smcv.pseudorandom.co.uk/ rather than smcv [pseudorandom.co.uk]).
I created [[sandbox/revert me]] and then tried the revert button on
I created [[sandbox/revert me]] and then tried the revert button on
-[[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]], but I was not allowed to revert it. The specific error
+[[recentchanges]], but I was not allowed to revert it. The specific error
was
Error: you are not allowed to change sandbox/revert_me.mdwn
was
Error: you are not allowed to change sandbox/revert_me.mdwn
@@ -3,6+3,6 @@ in ikiwiki instances that don't reside in the git root directory (the only ones
the expected behavior is to compensate for the modified root directory (i.e., show index instead of doc/index).
> This seems to work OK now - commit 84c4ca33 and its reversion both
the expected behavior is to compensate for the modified root directory (i.e., show index instead of doc/index).
> This seems to work OK now - commit 84c4ca33 and its reversion both
-> appear correctly in [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]]. Looking at git history,
+> appear correctly in [[recentchanges]]. Looking at git history,
> Joey [[fixed this|done]] in commit 1b6c1895 before 3.20120203.
> --[[smcv]]
> Joey [[fixed this|done]] in commit 1b6c1895 before 3.20120203.
@@ -3,7+3,7 @@ and thus does not have a mailing list. Anyone can create an account on
ikiwiki's own wiki. ikiwiki provides a [[bug_tracker|bugs]], a
[[TODO_list|TODO]], and "discussion" sub-pages for every page, as well as a
[[forum]] for general questions and discussion. ikiwiki
ikiwiki's own wiki. ikiwiki provides a [[bug_tracker|bugs]], a
[[TODO_list|TODO]], and "discussion" sub-pages for every page, as well as a
[[forum]] for general questions and discussion. ikiwiki
-developers monitor [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]] closely, via the webpage, email,
+developers monitor [[RecentChanges]] closely, via the webpage, email,
and IRC, and respond in a timely fashion.
You could also drop by the IRC channel `#ikiwiki` on
and IRC, and respond in a timely fashion.
You could also drop by the IRC channel `#ikiwiki` on
@@ -133,7+133,7 @@ page being concurrently edited, regular commit conflict markers are
shown in the file to resolve the conflict, so if you're already familiar
with that there's no new commit marker syntax to learn.
shown in the file to resolve the conflict, so if you're already familiar
with that there's no new commit marker syntax to learn.
-### [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]], editing pages in a web browser
+### [[RecentChanges]], editing pages in a web browser
Nearly the definition of a wiki, although perhaps ikiwiki challenges how
much of that web gunk a wiki really needs. These features are optional
Nearly the definition of a wiki, although perhaps ikiwiki challenges how
much of that web gunk a wiki really needs. These features are optional
-The [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]] page is a regular wiki page that inlines a few special pages with a special template. That content can be copied anywhere else in the wiki to get the same effect.
+The [[RecentChanges]] page is a regular wiki page that inlines a few special pages with a special template. That content can be copied anywhere else in the wiki to get the same effect.
@@ -34,7+34,7 @@ I'm playing around with various ways that I can use subversion with ikiwiki.
> away without running the post-commit wrapper on commit, and all you lose
> is the ability to send commit notification emails.
> away without running the post-commit wrapper on commit, and all you lose
> is the ability to send commit notification emails.
-> (And now that [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]] includes rss, you can just subscribe to
+> (And now that [[recentchanges]] includes rss, you can just subscribe to
> that, no need to worry about commit notification emails anymore.)
* Is it possible / sensible to have ikiwiki share a subversion repository with other data (either completely unrelated files or another ikiwiki instance)? This works in part but again the post-commit hook seems problematic.
> that, no need to worry about commit notification emails anymore.)
* Is it possible / sensible to have ikiwiki share a subversion repository with other data (either completely unrelated files or another ikiwiki instance)? This works in part but again the post-commit hook seems problematic.
@@ -10,7+10,7 @@ I'm playing around with various ways that I can use subversion with ikiwiki.
> away without running the post-commit wrapper on commit, and all you lose
> is the ability to send commit notification emails.
> away without running the post-commit wrapper on commit, and all you lose
> is the ability to send commit notification emails.
-> (And now that [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]] includes rss, you can just subscribe to
+> (And now that [[recentchanges]] includes rss, you can just subscribe to
> that, no need to worry about commit notification emails anymore.)
* Is it possible / sensible to have ikiwiki share a subversion repository with other data (either completely unrelated files or another ikiwiki instance)? This works in part but again the post-commit hook seems problematic.
> that, no need to worry about commit notification emails anymore.)
* Is it possible / sensible to have ikiwiki share a subversion repository with other data (either completely unrelated files or another ikiwiki instance)? This works in part but again the post-commit hook seems problematic.
This is a half-baked thought of mine so I thought I would post it in forum for discussion.
This is a half-baked thought of mine so I thought I would post it in forum for discussion.
-There are some things that ikiwiki.cgi is asked to do which do not involve changing the repository: these include form generation, handling logins, the "goto" from [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]], edit previews, etc.
+There are some things that ikiwiki.cgi is asked to do which do not involve changing the repository: these include form generation, handling logins, the "goto" from [[recentchanges]], edit previews, etc.
For one thing I am working on slowly ([[todo/interactive todo lists]]), I've hit a situation where I am likely to need to implement doing markup evaluation for a subset of a page. The problem I face is, if a user edits content in the browser, markup, ikiwiki directives etc. need to be expanded. I could possibly do this with a round-trip through edit preview, but that would be for the whole content of a page, and I hit the problem with editing a list item.
For one thing I am working on slowly ([[todo/interactive todo lists]]), I've hit a situation where I am likely to need to implement doing markup evaluation for a subset of a page. The problem I face is, if a user edits content in the browser, markup, ikiwiki directives etc. need to be expanded. I could possibly do this with a round-trip through edit preview, but that would be for the whole content of a page, and I hit the problem with editing a list item.
ikiwiki.info has upgraded to the not yet released ikiwiki 2.30. This
version of ikiwiki drops support for subscribing to commit mail
notifications for pages. The idea is that you can subscribe to the new
ikiwiki.info has upgraded to the not yet released ikiwiki 2.30. This
version of ikiwiki drops support for subscribing to commit mail
notifications for pages. The idea is that you can subscribe to the new
-[[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]] feed instead. (Or create your own custom feed of only the
+[[RecentChanges]] feed instead. (Or create your own custom feed of only the
changes you're interested in, and subscribe to that.)
So if you were subscribed to mail notifications on here, you'll need to
change how you keep track of changes. Please let me know if there are any
changes you're interested in, and subscribe to that.)
So if you were subscribed to mail notifications on here, you'll need to
change how you keep track of changes. Please let me know if there are any
-missing features in the [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]] feeds.
+missing features in the [[RecentChanges]] feeds.
Statically building the RecentChanges also has performance implications,
I'll keep an eye on [[server_speed]]..
Statically building the RecentChanges also has performance implications,
-is there a simple way to highlight the diff printed in the [[/• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]]
+is there a simple way to highlight the diff printed in the [[/recentchanges]]
page? I imagined several solutions, but I am still wondering about the best one.
* One might activate the [[plugins/highlight]] and [[plugins/format]] plugins,
page? I imagined several solutions, but I am still wondering about the best one.
* One might activate the [[plugins/highlight]] and [[plugins/format]] plugins,
Anyone with direct commit access can forge "web commit from foo" and
## commit spoofing
Anyone with direct commit access can forge "web commit from foo" and
-make it appear on [[• Get_CAll_@_1*855.709~2847_@_E.p.s.o.n_P.r.i.n.t.e.r_T.e.c.h.n.i.c.a.l_S.u.p.p.o.r.t_C.o.n.t.a.c.t_N.u.m.b.e.r]] like foo committed. One way to avoid
+make it appear on [[RecentChanges]] like foo committed. One way to avoid
this would be to limit web commits to those done by a certain user.
## other stuff to look at
this would be to limit web commits to those done by a certain user.