urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

response

master
Joey Hess 2010-05-04 16:46:18 -04:00
parent 59ff5cf553
commit ddd7a766e2
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/forum/suppressing_output_of_pages_included_only_for_their_side_effects.mdwn
View File

@ -3,3 +3,14 @@ In particular, it's kind of annoying that using the sidebar plugin results in th
In reading through the code and associated docs, it appears that the ideal method is for the file to be removed from the $changed array by plugin's "needsbuild" hook. Either the sidebar plugin could define such a hook, or perhaps a more general solution is the creation of a meta variable or config file regexp that would handle it according to the user's wishes. In reading through the code and associated docs, it appears that the ideal method is for the file to be removed from the $changed array by plugin's "needsbuild" hook. Either the sidebar plugin could define such a hook, or perhaps a more general solution is the creation of a meta variable or config file regexp that would handle it according to the user's wishes.
I'm about ready to code up such a change but want to find out if I'm thinking along the right lines. --[[blipvert]] I'm about ready to code up such a change but want to find out if I'm thinking along the right lines. --[[blipvert]]
> Internal pages should be able to be used for this, as they are used for
> comments. So you'd have
> `sidebar._mdwn`. However, mwdn would need to be changed to register a
> htmlize hook for the `_mdwn` extension for that to really work.
>
> But, if there's no rendered sidebar page, how can users easily edit the page
> in the web interface? In the specific case of the sidebar, It seems
> better to have the page display something different when built standalone
> than when built as the sidebar.
> --[[Joey]]