Revision 1779
Added by Dietmar over 11 years ago
README.en.txt | ||
---|---|---|
1 | 1 |
show_menu2, version 4.9 |
2 | 2 |
======================= |
3 |
A code snippet for the Website Baker CMS software. It provides a complete
|
|
4 |
replacement for the builtin menu functions. All menu data is retrieved using
|
|
5 |
a single database query, all types of menu styles (lists, breadcrums, sitemaps)
|
|
3 |
A code snippet for the Website Baker CMS software. It provides a complete |
|
4 |
replacement for the builtin menu functions. All menu data is retrieved using |
|
5 |
a single database query, all types of menu styles (lists, breadcrums, sitemaps) |
|
6 | 6 |
can be generated with extensive customisation of the resulting HTML. |
7 | 7 |
|
8 | 8 |
|
... | ... | |
16 | 16 |
the "Uninstall Module" list and choose the "Uninstall" button. |
17 | 17 |
5. In the "Install Module" section, enter the path to the show_menu2 zip file |
18 | 18 |
that you downloaded in step 1, and choose the "Install" button. |
19 |
|
|
20 |
|
|
21 |
|
|
19 |
|
|
20 |
|
|
21 |
|
|
22 | 22 |
USING SHOW_MENU2 |
23 | 23 |
================ |
24 |
You need to modify the PHP files of your template to call show_menu2 where you
|
|
24 |
You need to modify the PHP files of your template to call show_menu2 where you |
|
25 | 25 |
wish to have the menu displayed. Remember when you replace calls to the old |
26 |
menu functions to use the new parameters that show_menu2 requires.
|
|
26 |
menu functions to use the new parameters that show_menu2 requires. |
|
27 | 27 |
|
28 | 28 |
Often times the default menu generated by show_menu2 is all that you need. |
29 | 29 |
This menu shows the current page and children of the current page. It is |
30 | 30 |
generated by just calling show_menu2 with no parameters. For example: |
31 | 31 |
|
32 | 32 |
show_menu2(); |
33 |
|
|
33 |
|
|
34 | 34 |
Note that the call to show_menu2 is PHP, so you usually need to wrap it in the |
35 | 35 |
PHP code brackets so that it will execute. Like this: |
36 | 36 |
|
... | ... | |
39 | 39 |
This default menu generates a complete list based menu with many classes that |
40 | 40 |
allow easy CSS styling. For example, the current menu item will have the |
41 | 41 |
"menu-current" class added to the <li> tag. Additionally, every menu item with |
42 |
a sub-menu will have the "menu-expand" class added to the <li> tag. This allows
|
|
42 |
a sub-menu will have the "menu-expand" class added to the <li> tag. This allows |
|
43 | 43 |
you to create CSS rules to style those menu items differently. For example: |
44 | 44 |
|
45 | 45 |
li.menu-expand { font-weight: bold; } |
46 | 46 |
li.menu-current { background: red; } |
47 | 47 |
|
48 |
See the "Output" section for details of exactly what classes are added to each
|
|
49 |
element. More elaborate and different menu structures are able to be created by
|
|
50 |
supplying different parameters to the show_menu2 function call. For example,
|
|
48 |
See the "Output" section for details of exactly what classes are added to each |
|
49 |
element. More elaborate and different menu structures are able to be created by |
|
50 |
supplying different parameters to the show_menu2 function call. For example, |
|
51 | 51 |
to show only menu items from the top level of the menu you use: |
52 | 52 |
|
53 | 53 |
show_menu2(0, SM2_ROOT, SM2_START); |
54 |
|
|
54 |
|
|
55 | 55 |
Alternatively, to show up to two levels of the child menus of the current page: |
56 | 56 |
|
57 | 57 |
show_menu2(0, SM2_CURR+1, SM2_CURR+2); |
58 | 58 |
|
59 | 59 |
There are many more possible menus that can be generated by show_menu2. See the |
60 |
demonstration website at http://code.jellycan.com/sm2test/ for more examples.
|
|
60 |
demonstration website at http://code.jellycan.com/sm2test/ for more examples. |
|
61 | 61 |
|
62 | 62 |
|
63 | 63 |
|
64 | 64 |
COMMON QUESTIONS |
65 | 65 |
================ |
66 | 66 |
|
67 |
Q: I'm not a programmer. Do you have simpler documentation?
|
|
67 |
Q: I'm not a programmer. Do you have simpler documentation? |
|
68 | 68 |
A: Nup. This is it. Go hard. Gambarre. |
69 | 69 |
|
70 | 70 |
|
71 | 71 |
Q: How do I create a drop-down menu? |
72 |
A: This is unrelated to show_menu2. You need to change the template CSS code
|
|
72 |
A: This is unrelated to show_menu2. You need to change the template CSS code |
|
73 | 73 |
to display the menu as a drop-down. Try the "allcss2" template from the WB |
74 |
addon repository. http://addons.websitebaker.org/pages/templates.php
|
|
74 |
addon repository. http://addons.websitebaker.org/ |
|
75 | 75 |
|
76 | 76 |
|
77 | 77 |
Q: Why does the menu disappear after I do a search on my multilingual WB site? |
78 | 78 |
A: You're missing some required lines in your template. |
79 | 79 |
|
80 |
1. Log into WB administration, and go to Settings -> Show advanced settings
|
|
81 |
-> Search Settings -> Header Code and add the following input field
|
|
82 |
after the <form> open tag:
|
|
80 |
1. Log into WB administration, and go to Settings -> Show advanced settings |
|
81 |
-> Search Settings -> Header Code and add the following input field |
|
82 |
after the <form> open tag: |
|
83 | 83 |
|
84 | 84 |
<input type="hidden" name="referrer" value="[REFERRER_ID]" /> |
85 | 85 |
|
86 | 86 |
|
87 |
2. In the index.php of your template, add the following input field
|
|
87 |
2. In the index.php of your template, add the following input field |
|
88 | 88 |
immediately following the search <form> open tag. |
89 | 89 |
|
90 | 90 |
<input type="hidden" name="referrer" value="<?php echo defined('REFERRER_ID')?REFERRER_ID:PAGE_ID;?>" /> |
91 | 91 |
|
92 | 92 |
|
93 | 93 |
Q: Multilingual? That sounds cool. How do I do that? |
94 |
A: http://help.websitebaker.org/pages/en/advanced-docu.php
|
|
94 |
A: http://www.websitebaker2.org/en/help/designer-guide/multilingual-websites.php
|
|
95 | 95 |
|
96 | 96 |
|
97 | 97 |
Q: SM2 is generating a warning every time the page is accessed: |
98 | 98 |
"show_menu2 error: $aOptions is invalid. No flags from group 1 supplied!" |
99 |
A: You are passing the wrong values to the function. Have a closer look at the
|
|
100 |
parameters that you are passing. See the PARAMETERS section below for the
|
|
99 |
A: You are passing the wrong values to the function. Have a closer look at the |
|
100 |
parameters that you are passing. See the PARAMETERS section below for the |
|
101 | 101 |
correct flag values to pass for the $aOptions parameter. |
102 | 102 |
|
103 | 103 |
|
104 | 104 |
Q: How do I use a different class/picture/color/widget for each entry in a menu? |
105 |
A: Use the [page_id] format string in the $aItemOpen string. Create a unique
|
|
105 |
A: Use the [page_id] format string in the $aItemOpen string. Create a unique |
|
106 | 106 |
class or id for each menu item, then reference that item in your CSS or Javascript |
107 | 107 |
to do whatever you want. |
108 |
|
|
108 |
|
|
109 | 109 |
To add a unique class for each menu item (or similar): |
110 |
|
|
110 |
|
|
111 | 111 |
"<li><a href="[url]" target="[target]" class="[class] p[page_id]">[menu_title]</a>" |
112 | 112 |
|
113 | 113 |
... creating menu items like ... |
114 |
|
|
114 |
|
|
115 | 115 |
<li><a href="/pages/foo/bar.php" target="_top" class="menu-top p45">Top Menu</a> |
116 | 116 |
|
117 | 117 |
Reference this in your CSS like: |
118 |
|
|
118 |
|
|
119 | 119 |
a.p45 { color: red; } |
120 |
|
|
120 |
|
|
121 | 121 |
To add a unique ID for each menu item (or similar): |
122 |
|
|
122 |
|
|
123 | 123 |
"<li><a id="p[page_id]" href="[url]" target="[target]" class="[class]">[menu_title]</a>" |
124 |
|
|
124 |
|
|
125 | 125 |
... creating menu items like ... |
126 |
|
|
126 |
|
|
127 | 127 |
<li><a id="p45" href="/pages/foo/bar.php" target="_top" class="menu-top">Top Menu</a> |
128 | 128 |
|
129 | 129 |
Reference this in your CSS like: |
130 |
|
|
130 |
|
|
131 | 131 |
a#p45 { color: red; } |
132 |
|
|
132 |
|
|
133 | 133 |
Note that the ID can only be used if that menu is generated and displayed one time |
134 |
only on the page (because HTML ID's must be unique within a page). |
|
135 |
|
|
134 |
only on the page (because HTML ID's must be unique within a page). |
|
136 | 135 |
|
137 | 136 |
|
137 |
|
|
138 | 138 |
FUNCTION |
139 | 139 |
======== |
140 | 140 |
|
... | ... | |
157 | 157 |
Ensure that you use each parameter correctly. Use the following rules: |
158 | 158 |
|
159 | 159 |
$aMenu will be 0 for most people. |
160 |
|
|
160 |
|
|
161 | 161 |
$aStart must be either a page ID or a value starting with "SM2_". |
162 |
|
|
162 |
|
|
163 | 163 |
$aMaxLevel must be only values that start with "SM2_". |
164 |
|
|
165 |
$aOptions must be only values that start with "SM2_" (unless you are
|
|
164 |
|
|
165 |
$aOptions must be only values that start with "SM2_" (unless you are |
|
166 | 166 |
in a very small minority of users). |
167 |
|
|
168 |
All other parameters are the HTML tag templates that will be
|
|
167 |
|
|
168 |
All other parameters are the HTML tag templates that will be |
|
169 | 169 |
output for menus and menu items. |
170 |
|
|
171 |
Note that every parameter from $aItemOpen can be supplied as false to get
|
|
170 |
|
|
171 |
Note that every parameter from $aItemOpen can be supplied as false to get |
|
172 | 172 |
the default value. |
173 | 173 |
|
174 | 174 |
|
175 | 175 |
|
176 | 176 |
HTML OUTPUT |
177 | 177 |
=========== |
178 |
The menu is output differently depending on what parameters have been
|
|
179 |
supplied to the function, however in general the following classes are used
|
|
178 |
The menu is output differently depending on what parameters have been |
|
179 |
supplied to the function, however in general the following classes are used |
|
180 | 180 |
for each menu. Note that items will have multiple classes when relevant. |
181 | 181 |
|
182 | 182 |
CLASS ATTACHED TO |
... | ... | |
192 | 192 |
|
193 | 193 |
The following classes are added only if SM2_NUMCLASS flag has been used. |
194 | 194 |
|
195 |
menu-N Every menu item. The N is replaced with the ABSOLUTE
|
|
196 |
menu depth of the item starting with 0. The root level
|
|
195 |
menu-N Every menu item. The N is replaced with the ABSOLUTE |
|
196 |
menu depth of the item starting with 0. The root level |
|
197 | 197 |
menu is always menu-0, the next level is menu-1, etc. |
198 |
menu-child-N Every sub-menu of the current page, the N is replaced
|
|
198 |
menu-child-N Every sub-menu of the current page, the N is replaced |
|
199 | 199 |
with the relative depth of the submenu starting at 0. |
200 | 200 |
|
201 | 201 |
|
... | ... | |
240 | 240 |
|
241 | 241 |
PARAMETERS |
242 | 242 |
========== |
243 |
$aMenu
|
|
244 |
Menu number to use. This is useful when you are using multiple menus.
|
|
245 |
Supplying a menu number of 0 will use the default menu for the current
|
|
243 |
$aMenu |
|
244 |
Menu number to use. This is useful when you are using multiple menus. |
|
245 |
Supplying a menu number of 0 will use the default menu for the current |
|
246 | 246 |
page. Supplying SM2_ALLMENU will return all menus in the system. |
247 | 247 |
|
248 |
$aStart
|
|
248 |
$aStart |
|
249 | 249 |
Specify where the menu generation should start from. This is most |
250 |
times the parent item of the menu to display. It must be one of the
|
|
250 |
times the parent item of the menu to display. It must be one of the |
|
251 | 251 |
following values: |
252 | 252 |
SM2_ROOT+N Start N levels down from the root. e.g. |
253 |
SM2_ROOT Starting at the root menu
|
|
253 |
SM2_ROOT Starting at the root menu |
|
254 | 254 |
SM2_ROOT+1 Start 1 level below the root |
255 | 255 |
SM2_ROOT+2 Start 2 levels below the root |
256 | 256 |
SM2_CURR+N Start N levels down from the current page level. e.g. |
... | ... | |
259 | 259 |
SM2_CURR+1 Starts 1 level down from the current |
260 | 260 |
page with the children menus. |
261 | 261 |
page_id Display using the specific page as the parent. All |
262 |
child menus of that page will be displayed. The
|
|
263 |
page_id can be found by editing the page in WB admin
|
|
264 |
interface. The page_id is included in the URL like:
|
|
262 |
child menus of that page will be displayed. The |
|
263 |
page_id can be found by editing the page in WB admin |
|
264 |
interface. The page_id is included in the URL like: |
|
265 | 265 |
http://SITE/admin/pages/modify.php?page_id=35 |
266 | 266 |
|
267 |
$aMaxLevel
|
|
267 |
$aMaxLevel |
|
268 | 268 |
Maximum menu level to display. Menus are displayed from the start |
269 | 269 |
level down to this level. |
270 | 270 |
SM2_ALL No limit, all levels are displayed |
271 |
SM2_CURR+N Always show to the current page + N levels.
|
|
271 |
SM2_CURR+N Always show to the current page + N levels. |
|
272 | 272 |
SM2_CURR Current (no children) |
273 | 273 |
SM2_CURR+3 All parents + current + 3 children |
274 | 274 |
SM2_START+N Always show from the starting level + N levels. The |
... | ... | |
276 | 276 |
what level the current page is. |
277 | 277 |
SM2_START Single level of menus from starting level |
278 | 278 |
SM2_START+1 Starting level and 1 level down |
279 |
SM2_MAX+N Show at most N levels from the starting level. Levels
|
|
279 |
SM2_MAX+N Show at most N levels from the starting level. Levels |
|
280 | 280 |
won't be shown if they are below the current level. |
281 | 281 |
SM2_MAX Starting level only (same as SM2_START) |
282 | 282 |
SM2_MAX+1 Maximum of starting level and 1 level. |
283 | 283 |
|
284 |
$aOptions
|
|
284 |
$aOptions |
|
285 | 285 |
Specify flags for different generation options for the menu. The flags |
286 | 286 |
may be combined together using bitwise OR (|). For example, to specify |
287 | 287 |
both TRIM and PRETTY you should use, (SM2_TRIM | SM2_PRETTY). |
288 | 288 |
|
289 | 289 |
GROUP 1 |
290 | 290 |
------- |
291 |
Exactly one flag from this group must always be supplied. These flags
|
|
292 |
affect how the siblings in the tree are removed from the output.
|
|
291 |
Exactly one flag from this group must always be supplied. These flags |
|
292 |
affect how the siblings in the tree are removed from the output. |
|
293 | 293 |
|
294 | 294 |
SM2_ALL Show all branches of the menu tree |
295 |
A-1 -> B-1
|
|
295 |
A-1 -> B-1 |
|
296 | 296 |
-> B-2 -> C-1 |
297 | 297 |
-> C-2 (CURRENT) |
298 | 298 |
-> D-1 |
... | ... | |
300 | 300 |
-> C-3 |
301 | 301 |
A-2 -> B-3 |
302 | 302 |
-> B-4 |
303 |
SM2_TRIM Show all sibling menus of pages on the current path.
|
|
304 |
All sub-menus of elements that are not on the path
|
|
303 |
SM2_TRIM Show all sibling menus of pages on the current path. |
|
304 |
All sub-menus of elements that are not on the path |
|
305 | 305 |
are removed. |
306 |
A-1 -> B-1
|
|
306 |
A-1 -> B-1 |
|
307 | 307 |
-> B-2 -> C-1 |
308 | 308 |
-> C-2 (CURRENT) |
309 | 309 |
-> D-1 |
310 | 310 |
-> D-2 |
311 | 311 |
-> C-3 |
312 |
A-2
|
|
312 |
A-2 |
|
313 | 313 |
SM2_CRUMB Show only the breadcrumb trail, i.e. the current |
314 | 314 |
menu and all of it's ancestor menus. |
315 | 315 |
A-1 -> B-2 -> C-2 (CURRENT) |
316 |
SM2_SIBLING The same as SM2_TRIM however only sibling menus of
|
|
317 |
the current page are displayed. All other menus are
|
|
316 |
SM2_SIBLING The same as SM2_TRIM however only sibling menus of |
|
317 |
the current page are displayed. All other menus are |
|
318 | 318 |
trimmed to show only the path. |
319 | 319 |
A-1 -> B-2 -> C-1 |
320 | 320 |
-> C-2 (CURRENT) |
... | ... | |
326 | 326 |
------- |
327 | 327 |
All of these flags are optional. Any number of them may be combined. |
328 | 328 |
|
329 |
SM2_NUMCLASS Add the numbered menu classes to the menu. If this
|
|
330 |
flag is supplied, the "menu-N" and "menu-child-N"
|
|
329 |
SM2_NUMCLASS Add the numbered menu classes to the menu. If this |
|
330 |
flag is supplied, the "menu-N" and "menu-child-N" |
|
331 | 331 |
classes will be added. |
332 |
|
|
332 |
|
|
333 | 333 |
SM2_ALLINFO Load all fields from the page table of the database. |
334 | 334 |
This will result in quite a lot of memory being used |
335 | 335 |
and is not recommended, however it will make keywords, |
... | ... | |
338 | 338 |
NOTE: This flag must be used on the *FIRST* call to |
339 | 339 |
show_menu2 *for this menu ID*, or in combination with |
340 | 340 |
SM2_NOCACHE otherwise it will have no effect. |
341 |
|
|
341 |
|
|
342 | 342 |
SM2_NOCACHE Do not reuse or store the data read from the database |
343 |
between calls to show_menu2.
|
|
344 |
|
|
343 |
between calls to show_menu2. |
|
344 |
|
|
345 | 345 |
SM2_PRETTY Pretty print the menu HTML with spacing and newlines |
346 | 346 |
for debugging purposes. |
347 |
|
|
348 |
SM2_BUFFER Do not output the menu HTML but instead buffer it
|
|
347 |
|
|
348 |
SM2_BUFFER Do not output the menu HTML but instead buffer it |
|
349 | 349 |
internally and return it as a string from show_menu2. |
350 |
|
|
351 |
SM2_CURRTREE Exclude all other top level menus from being considered.
|
|
350 |
|
|
351 |
SM2_CURRTREE Exclude all other top level menus from being considered. |
|
352 | 352 |
Only items in the current menu tree will be output. |
353 | 353 |
This can be combined with any of the Group 1 flags as |
354 | 354 |
necessary. |
355 |
|
|
355 |
|
|
356 | 356 |
SM2_ESCAPE Call htmlspecialchars on the menu strings. This may be |
357 | 357 |
required with older installations of WB. By escaping the |
358 |
raw database strings, it permits menus to have HTML
|
|
358 |
raw database strings, it permits menus to have HTML |
|
359 | 359 |
formatting in them that would cause otherwise cause |
360 |
pages to fail validation.
|
|
361 |
|
|
362 |
SM2_SHOWHIDDEN Hidden pages are usually hidden all of the time, including
|
|
360 |
pages to fail validation. |
|
361 |
|
|
362 |
SM2_SHOWHIDDEN Hidden pages are usually hidden all of the time, including |
|
363 | 363 |
when they are active (i.e. current page or a parent page). |
364 | 364 |
Use private pages for time when you want pages to be |
365 | 365 |
hidden except when active. However for compatibility with |
... | ... | |
372 | 372 |
SM2_NO_TITLE Supress the value of the 'title'-attributes on links which |
373 | 373 |
are created by [a] or [ac] formatted links. |
374 | 374 |
|
375 |
This parameter also has an extended mode where an associative array of
|
|
376 |
options is supplied. See the EXTENDED OPTIONS section for details.
|
|
375 |
This parameter also has an extended mode where an associative array of |
|
376 |
options is supplied. See the EXTENDED OPTIONS section for details. |
|
377 | 377 |
Most users will NOT need to use this. |
378 | 378 |
|
379 | 379 |
$aItemOpen |
380 | 380 |
Format string to use for creating each individual menu item entry. |
381 |
A different format string may be used for the very first entry by
|
|
382 |
supplying a different format string for $aTopItemOpen. When set to
|
|
381 |
A different format string may be used for the very first entry by |
|
382 |
supplying a different format string for $aTopItemOpen. When set to |
|
383 | 383 |
false, it uses the default of '[li][a][menu_title]</a>' to maintain |
384 | 384 |
compatibility with show_menu(). Note however that CSS formatting is |
385 | 385 |
often easier if the classes are added to the <a> tag. Use the format |
386 | 386 |
string of '<li>[ac][menu_title]</a>' for this style of tag. |
387 | 387 |
|
388 |
This parameter may also be specified as an instance of a formatting
|
|
388 |
This parameter may also be specified as an instance of a formatting |
|
389 | 389 |
class for the menu. See the section "Formatter" below for details of |
390 |
the API this class must expose. When a formatter is supplied, all
|
|
390 |
the API this class must expose. When a formatter is supplied, all |
|
391 | 391 |
arguments after $aItemOpen are ignored. |
392 | 392 |
|
393 | 393 |
$aItemClose |
394 | 394 |
String used to close each item. Note that this is not a format |
395 |
string and no keywords will be replaced. When set to false, it uses
|
|
395 |
string and no keywords will be replaced. When set to false, it uses |
|
396 | 396 |
the default of '</li>'. |
397 | 397 |
|
398 | 398 |
$aMenuOpen |
399 |
Format string to use for opening a list of menu item entries. A
|
|
400 |
different format string may be used for the very first menu by
|
|
401 |
supplying a different format string for $aTopMenuOpen. When set to
|
|
399 |
Format string to use for opening a list of menu item entries. A |
|
400 |
different format string may be used for the very first menu by |
|
401 |
supplying a different format string for $aTopMenuOpen. When set to |
|
402 | 402 |
false, it uses the default of '[ul]'. |
403 | 403 |
|
404 | 404 |
$aMenuClose |
405 | 405 |
String used to close each menu. Note that this is not a format |
406 |
string and no keywords will be replaced. When set to false, it uses
|
|
406 |
string and no keywords will be replaced. When set to false, it uses |
|
407 | 407 |
the default of '</ul>'. |
408 | 408 |
|
409 | 409 |
$aTopItemOpen |
410 |
Format string for the first item. When set to false, it uses the same
|
|
410 |
Format string for the first item. When set to false, it uses the same |
|
411 | 411 |
format as $aItemOpen. |
412 | 412 |
|
413 |
$aTopMenuOpen
|
|
414 |
Format string for the first menu. When set to false, it uses the same
|
|
413 |
$aTopMenuOpen |
|
414 |
Format string for the first menu. When set to false, it uses the same |
|
415 | 415 |
format as $aMenuOpen. |
416 | 416 |
|
417 | 417 |
|
... | ... | |
419 | 419 |
EXTENDED OPTIONS |
420 | 420 |
================ |
421 | 421 |
The $aOptions parameter is a dual mode parameter. For most users, only the |
422 |
SM2_* flags will be sufficient. However, to access the extra options, it
|
|
422 |
SM2_* flags will be sufficient. However, to access the extra options, it |
|
423 | 423 |
must be supplied as an associative array. Note that the SM2_* flags are |
424 | 424 |
still required and must be supplied as 'flags'. |
425 | 425 |
|
426 | 426 |
'flags' **REQUIRED** These are the flags described in PARAMETERS |
427 |
above for the $aOptions parameter.
|
|
427 |
above for the $aOptions parameter. |
|
428 | 428 |
|
429 |
'notrim' Specify a number of levels relative to the menu level of
|
|
429 |
'notrim' Specify a number of levels relative to the menu level of |
|
430 | 430 |
$aStart that will always be displayed. This will cause the |
431 | 431 |
SM2_TRIM flag to be ignored for these levels. |
432 |
|
|
433 |
To supply one of these options in addition to the flags, the option array
|
|
432 |
|
|
433 |
To supply one of these options in addition to the flags, the option array |
|
434 | 434 |
should be created and passed as the $aOptions parameter: |
435 | 435 |
|
436 | 436 |
$options = array('flags' => (SM2_TRIM|...), 'notrim' => 1); |
437 | 437 |
show_menu2(0, SM2_ROOT, SM2_CURR+1, $options); |
438 |
|
|
439 |
|
|
440 |
|
|
438 |
|
|
439 |
|
|
440 |
|
|
441 | 441 |
FORMAT STRINGS |
442 | 442 |
============== |
443 |
The following tags may be included in the format strings for $aItemOpen and
|
|
443 |
The following tags may be included in the format strings for $aItemOpen and |
|
444 | 444 |
$aMenuOpen and will be replaced with the appropriate text. |
445 | 445 |
|
446 | 446 |
[a] <a> tag (no class): '<a href="[url]" target="[target]">' |
... | ... | |
476 | 476 |
|
477 | 477 |
[if(A){B}] |
478 | 478 |
[if(A){B}else{C}] |
479 |
|
|
479 |
|
|
480 | 480 |
A Conditional test. See below for more details. |
481 |
|
|
482 |
B Expression emitted when the if-test is true. This may be any string
|
|
483 |
that does NOT include the '}' character. It may include any of the
|
|
484 |
format strings described in the section FORMAT STRINGS with the
|
|
481 |
|
|
482 |
B Expression emitted when the if-test is true. This may be any string |
|
483 |
that does NOT include the '}' character. It may include any of the |
|
484 |
format strings described in the section FORMAT STRINGS with the |
|
485 | 485 |
exception of the conditional test (because '}' is not permitted). |
486 |
|
|
487 |
C Expression emitted when the if-test is false. This may be any string
|
|
488 |
that does NOT include the '}' character. It may include any of the
|
|
489 |
format strings described in the section FORMAT STRINGS with the
|
|
486 |
|
|
487 |
C Expression emitted when the if-test is false. This may be any string |
|
488 |
that does NOT include the '}' character. It may include any of the |
|
489 |
format strings described in the section FORMAT STRINGS with the |
|
490 | 490 |
exception of the conditional test (because '}' is not permitted). |
491 |
|
|
491 |
|
|
492 | 492 |
The conditional test is a combination of one or more boolean tests. |
493 | 493 |
If more than one test is supplied, it must be combined with other tests |
494 |
using either || (boolean OR) or && (boolean AND).
|
|
494 |
using either || (boolean OR) or && (boolean AND). |
|
495 | 495 |
|
496 | 496 |
A single test is made up of the left operand, operator and right operand. |
497 | 497 |
e.g. X == Y where X is the left operand, == is the operator and Y is the |
498 | 498 |
right operand. |
499 |
|
|
499 |
|
|
500 | 500 |
Left operand. It must be one of the following keywords: |
501 | 501 |
class Test for existence of one of the classes. Only the |
502 | 502 |
"==" and "!=" operators are permitted. In this case |
503 |
these operators have the meaning of "includes"
|
|
503 |
these operators have the meaning of "includes" |
|
504 | 504 |
instead of "equals". |
505 | 505 |
level Test against the page level. |
506 | 506 |
sib Test against the current page sibling number. |
507 | 507 |
sibCount Test against the number of siblings in the menu. |
508 | 508 |
id Test against the page id. |
509 | 509 |
target Test against the target attribute |
510 |
|
|
510 |
|
|
511 | 511 |
Operator. It must be one of the following: |
512 | 512 |
< Less Than |
513 | 513 |
<= Less Than Equals |
... | ... | |
515 | 515 |
!= Not Equal |
516 | 516 |
>= Greater Than Equals |
517 | 517 |
> Greater Than |
518 |
|
|
518 |
|
|
519 | 519 |
Right operand. The type of this operand depends on the keyword used |
520 | 520 |
for the left operand: |
521 |
class One of the "menu-*" class names as listed in the
|
|
521 |
class One of the "menu-*" class names as listed in the |
|
522 | 522 |
section "OUTPUT". |
523 | 523 |
level Test the page level against the following values: |
524 | 524 |
<number> absolute page level |
... | ... | |
535 | 535 |
the count of siblings in this menu. |
536 | 536 |
sibCount A positive integer. |
537 | 537 |
target A string, containing a possible target |
538 |
|
|
538 |
|
|
539 | 539 |
For example, valid tests are expression "exp" is emitted only when the menu item: |
540 |
|
|
540 |
|
|
541 | 541 |
[if(class==menu-expand){exp}] has a sub-menu |
542 | 542 |
[if(class==menu-first){exp}] is first item in a menu |
543 | 543 |
[if(class!=menu-first){exp}] is NOT first item in a menu |
... | ... | |
551 | 551 |
[if(id==parent){exp}] is the parent of the current page |
552 | 552 |
[if(target==_self){exp}] if value of target-attribute is '_self' |
553 | 553 |
|
554 |
If an else-clause was added, then the expression for the else would be
|
|
554 |
If an else-clause was added, then the expression for the else would be |
|
555 | 555 |
emitted in all other cases. For example the expression "foo" is emitted |
556 | 556 |
whenever the if-test is false, so therefore: |
557 | 557 |
|
... | ... | |
560 | 560 |
|
561 | 561 |
For multiple tests, the expression "exp" is emitted only when the menu item: |
562 | 562 |
|
563 |
[if(sib == 1 || sib > 3){exp}]
|
|
563 |
[if(sib == 1 || sib > 3){exp}] |
|
564 | 564 |
[is the first item] OR [is the 4th or larger item] in the menu |
565 |
|
|
565 |
|
|
566 | 566 |
[if(id == current && class == menu-expand){exp} |
567 | 567 |
[is the current item] AND [it has children] |
568 | 568 |
|
569 | 569 |
Note that all tests are evaluated in the order listed because: |
570 | 570 |
* there is no short-circuit evaluation (all individual tests are always evaluated) |
571 | 571 |
* there is no grouping of tests (i.e. no support for parenthesis) |
572 |
* both || and && are considered the same level
|
|
572 |
* both || and && are considered the same level |
|
573 | 573 |
|
574 | 574 |
|
575 | 575 |
|
... | ... | |
577 | 577 |
========= |
578 | 578 |
Note: This is an advanced and rarely needed feature! |
579 | 579 |
|
580 |
If you are capable of extensive PHP programming, it is possible to replace the
|
|
580 |
If you are capable of extensive PHP programming, it is possible to replace the |
|
581 | 581 |
predefined menu formatter that show_menu2 is uses with a custom module. See the |
582 |
include.php file of show_menu2 for an example of how the menu formatter must be
|
|
582 |
include.php file of show_menu2 for an example of how the menu formatter must be |
|
583 | 583 |
written. The API it must use is: |
584 | 584 |
|
585 | 585 |
class SM2_Formatter |
586 | 586 |
{ |
587 | 587 |
// called once before any menu is processed to allow object initialization |
588 | 588 |
function initialize() { } |
589 |
|
|
589 |
|
|
590 | 590 |
// called to open the menu list |
591 | 591 |
function startList($aPage, $aUrl) { } |
592 |
|
|
592 |
|
|
593 | 593 |
// called to open the menu item |
594 | 594 |
function startItem($aPage, $aUrl, $aCurrSib, $aSibCount) { } |
595 |
|
|
595 |
|
|
596 | 596 |
// called to close the menu item |
597 | 597 |
function finishItem() { } |
598 |
|
|
598 |
|
|
599 | 599 |
// called to close the menu list |
600 | 600 |
function finishList() { } |
601 |
|
|
601 |
|
|
602 | 602 |
// called once after all menu has been processed to allow object finalization |
603 | 603 |
function finalize() { } |
604 |
|
|
604 |
|
|
605 | 605 |
// called once after finalize() if the SM2_NOOUTPUT flag is used |
606 | 606 |
function getOutput() { } |
607 | 607 |
}; |
Also available in: Unified diff
! coreecting url to WB help in readme files module showmenu2