diff options
Diffstat (limited to 'doc/bugs/HTML_is_not_update_nor_created_when_editing_markdown_via_CGI.mdwn')
| -rw-r--r-- | doc/bugs/HTML_is_not_update_nor_created_when_editing_markdown_via_CGI.mdwn | 13 |
1 files changed, 12 insertions, 1 deletions
diff --git a/doc/bugs/HTML_is_not_update_nor_created_when_editing_markdown_via_CGI.mdwn b/doc/bugs/HTML_is_not_update_nor_created_when_editing_markdown_via_CGI.mdwn index e95166518..b1a63361e 100644 --- a/doc/bugs/HTML_is_not_update_nor_created_when_editing_markdown_via_CGI.mdwn +++ b/doc/bugs/HTML_is_not_update_nor_created_when_editing_markdown_via_CGI.mdwn @@ -5,4 +5,15 @@ so when have new page it has a "?Page". (So CGI is working that much.) I edit (" How to get that file generated automatically on save (via edit)? -If this is documented, sorry I missed it.
\ No newline at end of file +If this is documented, sorry I missed it. + +> If a revision control system is configured, ikiwiki relies on a hook +> being triggered by its commit to the RCS, which then runs ikiwiki again +> to do the build, same as happens when a commit is made to the RCS +> directly. If the appropriate hook is not uncommented and configured in +> the setup file, you could see the behavior you describe. +> +> If no revision control system is used, ikiwiki handles the build after +> writing the file. +> +> --[[Joey]] |