Category: Menu

I use Tikiwiki v2.2

I use the standard menu id=42 for admin menu on the right pane on my website but the menus will not expand so I am able to see the menuitems.

I get the following javascript error in my browser:

Error: document.getElementsByName("icn" + foo)[0] is undefined
Source File: http://www.mydomain.com/lib/tiki-js.js
Line: 520

Featured link (tiki-admin_links.php) offers three types of links (framed, new window, replace).

This functionality would be most welcome with our menu system (tiki-admin_menus.php) when adding links.

It is not possible to set a multilevel menu using the default implementation of bootstrap in Tiki.

The result of trying using Tiki tools is a weird behavior that doesn't fit the available tools and the user choice (sublevel are omitted and missing).

They were debate among the dev community on early bootstrap v3 days about having or not multilevel menu and multilevel dropdown.

As per today, there are already plenty of solutions for v3 and v4 including multilevel menu;
[https://www.google.com/search?q=bootstrap+v4+multilevel+menu&rlz=1C5CHFA_enIL504IL504&oq=bootstrap+v4+multilevel+menu&aqs=chrome..69i57.8999j0j4&sourceid=chrome&{google:instantExtendedEnabledParameter}ie=UTF-8|Goole search]

Implementing one of those solution in our Tiki menu (that include multilevel menu tools) will avoid revamping it from the ground and having to distinct interface (bootstrap menu __vs__ suckerfish/legacy tiki menu).

One of the key features of Smartmenus is to enable more menu levels than the two that Bootstrap supports out of the box. But this isn't happening yet with Tiki's menus in branch 19.

Also, the down arrows in parent items display briefly but then slide into/behind the item text so they no longer display.

I categorized this "Dogfooding" because people have been requesting it and also I want to check out its full functionality at themes.tiki.org.

More info: Section level 3 items (and their child items) are ignored in the menu implementation when the menu type is "Bootstrap", so Smartmenus has nothing to work with where level 3 should be (just a detail).

As of now, you need to full admin to edit the menus. Often, we would like to delegate this to somewhere at the editor level.

{syntax type="tiki" editor="plain"}
I have a menu with a third-level dropdown, followed by another link in the second level, as shown in the attached screenshot. The menu is saved, including the last option, "One more link", but the menu doesn't show the item "One more link" in the second-level dropdown, or anywhere. Another master instance here on my localhost also has the same problem. The second-level dropdown items just get truncated after the link with the dropdown. This obviously doesn't happen with first-level links, but is happening with second-level links (and probably with third-level, etc. links).

This is a regression maybe linked to the change in Smartmenus versions.

When entering the parameters for the menu module, to have a horizontal Bootstrap menu, if you don't enter anything in "Use Bootstrap menus", the menu will be Bootstrap as this is the default. And it will be horizontal if for "Type" you enter "horiz". But if for "Use Bootstrap menus" you enter "y", then the resulting menu is vertical, not horizontal.

On /tiki-admin_menu_options.php , "Preview" tab, a preview of the menu should display. The hierarchy of links is ok, but the menu type doesn't match the requested options (CSS or not, horizontal or vertical). Maybe this code hasn't been updated since Bootstrap integration.

Using (or not) structure to create a menu, the first item (top menu item) i not clickable anymore.

Check : http://bsfez-11581-6514.show.tikiwiki.org/tiki-index.php

Menu Wiki 'List Pages' and 'Create a Wiki Page' are two tabs on one page.

After visiting 'Create a Wiki Page' the focus stays on this tab when visiting 'List Pages'. Average expectation is assumed to refocus to the new tab.

See the videoscreenshot: {file type="gallery" fileId="2062" showicon="y"}

Also the "Add or remove from a group" action at tiki-adminusers.php#contenttabs_adminusers-1

{img fileId="2066" thumb="box"}

On fresh install:
* I set the layout to "Classic bootstrap"
* I set the Fixed-top navbar height to 70px
* I mov the left menu to the top and set it to nobox=y (check it is set to horizon)

--An dropdown of the menu 42 states always open (no matter if it is placed on top or at the bottom)
Creating a second menu doesn't change the issue (menu 42 item stays open) (Wiki subsection only may be ?)--

{mediaplayer src="display1916"}

I switched from the Tiki default theme to a new "empty" theme and it seems to ended. (menu closed properly)

---
__Update 2023-06-26:__
It seems it is related to the page location.
Some items will stays open when you are looking to a page related.

{mediaplayer src="display2068"}

Since some weeks ago, afaik (April 2008, or so), menus and menu options cannot be seen for anonymous on several sites that I admin, including edu.tikiwiki.org, if you select some themes. Example: moreneat.css

On others, like http://moviments.net/ilp (using nornia.css), the menu on a module assigned to anonymous and registered, was shown when you logged in. Right now I've just assigned thatmodule to admins only, and used menupage module, which works fine. But I can re-set the previous config. is somebody wants to reproduce the missworking.

Part of IRC-Log from 20050709:

[18:48:51] luci amette: imho the quickest fix for the Admin menu would be: 1. rename "Admin home" to "Admin Sections"
[18:49:40] luci amette: 2. clicking Admin folder would bring you list with the same entries like when you expand the folder
[18:50:53] luci 3. rename "Admin mods" entry to "Mods Admin" to prevent listing it as first entry since the menu is alphabetically sorted
[18:50:57] amette luci : Yup, that sounds really clean - Admin Home should be moved to the top of the submenu then though
[18:51:08] luci sure
[18:51:36] amette Ah, just wanted to ask - yeah, alphabetical sort is bad here - I just looked at my menu and it took some time to find "Verwaltung Hauptseite" <- very much at the bottom
[18:52:12] luci "Admin Sections" sounds logical to me because we use "Sections" in title bar there already anyway
[18:52:41] luci amette: good point, that'Ä‘ why i fixed my language.php entry to "Administrace"
[18:55:06] luci ok, we can consider removing that sorting stuff
[18:55:42] amette What would be a good solution imho - It gives you e.g. the option to say "The third entry in Admin menu"
[18:55:52] luci maybe only the module one
[18:55:56] amette And you can sort options by importance!
[18:56:14] amette And I'm often confused, since my admin-account uses English and amette-account uses german
[18:56:20] luci amette: not that easy, some appear depending on fetures enabled

From here on, was discussed, that Admin Items could/should be hidden, when the corresponding feature is not activated. I'm not too sure about that now - because like that you loose the ability to customize a feature and then afterwards activate/release it.

I created one menu with multiple sub-items. I then applied it to user module, e.g.

{phplayers id=44 type=vert}

And displayed it on the right column. All good so far.

But when I added another menu with PHPlayers, e.g.

{phplayers id=45 type=vert}

then the first menu no longer showed the roll-over menus in the proper place, nor did they disapear after exit.

Since I upgraded to 3.0 from a 2.x I lost the mytiki item on the left menu and I don't know how to restore it. I'm using coalesce theme. Mine website is www.magowiz.net

There are two ways to specify navbar foreground and background colors: the "Navbar background color" checkboxes on the admin Look and Feel page and the "CSS class(es) for the menu nav element" on the admin-modules page. The Look and Feel checkbox value is used in all cases, though, so if that preference is set to "Dark", for example, to get a dark-background navbar for the main navigation, then ''every'' navbar instance assigned on the admin-modules page gets the CSS classes for "Dark". This causes a problem if, for example, a Light-background system menu is wanted in the footer. Then the CSS classes for the navbar are "navbar-light bg-light navbar-dark bg-dark". In my test, this caused light text on light background, so it's unreadable.

Unless I'm missing something, I think it would be good if the navbar color switch on the Look and Feel admin page was removed and the navbar color specified by the module only (maybe using a checkbox or radio buttons instead of inputting the class names as is required now), or else make the L&F switch apply only to the admin interface. This would be similar to moving the setting of the site logo and title from Look and Feel to the module admin page.

{syntax type="tiki" editor="plain"}
Mobile mode in doc.t.o (12.x)
Log in as registered user, with chrome on android
Go down and click to open the editor menu
Click on File galleries.
Error shown:

Page not found
Documentation&ui-page=cssmenu5-6

---

I tried the same from a PC with Chrome 29, switched to mobile mode, and then, when I cicked at the File Galleries link, or Adminlink, I get a WSOD with the url:
https://doc.tiki.org/Mobile+Home&ui-page=cssmenu5-6
(for file galleries, in this case)
---
UPDATE: same type of approach seems to work in dev.t.o. Weird! {sign user="xavi" datetime="2013-11-22T14:19:52+00:00"}
---
UPDATE 2015: Is this still relevant? We're not on 12 any more so i think this needs a show instance to be investigated further {sign user="jonnybradley" datetime="2015-07-19T10:44:35+00:00"}

https://doc.tiki.org/Menu#url_-_attributes_target_rel_..._

https://doc.tiki.org/How+to+make+menu+items+open+in+a+new+window

one of the above documented features should work.... are any regression tests done before doing new releases? ugh... ad hoc testing makes software quality degrade you know!

I implore the team to stop adding features to TikiWiki without making sure they don't break the most trivially basic functionality first. No body wants another kitchen sink in a house that's falling apart :-(

My website has a navigation menu set up using a tiki structure. It is set to use non-bootstrap menus for this. When I hover over the menu, there are potentially multiple levels of the menu that can pop out.

Since Tiki 14.x, only one level of the menu will pop out. The menu options that have more levels below them even retain the ::after arrow showing that it can pop out, except, when you hover over it, the second menu level does not pop out.

I have attached a screenshot to show what my set up looks like.

{img fileId="994" thumb="y" rel="box[g]"}

To reproduce:

1- tiki-admin_menus.php

2- click the permission key

ex.:
tiki-objectpermissions.php?objectName=Go Green&objectType=menus&permType=menus&objectId=56

{CODE()}Permissions
No rows found

Warning
You must select at least one feature.{CODE}

Like this site:
http://agilewebsolutions.com/downloads


When you scroll down, the menu stays. The same idea could be done for a menu on the bottom of the page.

When you rollover any of the phplayers horiz menu, causing the menu to popup, and then subsequently try to use an overlib, e.g. the userlink popup that appears when you rollover the name of a user, the overlib will fail with javascript error "windowWidth is not a function".

The reason is because phplayers layersmenu.js (or if you have copied its contents into another file like layersmeny-header.ijs) defines windowWidth as it works, destroying the overlib function.

on 1.9.cvs

Horizontal phplayer menu is behaving weird when adding new options, etc. (sections level 0 and options inside dissapearing + separators rare)
Menú and menú items below, in utf-8 encoding.

{CODE()}
INSERT INTO `tiki_menu_options` (`optionId`, `menuId`, `type`, `name`, `url`, `position`, `section`, `perm`, `groupname`) VALUES
(171, 43, 'r', 'Comissions', 'Comissions', 10, '', '', ''),
(172, 43, 'o', 'Secretaria', 'Comissió+de+Secretaria', 20, '', '', ''),
(173, 43, 'o', 'Turisme', 'Comissió+de+Turisme', 30, '', '', ''),
(174, 43, 'o', 'Dinamització social', 'Comissió+de+Dinamització+social', 40, '', '', ''),
(175, 43, 'o', 'Medi ambient', 'Comissió+de+Medi+ambient', 50, '', '', ''),
(191, 43, 's', 'Enllaços', 'tiki-directory_browse.php', 300, '', '', ''),
(177, 43, 'o', 'Login', 'tiki-login_scr.php', 1010, '', '', 'Anonymous'),
(178, 43, 'o', 'Logout', 'tiki-logout.php', 1010, '', '', 'Registered'),
(179, 43, 's', 'Activitats', '', 200, '', '', ''),
(180, 43, '1', '2007', '', 210, '', '', ''),
(181, 43, '2', 'Artístiques i artesanals', 'Activitats+artístiques+i+artesanals', 220, '', '', ''),
(182, 43, 'o', 'Comerç Just', 'Activitats+artístiques+i+artesanals+de+Comerç+Just', 230, '', '', ''),
(190, 43, '-', '', '', 1001, '', '', ''),
(185, 43, '1', '2006', '', 250, '', '', ''),
(186, 43, 'o', '<img src="img/rss.png" alt="Sindicació de notícies per Agregadors RSS" title="Sindicació de notícies per Agregadors RSS" border="0" />', 'Notícies+per+RSS', 1008, '', '', ''),
(189, 43, '-', '', '', 1000, '', '', ''),
(192, 43, 's', 'Home', 'index.php', 5, '', '', ''),
(193, 43, 'o', 'Presentació', 'Presentació', 7, '', '', ''),
(194, 43, 'o', 'Història de l''associació', 'Història+de+l´associació', 400, '', '', ''),
(195, 43, '-', '', '', 1002, '', '', ''),
(196, 43, '-', '', '', 1003, '', '', ''),
(197, 43, '-', '', '', 1004, '', '', ''),
(198, 43, '-', '', '', 1005, '', '', ''),
(199, 43, '-', '', '', 1009, '', '', ''),
(200, 43, 'o', 'Historia2', 'Historia2', 410, '', '', ''),
(201, 43, 'o', 'Presentació de les activitats', 'Presentació+de+les+activitats', 205, '', '', ''),
(202, 43, '-', '', '', 60, '', '', '');

INSERT INTO `tiki_menus` (`menuId`, `name`, `description`, `type`) VALUES
(43, 'Menú horitzontal capçalera', 'Menú horitzontal per la capçalera de la web', 'd');
{CODE}

If interested in analyzing any more in the server where it happened, please, request me an admin account at:
http://www.moviments.net/valldelcorb

so that you can reproduce the buggy behavior.
I'm afraid of adding new items or sections since they break the present layout of phplayer menus if it is set as horitzontal.
when previewed as vertical, it's always shown ok, at it should.

I was using twist.css theme style.
-------
April 4th: the problem seems to dissapear if using tikineat style instead of twist.css theme style. See the screenshots of the same menu with each theme style.

After upgrading to 1.10, php layers menus from 1.9 are gone from site identity.

Apparently, there are also reports of display of horizontal CSS ("suckerfish") menus not correct. Tag isn't setting horizontal style or getting css/cssmenu_horiz.css so top-level items display vertically rather than horizontally.