foo

[git.ikiwiki.info.git] / doc / bugs.mdwn

diff --git a/doc/bugs.mdwn b/doc/bugs.mdwn
index 8fa6e1aff7193eaf6fe7a8bad06227aeb494f467..3bcd1998ad14d648fb60fe71269e1c0ccad4c576 100644 (file)
--- a/doc/bugs.mdwn
+++ b/doc/bugs.mdwn
@@ -2,10 +2,11 @@
   adding/removing a page. For example, if Foo/Bar links to "Baz", which is
   Foo/Baz, and Foo/Bar/Baz gets added, it will update the links in Foo/Bar
   to point to it, but will forget to update the linkbacks in Foo/Baz.
   adding/removing a page. For example, if Foo/Bar links to "Baz", which is
   Foo/Baz, and Foo/Bar/Baz gets added, it will update the links in Foo/Bar
   to point to it, but will forget to update the linkbacks in Foo/Baz.

-  And if Foo/Bar/Baz is then removed, it forgets to update Foo/Bar to link
+  
+* And if Foo/Bar/Baz is then removed, it forgets to update Foo/Bar to link

   back to Foo/Baz.
 
   back to Foo/Baz.
 

-    -- is this still true?
+    -- is this still true? (Yes (as of 1.0))

 
 * If I try to do a web commit, to a svn+ssh repo, it fails with
   "Host key verification failed."
 
 * If I try to do a web commit, to a svn+ssh repo, it fails with
   "Host key verification failed."


@@ -14,19 +15,20 @@
   EUID/Real UID screwage.
 * Can't put the source in a directory named .source; the page finder skips
   that due to too broad exclusion of any dotfile in a path.
   EUID/Real UID screwage.
 * Can't put the source in a directory named .source; the page finder skips
   that due to too broad exclusion of any dotfile in a path.

-* RecentChanges is a regular page, perhaps it should be automatically
-  replaced with a link to the [[CGI]]?

 * [[ikiwiki]] should go to the same place as [[index]] (on this wiki).
 * Web browsers don't word-wrap lines in submitted text, which makes editing a
   page that someone wrote in a web browser annoying (`gqip` is vim user's
   friend here). Is there any way to improve this?
 * The diff links in RecentChanges go to a viewcvs backtrace if the rev in question is when the page was added. Is this a viewcvs bug, or a behavior ikiwiki needs to work around?
 * [[ikiwiki]] should go to the same place as [[index]] (on this wiki).
 * Web browsers don't word-wrap lines in submitted text, which makes editing a
   page that someone wrote in a web browser annoying (`gqip` is vim user's
   friend here). Is there any way to improve this?
 * The diff links in RecentChanges go to a viewcvs backtrace if the rev in question is when the page was added. Is this a viewcvs bug, or a behavior ikiwiki needs to work around?

+    - As a special case, there should certianly be no history link for
+      pages generated from the underlaydir as it can never work for them.

 * If a page stops inlining anthing, its rss feed file
   will linger around and not be deleted.
 * If a page stops inlining anthing, its rss feed file
   will linger around and not be deleted.

-* Currently only one blog is supported per page. Attempts to add more
-  will make it only update one of the blogs on the page.
-* If I edit blog/entry/blog_moved, add a link to code/ikiwiki, and hit
-  preview, it doesn't get the link right because it makes it relative to
-  where the page will be saved to, not to where the cgi script is.

 * RSS output contains relative links. Ie. http://kitenet.net/~joey/blog/index.rss contains a link to http://kitenet.net/~joey/blog/../blog.html
 * RSS output contains relative links. Ie. http://kitenet.net/~joey/blog/index.rss contains a link to http://kitenet.net/~joey/blog/../blog.html

-* \[\[inline archive="yes\]\] creates an RSS link, but no feed.
\ No newline at end of file
+* If a file in the srcdir is removed, exposing a file in the underlaydir,
+  ikiwiki will not notice the change and rebuild it until the file in the
+  underlaydir gets a mtime newer than the mtime the removed file had.
+* ikiwiki will generate html formatted error messages to the command
+  line if --cgi is set, even if it's not yet running as a cgi
+* The meta plugin doesn't affect a page if it's being inlined. Probably
+  setting the title with it should override the title of the blog post.