X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/e47a2829893f7e458752abc5b02c6edd4f2621c9..65fce725b54b44e7a05b5cbc207d22f226fe5b47:/doc/todo/Moving_Pages.mdwn?ds=inline

diff --git a/doc/todo/Moving_Pages.mdwn b/doc/todo/Moving_Pages.mdwn
index 1952840db..62dda204a 100644
--- a/doc/todo/Moving_Pages.mdwn
+++ b/doc/todo/Moving_Pages.mdwn
@@ -18,10 +18,21 @@ I see the need for:
 
 * a new type of file to represent a forwarding page
 * a rename tool that can
-* * move the existing page to the new name
-* * optionally drop a forwarding page
-* * optionally rewrite incoming links to the new location
-
-(hrm, side note, does markdown not support nested bulleted lists?)
-
-Brad
\ No newline at end of file
+  * move the existing page to the new name
+  * optionally drop a forwarding page
+  * optionally rewrite incoming links to the new location
+
+Brad
+
+> This could be implemented through the use of an HTTP redirect to the 
+> new page, but this has the downside that people may not know they're being 
+> redirected.
+>
+> This could also be implemented using a combination of raw inline and meta
+> to change the title (add a "redirected from etc." page. This could be done
+> with a plugin. A redirect page would be [[redirect page="newpage"]].
+> But then if you click "edit" on this redirect page, you won't be able
+> to edit the new page, only the call to redirect.
+> --Ethan
+
+Note that there is a partial implementation in the [[patchqueoe|patchqueue/move_page]].