Ok, I'll add this. It should be easy. Just a line or two... We already have a $BOLTdefaultExclude that can be set in a config file, but we need a $BOLTdefaultSearchType.
Also, it may be advisable to make these config options, so they can be set in site.config. Cheers, Dan P.S. Next release. On Tue, May 12, 2009 at 10:23 AM, DrunkenMonk <[email protected]> wrote: > > Is there anyone who uses search and does not want to exclude headers, > footers, and any eventual tops and sides 99% of the time? > > I've been making some fancy pages in my wiki, trying to give my > theatre group clean, well designed pages to organise our work during > the year, and I find that 5-10% of my code is search functions > requiring the darn "type=-header,footer,top,side", of which there are > currently on average two in any given group. > > This would not have been possible, by the way, if not for the timely > change to the include function, which happened just before I needed to > use it. Well done Dan! (I chain 'side' pages such that the most > relevant table of contents is highest, and then include the parent > side at the bottom. Works really well.) > > I suggest that "type=-header,footer,top,side" is made the default > behaviour of search, or that a site configuration option for default > values is implemented: > > defaultSearchType: > > Which can be set to empty, initially, so that newly installed wikis > don't have 'strange' behaviour, but is easy to modify once you realise > that you never want to return a header,footer,side or top page in a > search, ever. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
