DokuWiki

It's better when it's simple

User Tools

Site Tools


plugin:indexmenu:discussion

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
plugin:indexmenu:discussion [2015-02-15 12:55] 91.20.122.190plugin:indexmenu:discussion [2021-04-12 16:12] – [nojs: How make all namespaces always switching open/close by clicking?] garrettlynch
Line 144: Line 144:
 >– Juan Mejias 2013/03/05 >– Juan Mejias 2013/03/05
  
 +I've just updated from the old version 4.6 to the current 5.0. With version 4.6 pages and namespaces are mixed, with the new they are separated. I found https://github.com/samuelet/indexmenu/pull/111 which re-implement the old behavior. But it is still not merged into the source on github. Will his happen soon?
 +--- //[[rene.fertig-bonacker@versatel.de|René Fertig-Bonacker]] 2016/06/29 13:39//
  
 ===== <navigation> tag from indexmenu2 ===== ===== <navigation> tag from indexmenu2 =====
Line 217: Line 219:
 >>> This way you also loose the names.. I managed this by changing this line ''($item['hns']) ? $out .= ",'".idfilter($item['hns'], false)."'" : $out .= ",0";'' to ''$out .= ",0";'' in ''syntax/indexmenu.php'' (line 548), thats for javascript menu.. it would be nice to introduce some extra tag I could put into my page like ''nolink'' which would tell the menu to take only the name from heading and not the link.. this would be really appreciated.. [[petr.zoufaly@gmail.com|Petr]] //2015/01/12 19:45// >>> This way you also loose the names.. I managed this by changing this line ''($item['hns']) ? $out .= ",'".idfilter($item['hns'], false)."'" : $out .= ",0";'' to ''$out .= ",0";'' in ''syntax/indexmenu.php'' (line 548), thats for javascript menu.. it would be nice to introduce some extra tag I could put into my page like ''nolink'' which would tell the menu to take only the name from heading and not the link.. this would be really appreciated.. [[petr.zoufaly@gmail.com|Petr]] //2015/01/12 19:45//
  
 +> In indexmenu.php change line 820 to <code>$tagid = "indexmenu_idx_head indexmenu_idx";</code> to allow opening and closing with a start page set.
 +> //[[richard@nospam.com|Richard Ginzburg]] 2015-08-07 11:20//
  
 +>> Sadly this (changing /syntax/indexmenu.php) does not work for me on DokuWiki 2017 Frusterick
 +>> But I did manage to add a new "+" button after the headpage link to toggle the namespace open/close. ☞ [[https://github.com/samuelet/indexmenu/pull/181|my pull request]] --- [[user>MilchFlasche|MilchFlasche]] //2017-10-31 04:00//
 +
 +>>>Changing line 820 of /syntax/indexmenu.php to <code>$tagid = "indexmenu_idx_head indexmenu_idx";</code>
 +>>>does not work as mentioned above. Instead comment out line 815 <code>$more  = '';</code>
 +>>>and namespaces with headpages will open as required. Why this isn't the default setting I'm unclear 
 +>>>but agree with Petr above that it would be very easy to implement as a 'nolink' tag.
 ===== How to clean up dead links?! ===== ===== How to clean up dead links?! =====
 As I've got described in the DokuWiki Forum http://forum.dokuwiki.org/post/17408 I have dead links in the Indexmenu after I moved a page. Is there a way to clean up that entries? As I've got described in the DokuWiki Forum http://forum.dokuwiki.org/post/17408 I have dead links in the Indexmenu after I moved a page. Is there a way to clean up that entries?
Line 249: Line 260:
 > When you apply the sorting options, these firstly apply to pages. When you add ''nsort'' these sorting will be applied to the namespaces too. > When you apply the sorting options, these firstly apply to pages. When you add ''nsort'' these sorting will be applied to the namespaces too.
  
 +>>but how do you give that custom sorting number to a namespace which doesnt have a page? Am I missing something?
 ===== Permanent cookies? ===== ===== Permanent cookies? =====
  
Line 285: Line 296:
 Is it possible to add option for match only files or namepsaces with regexp. So the options could be (for example) ''matchfile[+|=]/regexp/'' and ''matchns[+|=]/regexp/'' and the plugin will only display files or namespace that respects the regular expression. Thanks. Is it possible to add option for match only files or namepsaces with regexp. So the options could be (for example) ''matchfile[+|=]/regexp/'' and ''matchns[+|=]/regexp/'' and the plugin will only display files or namespace that respects the regular expression. Thanks.
  
 +> +1
 +> The only reason I am still using [[:plugin:nspages]] plugin is its support for //inclusion// filter
 +> --- [[user>marcink|marcink]] //2016-02-18 21:11//
 ===== Showing tree and ACL ===== ===== Showing tree and ACL =====
 Is it possible to show all the tree (namespaces/directories) in the menu when the only subnamespace is allowed in ACL? Currently the nothing is shown. Is it possible to show all the tree (namespaces/directories) in the menu when the only subnamespace is allowed in ACL? Currently the nothing is shown.
Line 365: Line 379:
   * I also don't understand what the first number (m) and second one (n) are   * I also don't understand what the first number (m) and second one (n) are
  
-Sorry for my dumb questions. I'm really gratefull for this plugin, but I also really have problems with some description.+Sorry for my dumb questions. I'm really grateful for this plugin, but I also really have problems with some description.
  
 ===== Letters Color ===== ===== Letters Color =====
Line 371: Line 385:
   * The letters of the Main Page are in red color  and the sub pages are in blue color.   * The letters of the Main Page are in red color  and the sub pages are in blue color.
   * But some new Main Pages are now in blue. What is the reason for that?   * But some new Main Pages are now in blue. What is the reason for that?
 +
 +
 +===== Hide Categories/Namespaces based on ACL =====
 +
 +In a wiki with n number of categories (for example c1, c2, c3)and  where most users only have read access to one of those categories; Is it possible to hide the namespaces in the tree structure that the user does not have read access to  based on the ACLs?
 +
 +The default situation seems to be that all the users who have read access to root see all the namespaces but not the individual pages inside those categories. I don't see any point in seeing namespaces that you don't have access to. 
 +
 +===== Inconsistency w/ core sneaky_index behaviour =====
 +
 +It appears that the plugin is still displaying the name of namespaces that the logged-in user does not have access to.  This, as I understand it, is the purpose of sneaky_index.  Better behaviour would be to exclude these namespaces from the index when sneaky_index is on.
 +
 +Please refer to doku documentation for sneaky_index: 
 +https://www.dokuwiki.org/config:sneaky_index
 +
 +===== Hide root =====
 +
 +IMHO displaying the root node of the indexmenu tree is a waste of precious screen real estate. Is it possible to hide it?
 +
 +  Software User Manual
 +  |
 +  |- 1.0 Installation
 +  |- 2.0 Configuration 
 +  |  |-2.1 Global Configuration
 +  |  |-2.2 User Configuration
 +  |  |-2.3 Exporting/Importing Configurations
 +  |-3.0 Uninstalling
 +
 +change to
 +<code>
 +- 1.0 Installation
 +- 2.0 Configuration 
 +  |-2.1 Global Configuration
 +  |-2.2 User Configuration
 +  |-2.3 Exporting/Importing Configurations
 +-3.0 Uninstalling
 +</code>
 +
 +===== Could You add Images to the index? =====
 +
 +I would like to have a consistent display for my images files and folders. Could this be a future feature?
 +
 +
 +
plugin/indexmenu/discussion.txt · Last modified: 2021-09-29 20:06 by GogglesPisano

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki