Differences

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

--- plugin:navilevel [2012-11-26 10:18] – [Installation] 85.74.41.225
+++ plugin:navilevel [2018-06-04 23:36] (current) – Klap-in
@@ Line 1: / Line 1: @@
-====== navilevel plugin ======
+====== navilevel Plugin ======
 ---- plugin ----
@@ Line 67: / Line 67: @@
 Note that, there was a change from version #4 on how this works.
-Release version 2007-06-14 also has a new feature. If the page that calls the plugin (or the "main" page if it is called from a sidebar page) is named 'sitemap', all nodes will expand. You can see this in action at [[http://www.kapagroup.gr/sitemap]] and I even use it as my ''link rel="contents"''.
+Release version 2007-06-14 also has a new feature. If the page that calls the plugin (or the "main" page if it is called from a sidebar page) is named 'sitemap', all nodes will expand. You can see this in action at [[http://www.acsys1.gr/sitemap]] and I even use it as my ''link rel="contents"''.
 ==== Issues with older releases ====
@@ Line 242: / Line 242: @@
 ===== Installation =====
-Use the [[plugin:plugin|plugin manager]] to download it from:
+Search and install the plugin using the [[plugin:extension|Extension Manager]]. Refer to [[:Plugins]] on how to install plugins manually.
   * [[http://www.acsys.gr/_media/plugins/navilevel/navilevel.tgz]]
@@ Line 590: / Line 590: @@
+====== Multilingual content ======
+With a slight modification, navilevel can become aware of a multilingual environment. The way it works in this case is demonstrated in [[http://www.acsys.gr/]]. The code for that is not included in the version of navilevel presented in this page in order to keep things simple. However, if someone is interested in it, please drop me an e-mail.
 ====== Discussion ======
@@ Line 631: / Line 632: @@
-Actually, this is close to how this plugin works. I include the relevant code in the sidebar page (I'm obviously using a template with a sidebar) and the navigation tree adapts to the current page. The example site I mention above, demonstrates just that. However, I like the approach of the [[plugin:navi|navi]] plugin where, unlikely navilevel, you can define a site structure independent of the actual namespace structure. Besides, it is actively developed (not to mention who the author is).
+Actually, this is close to how this plugin works. I include the relevant code in the sidebar page (I'm obviously using a template with a sidebar) and the navigation tree adapts to the current page. The example site I mention above, demonstrates just that. However, I like the approach of the [[plugin:navi|navi]] plugin where, unlikely navilevel, you can define a site structure independent of the actual namespace structure. Besides, it is actively developed.
  --- //[[thanos.massias@gmail.com|Thanos Massias]] 2009/05/14 19:33//
@@ Line 638: / Line 639: @@
  --- //[[hella.breitkopf@gmail.com|Hella Breitkopf]] 2012-02-15//
+Actually this plugin still works. I'm now using it with “Adora Belle”. BTW, there are some cool things you can do with it by creatively using the 'some_text_before' and 'some_text_after' fields (which can include HTML) that make it irreplaceable for me. The silliest trick was including a <blink>«</blink> marker for a menu item I wanted highlighted. I also added descriptive text after the links, properly positioned with <br /> and even modified the plugin a bit to have some list items permanently expanded.
+ --- //[[thanos.massias@gmail.com|Thanos Massias]] 2013/03/15 10:17//