From ecb2626309754d3bb8fb7fdb59126169db92026a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 2 Sep 2008 13:40:46 -0400 Subject: rename --- doc/todo/Easier_disabling_action_URLs.mdwn | 35 ------------------------------ doc/todo/page_edit_disable.mdwn | 35 ++++++++++++++++++++++++++++++ 2 files changed, 35 insertions(+), 35 deletions(-) delete mode 100644 doc/todo/Easier_disabling_action_URLs.mdwn create mode 100644 doc/todo/page_edit_disable.mdwn diff --git a/doc/todo/Easier_disabling_action_URLs.mdwn b/doc/todo/Easier_disabling_action_URLs.mdwn deleted file mode 100644 index 578c394a2..000000000 --- a/doc/todo/Easier_disabling_action_URLs.mdwn +++ /dev/null @@ -1,35 +0,0 @@ -Disabling some of action URLs is not possible now without creating own -version of `templates/page.tmpl` file. For example, how to disable -displaying `EDITURL`, `RECENTCHANGESURL` or `PREFSURL` without -touching original `page.tmpl` template? - -Now I can only enable/disable `HISTORYURL` and `DISCUSSIONLINK`. -It's not hard for me, but I think that the way to do it can be -confusing for another Ikiwiki users. For example, if I don't -want `HISTORYURL`, then I need to comment `historyurl` hash -in setup file. But if I want to disable discussions, then I need -to set `discussion=0` there. So, you can see that we don't have -one common method here. - -Maybe Ikiwiki setup file should has more hashes for action URLs, -for example `edit=[01]`, `recentchanges=[01]`, `prefs=[01]` -and `history=[01]`? - -If you are curious why I need that features, I can clarify it. -I'm building "parallel" version of my site. It means that I want -to have one editable version for internal users and second only -readable version (+ search feature) for external users. I build -both versions on secure, internal machine from the same pages, -of course, and separated setup files and different templates. -The readable version of the site will be rsynced to clustered WWW -front-ends immediately via `post-commit` hook file or periodically -by Cron. I haven't decided how to do it yet. --[[Paweł|ptecza]] - -> You disable display of recentchanges by disabling that plugin. -> You disable edit and preferences by not enabling a cgiurl at all. -> -> Maybe page editing will become a plugin some day, or be made -> configurable -- there are a few things like searching and websetup -> (and possibly the poll plugin, aggregate webtrigger, and pingee) -> that it may make sense to enable a cgi for even if you don't want to -> allow page editing. --[[Joey]] diff --git a/doc/todo/page_edit_disable.mdwn b/doc/todo/page_edit_disable.mdwn new file mode 100644 index 000000000..578c394a2 --- /dev/null +++ b/doc/todo/page_edit_disable.mdwn @@ -0,0 +1,35 @@ +Disabling some of action URLs is not possible now without creating own +version of `templates/page.tmpl` file. For example, how to disable +displaying `EDITURL`, `RECENTCHANGESURL` or `PREFSURL` without +touching original `page.tmpl` template? + +Now I can only enable/disable `HISTORYURL` and `DISCUSSIONLINK`. +It's not hard for me, but I think that the way to do it can be +confusing for another Ikiwiki users. For example, if I don't +want `HISTORYURL`, then I need to comment `historyurl` hash +in setup file. But if I want to disable discussions, then I need +to set `discussion=0` there. So, you can see that we don't have +one common method here. + +Maybe Ikiwiki setup file should has more hashes for action URLs, +for example `edit=[01]`, `recentchanges=[01]`, `prefs=[01]` +and `history=[01]`? + +If you are curious why I need that features, I can clarify it. +I'm building "parallel" version of my site. It means that I want +to have one editable version for internal users and second only +readable version (+ search feature) for external users. I build +both versions on secure, internal machine from the same pages, +of course, and separated setup files and different templates. +The readable version of the site will be rsynced to clustered WWW +front-ends immediately via `post-commit` hook file or periodically +by Cron. I haven't decided how to do it yet. --[[Paweł|ptecza]] + +> You disable display of recentchanges by disabling that plugin. +> You disable edit and preferences by not enabling a cgiurl at all. +> +> Maybe page editing will become a plugin some day, or be made +> configurable -- there are a few things like searching and websetup +> (and possibly the poll plugin, aggregate webtrigger, and pingee) +> that it may make sense to enable a cgi for even if you don't want to +> allow page editing. --[[Joey]] -- cgit v1.2.3