\n"; //Making sure the cookies are used// 288 $out .= "document.write(".$js_name.");\n"; 289 //level 1 closes the tree | 290 //if ($level==1) $extra =$js_name.".closeAll();\n"; 291 //no opened levels | 292 //if (empty($extra)) $extra=$js_name.".openAll();\n"; 293 $out .= $extra; Regarding, the #[n] syntax, I was initially expecting it to be used to limit the size of the tree being used. If you have a big wiki, with a lot of pages, it might become too heavy. And that would enable us to control the size of the index... --- //[[frbaron@gmail.com|Franck Baron]] 2006-07-21 11:43// Thank you very much for pointing this out - it's very useful modification! --- //[[alex@facile-it.de|Alexander Behringer]] 2006-08-18 14:01// > Thanks to you, I hope it's done. The id#page options makes the work. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2006-09-11 00:47// >I've searched a way to implement a limit size option, but it needs the rewriting of a core function. The result will be an easier lost of indexmenu functionality in case of DokuWiki upgrade, so I prefer don't implement it, at least till core function will have by its own. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2006-10-07 21:09// --- Thank you for this excellent plugin. I've needed to skip some namespaces (discussion, wiki, playground, etc) from the index and made small patch: --- syntax.php.orig 2006-07-18 16:02:35.000000000 +0400 +++ syntax.php 2006-07-18 16:01:34.000000000 +0400 @@ -281,6 +281,12 @@ $id = pathID($file); + // check files/folders to skip + if (isset($conf['plugin_indexmenu']) && isset($conf['plugin_indexmenu']['skip_index']) && + preg_match($conf['plugin_indexmenu']['skip_index'], $file)) + return false; + + //check hiddens if($type=='f' && isHiddenPage($id)){ return false; Together with new plugin option $conf['plugin_indexmenu']['skip_index']="/\/(discussion|wiki|playground)(\.\w+)?$/i"; it do the job. Hope, you'll find it useful. --- //[[ilya@lebedev.net|Ilya Lebedev AKA WingedFox]] 2006-06-24 02:23// >Oh, Thanks ilya. I 'll add code in next indexmenu version ;). --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2006-07-19 22:33// >> Samuele, have you received the email I sent you from ilya[at]lebedev[dot]net? If not, send me blank email, plz. --- //[[ilya@lebedev.net|Ilya Lebedev AKA WingedFox]] 2006-08-01 13:23// Another small extension to the skip_index for directories: skip_files. (skip_index doesn't seem to skip files.) So I added the following to syntax.php... if($type == 'd'){ // Folders to skip if (isset($conf['plugin_indexmenu']['skip_index']) && preg_match($conf['plugin_indexmenu']['skip_index'], $file)) return false; if ($opts['level'] == $lvl) $return=false; if ($opts['nons']) return $return; } elseif ($type == 'f' && !preg_match('#\.txt$#',$file)){ //don't add return false; + // Next clause to skip node files + } elseif ( $type == 'f' + && isset($conf['plugin_indexmenu']['skip_file']) + && preg_match($conf['plugin_indexmenu']['skip_file'], $file) + ) { + return false; } Then something like this in local.php filters out files... $conf['plugin_indexmenu']['skip_file']="/(copyright|navigation|talk|site_notice)/i"; //[[jnews@jonbuckingham.me.uk|Jon B]] 2006-09-21 18:14// >Patch added. Thanks --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2006-10-07 20:55// ===== Include section titles ===== Hi Samuele and all! Is there a way to include section titles in an index. So next level after a page would be its sections. Thanks! Blaz >Hi, I'm sorry but currently the plugin does not support this. And I've no idea how I could implement it (for instance, if the next level of a page is its sections, what level should I put lower page in?). Could you make a visual sample? --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2007-01-14 11:30// >> Hm, actually pages are usually on the lowest level, aren't they? Anyway, it would work like this: if this option was set in conf.man., the pages would still have the page icon, with a '+' in front of it. That would enable you to expand it as a 'folder' to show sections. I'm not sure it is a reasonable feature, maybe somebody else has an opinion? Regards, [[bmertelj@yahoo.com|Blaž]] 18.1.2007 9:02 > I'm implementing something that in the [[..:indexmenu#development]] release. You can test it on my site. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2007-05-19 12:25// ===== Sort Option ===== Hi, I am using the indexmenu plugin along with the sidebar template to great effect. The only draw back is that the although I am using page headers as names, the sort order is still based on file/folder name which can be a little confusing to users. It would be very nice to have to option to sort by page title instead of filename; this is especially useful for those in my situation where a namespace might start off with one foldername, but need to be "renamed" to be more descriptive - and to allow group next to other similar namespaces in the menu. Thanks > Good idea, but unfortunately it's harder than it could seem. I'll look for a solution in next 3.1 version. >Another option is also to offer a sort option based on some kind of page meta data. The fullindex plugin attempts to do this with an "identifier" key that you can use to assign a pagenumber to each page/namespace root, and then sort the index based on this. This idea is heaps powerful and useful, but does not appear to have caught on elsewhere. Either way, the fullindex plugin only replaces the "idx" DokuWiki command, and does not apply to any inserted menus. Any chance that something like this could be integrated into indexmenu? --Ryan >> Ummm, let sort pages by a metada number could be useful, I'll look for an implementation. The main problem with sorting in indexmenu is that i've not yet find a way to sort namespaces in a "cheap way", so for the moment I prefer don't sort them. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2007-07-25 09:53// >>> Thanks for the info! Please allow me to expand on this thread a bit, perhaps just to help emphasize the importance of sorting options in an index plugin. The person that started this thread/feature-request was right-on when mentioning the importance of being able to re-order the items in an index, this is especially important for documentation projects (which DokuWiki is targeting). As documentation develops, sections/namespaces get inserted and moved often, and I see a key need reflect this in the index. A user can sort by filename and use names like 010_preference, 020_section_x, etc., and this leaves room to add sections while maintaining the order, but what about when a section must be moved (especially if it's a namespace)? The tsort option really helps, and if it were possible to apply it to sort namespaces too (currently not available), the whole index order could be maintained by simply using outline numbering in the first heading of all pages (totally dynamic). I mentioned the metadata idea above because, IMHO, this seems like the ultimate method to sort by... a totally dynamic and "invisible" method to maintain indexes that must follow a specific order. Thanks! Just wanted to share my ideas as I explore DokuWiki and all these fantastic plugins! --- //[[ryan.jake@gmail.com|Ryan Jacobs]]// >>>> Okay, sort by metadata (and date creation) is implemented and it'll be out next week as 3.9 release, after some cosmetic changes. Still no namespace sorting, only pages sorting. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2007-08-26 10:53// >>>>> Thanks Samuele! I look forward to checking it out (sort options and new scrolling, etc.). Please keep us informed on any namespace sorting options, etc (if that's still a priority in your eyes too). Thanks again! --- //[[ryan.jake@gmail.com|Ryan Jacobs]]// >>>>>> Ok. I hope for the next release. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2007-08-30 21:33// >>>>>> It's implemented in the [[..:indexmenu#development]] release (this a [[http://samuele.netsons.org/dokuwiki/media/indexmenu-4.0beta.zip|link]] to its last zip, but at the moment the web site is down). Namespaces are sorted according to msort and (d|c)sort options, but I'm thinking to add another option for them. I need heavy testing before release it. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2007-09-28 11:05// ===== Don't show pages ===== I would like to show only the ns in the menu. I use it as a sidebar and if there are too many pages in a ns it is not well arranged. Is there any possibility like the "nons" syntax to create a "nopage" syntax? This means: Exclude single pages from index. It shows only the namespaces. --- //[[fgmelle@osnanet.de|Sebastian E]] 2008-07-31 12:26// >Not currently. But before thinking to implement it, I'd like to understand what you exactly mean with "not well arranged", just because I don't like workarounds if a problem can be solved directly. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2008/07/31 13:00// >>I have the same idea as Sebastian : I wish to let the index in the side bar with all nodes closed and root pages hidden two : it is not that they are "not well arranged", because they are alphabetically sorted, but that there are so many pages in root namespace that I can't insert my index anywhere 8-O --- //[[hugoborrell@gmail.com|NewMorning]] 2008/08/05 13:44// >>>I mean that if there are for example 100 pages in one ns they are all shown in the sidebar. I think it is sometimes better to show only the namespaces. To assure good overview. For all ns I could simply create a headpage to show them. --- //[[fgmelle@osnanet.de|Sebastian E]] 2008-08-06 13:09// >>I'm just starting with DokuWiki and navigation is my first hurdle; Our site will have many names spaces and some deep hierarchies. I too need a way just to display the top level name spaces, perhaps two levels down, but now pages. Then, just to add to the mix; my wish list would include a way to include navigation for all items in the namespace and below it in the default start page for any name space, even if such a start page had not been created. i.e. if someone makes a page like this ..:newNameSpace:coolIndexPlugIn... there is no start page created for the name space "newNameSpace" what would be really super would be to have the an indexmenu auto insert for the name space in a default start page. So, in the side bar they see only top level names spaces, no pages, but on any start page, the get the full navigation for that names space...this way someone can rapidly navigate across a very complex hierarchy of name spaces just by clicking on different points of the "trace" breadcrumbs or "Your are here" (I'm using monobook at the moment) Your are here root:kingdom:species:mammals:cats:simiens... use clicks on "species" and lands on a start page with an auto index for the whole species names space. Am I dreaming too much? :-) katir 2008/08/09 >>> Katir, take a look at the [[plugin:autosearch]] plugin. I never used it but from its description it should build a list of subpages using indexmenu when a page does not exists. Together with the below new "nopg" option you should get your goal. Please, let we know if this work. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2008/08/26 20:32// >>>I solved my problem in this way -> In the indexmenu.php go to the function handle(), there you have to insert in row 108 and 109 //plugin options $nons = in_array('nons',$opts); //nopages option $nopg = in_array('nopg',$opts); //disable toc preview On the same function on row 165 you have to insert 'js' => $js, 'nopg' => $nopg, 'skip_index' => $this->getConf('skip_index'), The last thing you have to do is in the function _search_index on line 445 //check hidden and ACL if (isHiddenPage($id) || auth_quickaclcheck($id) < AUTH_READ) return false; //Nopg.Dont show pages if ($opts['nopg']) return false; //Skip files in plugin conf Now you can use the syntax 'nopg'. Then every page (AND every NS without an headpage) is not shown any more. --- //[[fgmelle@osnanet.de|Sebastian E]] 2008-08-12 10:32// >> Thanks Sebastian. Your patch (with some modifications) is available in the [[..:indexmenu#development]] release. Please, report any bug or hint about it. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2008/08/23 12:58// ===== Namespaces as links themselves ===== Example: * 1 * 1.1 * 1.2 * 1.2.1 * 1.2.2 * 1.3 I would like that "1" be a page itself, as well as "1.2" Using Index Menu or DokuWiki's index I can see that the page is created under .. or under 1 in the example. > I'm not sure you mean this, but take a look at [[plugin:indexmenu#namespaces title and link]]. Enable also the hide headpage option. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2009/01/13 10:08// No is not that... Here I go again: \\ [[Cap06:softbase | **example here**]] \\ [[Cap06:softbase:man]] \\ [[Cap06:softbase:mes]] \\ [[Cap06:softaux]] \\ [[Cap06:softaux:man]] \\ [[Cap06:softaux:mes]] \\ [[Cap06:web]] \\ [[Cap06:web:mes]] \\ [[Cap06:web:web]] \\ But in the index when I click on **example here** I see: cap06 softbase man mes softbase The page softbase is not save inside softbase namespace. The same thing with cap06, when I create this page it is saved in another level. If I have a lot of namespaces is going to be difficult for me to have a "pure" and correct index A possible solution could be adding an intro page inside every namespace so to introduce the whole namespace content I wouldn't use the "namespace itself". What do you think? > I suppose I still does not understand your request but I try again. First of all, with DokuWiki it's not possible to have a namespace which is also a page. To achieve this, indexmenu use the workaround to "link" a page to a namespace (i call this special page as "headpage"), but it works only inside the indexmenu context. Then it's up to you where to create the headpage, not to indexmenu. So, about your example, if you want create an "intro page" for **%%cap06:softbase%%**, create the **%%cap06:softbase:softbase%%** page then set indexmenu headpage option only with :inside: value, and set hide_headpage option on to hide that headpage from indexmenu tree. That headpage will be still visible in the DokuWiki standard index, but you could replace it with the indexmenu index as explained [[plugin:indexmenu#replace_index|here]]. >If I'm wrong in understand you, please continue this discussion via email. ===== Hide a namespace ===== I would like that in the main menu does not appear some namespaces (such as misc, various, etc...). But those namespaces should be available to edit. (Not [[http://www.dokuwiki.org/plugin:indexmenu?s[]=indexmenu#acl_cache|this]]) I mean, I have a namespace where I saved many editable pages.... But I do not want that people could see that in the indexmenu. It’s OK for me if they reach there only by any link in main pages. I want that people only reach those places if they > The [[plugin:indexmenu#skip_index]] option is what you need. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2009/01/23 23:16// ===== Newbie Missing Something Very Basic Here ===== The documentation frequently refers to statements such as %%"{{indexmenu>.#1 .:jack#1 .:june}}"%% which, if I'm reading this right, controls how each page will be eventually indexed depending in other things (??). My only problem on building on this which appears to be so basic is that I have absolutely no idea where to put this statement. Do I create an new page for it? Do I insert somewhere? The documentation appears to me to be very unclear on this. I'll also admit that as a DokuWiki newbie who is trying to get up to speed quickly the above notation is confusing as I don't see it reflected in page titles which are, I understand, supposed to be showing me from page on the right to top level namespace on the left. So I'm baffled by the .: notation as it is new to me and unexplained even on the namespace page of the manual where it also appears. I'm sure this is just a matter of misunderstanding the notation but until then I can't see myself getting further with this plugin. Thanks in advance John Wilson ttfnjohn@hotmail.com >You can insert indexmenu statement in every page you want. Anyway, I suggest you to carefully read the indexmenu syntax page to optimize it for your needs. There is also an indexmenu toolbar button in edit mode for easier use of it. In your example, the first "." notation means "display the tree of the namespace of the page which contains indexmenu statement" closed at "#1" level. So, don't expect that "." will dinamically display the tree of the namespace of the page that the user is displaying (there is the "context" option for this). The next statements refer to the jack and june as subnamespaces of the main namespace (the previous ".") and how to display them (closed or open) --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2009/03/19 10:14// >Thanks Samuele. I'll have another go at it and see how it goes. Sometimes we newbies do need to be pointed in the right direction and you've been kind in doing just that.!//[[john_wilson@telus.net|John Wilson]] 2009/03/19 08:20// ===== A question about the great right-click contextmenu ===== After experimenting with your marvelous plugin, I decided to use indexmenu as the primary way to add new topics and namespaces to my Wiki. This was easily accomplished using the right-click jsmenu scripts. I have a question though: * It seems that the top-level namespace (the page root) is considered by indexmenu to be a file not a directory. Therefore if for instance, one menu option in usrmenu.js is: **'Edit this page...','indexmenu_getid(this.config.urlbase,id)+"do=edit"',1,0,** then this option will wrongly be enabled when right-clicking on the top-level folder. Great work! //[[urban@ottosson.org|Urban]]// > If you think this is a bug, you should report it in the [[..:indexmenu#bugs]] section. > Does this bug persist in the [[..:indexmenu#development]] release too? If yes, could you report your indexmenu settings? --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2009/07/06 09:39// > If you root node is an headpage, than, in the context menu, page menu links will be displayed instead of namespace menu links. Try to disable or change this option in the indexmenu settings. ===== psort? ===== Is there a way to sort according to the page, similar to the nsort? Would be helpful if you can direct me to change the code for this. > All the indexmenu sort options, except for nsort, can be used to sort pages in different ways. ===== FAST nav bar ===== I'm found of this plugin for my sidebar, but my wiki gets pretty big and it seems that the amount of pages makes my navbar CPU consumming, resulting in a very slow result. How can I optimise the navbar options to make it as fast as possible ? I did try many options but probably not the way they should be : {{indexmenu>..#1|js1 navbar context max#1 maxjs#1}} Is that the best choice I can make to make it fast ? > In general it is the best choice, but i'd like to have more details to test it (is your site public?). > First of all i suppose that "js1" is a typo which stands for "js", then, when exactly does the cpu consuming occur (ie: always or when a namespace is opened and contains a lot of pages (how many?) ) ? > Supposing that nothing else prevents the page caching, does removing the "context" option change something? > Could you check if it's installed some other plugin which uses javascript and could interfers with indexmenu (i.e: try to disable all except indexmenu)? --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2009/10/04 21:10// >>well, the site is not public, you can just see first page [[http://wiki.survie.org/accueil|here]]. >>js1 refers to documentation : maybe I did not understand this line : | js | JavaScript render method: the index is an expandable tree menu. | Without n, all nodes are open, with it, nodes are open till n level. | >>Indeed the "context" option did not change anything. >>I did not try to remove the other plugins, since everything works fine on the whole whith this code : {{indexmenu>..#1|js navbar}} It's just that I'm looking for a way to diminish CPU constraint for my poor server :-\ >>When I check the source code of the page, I can see many lines relating to all the wiki pages like indexmenu_12108424764acb69809e3af.add('bulletin_de_veille:bdv_7',19,2,'BDV 7',0,0,0); This should only be loaded when asked (i.e.when clicking on the namespace in the index), and i whish it could not be seen if not connected (but it's said somewhere that it is slower, which is why this option is off). >>> Documentation says "js" not "js1" and it creates a javascript index theme (yellow folders and so on) instead of a standard dokuwiki index theme (like [[http://wiki.survie.org/accueil?do=index|this]]). >>> What's is not clear to me in your report is if the CPU load affects the client side (the user browser) or the server side (the server hosting your site). The first case can be checked also viewing the site with different pcs. The second case occurs (if it really occurs) only when page cache is purged (look in the indexmenu page for further details). Anyway for both cases, this syntax is the best for your site: {{indexmenu>..#1|js navbar max#1#1}} >>> With max#1#1, the "indexmenu_xxxxxx.add" lines should be less because nodes will be loaded when asked. >>> Just two observation: >>> At a first look, it seems that the [[..:indexmenu#acl_cache]] option in you site is set to none becasue when i viewed it, i saw the full index of your site (with denied pages). Then i purged it, and i got the correct limited index (without denied pages). This means that until cache is not purged while an authenticated user is logged in, your users will still view the limited index of the anonymous user. >>> The number of pages that i saw in the cached unlimited index seems not so high and i don't think that they can affect the CPU of your site or your browser, maybe the problem is a bug, a misconfiguration or something else. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2009/10/06 19:46// >>>>I suggest that documentation could be changed from "Without n, all nodes are open, with it, nodes are open till n" to "Without the max#n(#n) option, all nodes are open, with it, nodes are open till n". >>>>I tried {{indexmenu>..#1|js navbar max#1#1}} with ACL_cache set to true : it starts like you describe, with nodes not loaded until asked, but when I ask them to load, a red cross appears (as no pages where listed below this node, or as if access where denied in spite of my connection). I get to an existing page that I know of using the url, the red cross is not shown, the node shows a "-" sign (as if opened) but no page titles are shown below in the navbar index. >>>>I then disabeld ALL plugins but indexmenu : here is the list : Plugin aclinfo désactivé Plugin actionlink désactivé Plugin box désactivé Plugin cacherevisionserase désactivé Plugin censure désactivé Plugin cloud désactivé Plugin comment désactivé Plugin commentsrc désactivé Plugin dailymotion_videozap désactivé Plugin database2 désactivé Plugin dir désactivé Plugin displaywikipage désactivé Plugin feed désactivé Plugin force_preview désactivé Plugin goto désactivé Plugin importoldchangelog désactivé Plugin importoldindex désactivé Plugin indexmenu désactivé Plugin lib désactivé Plugin loginredirect désactivé Plugin mp3play désactivé Plugin multitemplate_styleman désactivé Plugin note désactivé Plugin orphanswanted désactivé Plugin pagelist désactivé Plugin pagemove désactivé Plugin pageredirect désactivé Plugin popularity désactivé Plugin redirect désactivé Plugin searchindex désactivé Plugin showlogin désactivé Plugin tag désactivé Plugin tagentry désactivé Plugin vshare désactivé Plugin youtube désactivé >>>>I then had to set back indexmenu and multitemplate_styleman to find back the usual template : it worked exacty as you described ! >>>>I set back all of them step by step and... it still worked exacty as you described ! >>>>**The only thing I had done in the meanwhile is clear an empty folder through ftp access (I don't know why Dokuwiki did not do it itself) and clear cache (refreshing a page with ?purge=true). This empty folder might have caused the previous strange behaviour since it remained the only node showing this behaviour (red cross) but for good reason (empty folder).** >>>>As for misconfiguration you're right : this site is not so big, but I should clean up some plugins + change host which has very low CPU (this is the CPU I want to spare). One more thing : there is a huge amount of pages hidden from index in an "article" namespace : they might cause part of the slow down. >>>>Thanks for everything (plugin+advices). --- //[[hugoborrell@gmail.com|NewMorning]] 2009/10/08 08:18// >>>>> You're a little confused about the syntax ^_^. Open/closed is related to the namespaces status (the +/- sign) and it depends on the main and secondary namespaces "n" option, whereas the max option is the way how to retrieved childs of closed namespaces. >>>>>If it's not an indexmenu bug (and i don't think so), the your issue with the red cross depends only on how you configured the [[plugin:indexmenu#acl cache]]. First of all, you have to know that it can be displayed when ns or pages are denied by ACL for the reasons explained in the [[plugin:indexmenu#about_empty_namespaces]] section. >>>>>Then, simply, if the indexmenu acl cache is not correctly configured ("true" is not a valid value for it), users could display cached indexmenu trees created for other users with different permissions. This is what probably happened to you until you disabled plugins, one of whose consequences is to purge the cache of all pages. >>>>>I suggest you to read carefully the [[plugin:indexmenu#acl cache]], [[plugin:indexmenu#about_acls]] and [[plugin:indexmenu#about_empty_namespaces]] sections, and if something is still not clear or does not work as described there, feel free to continue this discussion contacting me via email --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2009/10/08 15:52//. ===== How to get rid of the 'Indexmenu sort number' info blob? ===== I'm trying to use the ''msort'' feature of indexmenu and it is working as expected except for one side-effect: on any page where the ''{indexmenu_n}}'' option is defined I see a blue "Info" bar with something like "Indexmenu sort number: 2" at the top of the wiki page. The browser is Mozilla Firefox 2.0.0.12. The problem does not occur on IE 6. Also it doesn't appear on the latest version you've got installed on the test site. FYI I'm using DokuWiki version 2007-06-26b with Monobook 07202007 template. I've tried [en|dis]abling debugging using ''$conf['allowdebug'] = 0;'' to no avail. Any suggestions? --- SSMC Feb-18-2008 > Sorry, but I forgot to add its explanation in this wiki. The sort message is displayed **only** to wiki admins and it's useful to check your pages order. Anyway, you can disable it also for admins by unchecking the indexmenu show_sort option in the [[plugin:config|Configuration manager]]. --- //[[samuele@samuele.netsons.org|Samuele Tognini]] 2008-02-18 19:30// >> Thanks! That explains the on-again-off-again observations using different ids. I didn't make the connection though as I have some local browsers with auto-login as an admin for working. Thanks again. --- SSMC