From: Reini U. <ru...@x-...> - 2004-02-17 12:07:26
|
Micki Kaufman schrieb: > Reini also mentioned 'IncludeSiteMap'. > > The IncludeSiteMap plugin (which was a homegrown plugin for 1.3.4 that > Cuthbert/DevNull Cat and I whipped up) allows you to use the same > functionality as the 'SiteMap' plugin (a recursive, fwd/backward, > indented 'BackLinks'), but to return each page's contents instead of the > list of page names. Works great for my users, being able to generate > 'Books' of pages for various CategoryWikiBadges, etc. Best of all, the > 'transclusion-title' can be set to trigger a 'chapter' in a printed .pdf > file, allowing you to have full joy between wiki and printable pdf > structures like bookmarks and tables of contents. > > The plugin was crafted by Cuthbert Cat about a year ago, and I've sent > Reini a copy for his analysis. To be honest, I've kept our install at > 1.3.4 awaiting this plugin's consideration and would love to see this > functionality added to the phpwiki code base. > > Also, Cuthbert - if you read the lists, can you give your 4 cents about > IncludeSiteMap? I added IncludeSiteMap support to SiteMap on which its based on, to avoid code duplication. You can see it, when you look at the CVS version of SiteMap. (attached) The current problem is very simple and is now solved as in InterWikiSearch or PluginManager. Warning! The default usage of IncludeSiteMap would recursively include the WHOLE content of all your PhpWiki pages in one big page. That may result in a MEGA html output. Just to make that clear. Personally I don't buy that idea. Maybe we should avoid the recursive nature (which is in fact IncludePage with multiple pages) or at least limit the recursion depth (reclimit) to 1 or 2. Well, I defined now the following default arguments to IncludeSiteMap: 'includepages' => 'words=50' 'reclimit' => 2, The 'includepages' argument will be passed verbatim to IncludePage. Direct usage of 'includepages' within SiteMap is forbidden, only from the child class IncludeSiteMap. BTW: jeff, I had to fix almost all plugins, because a new basepage argument for ->run() was not defined and silently dropped. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |