You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be a good idea, to adapt the horde_variable that is send to the fronted. One could send an extra entry called "active" with a boolean as value. If for example active: false would be in the horde variable, then Reactfrontend knows that it should not show part of the object in the menu.
Example of Horde-variable datastructure:
{
entryId: "horde-component",
type: "entry",
parent: "",
caption: "horde-component",
action: "router",
targetUrl: "/subpage1",
icon: "",
active: "false" # Here one could add the active entry
},
This could be practical, because there are entries in the Horde menu-tree-object, such as "horde- components", which should not be displayed in the menu. The Horde Treeobject has an enty "active = false" to help with this.
The text was updated successfully, but these errors were encountered:
It might be a good idea, to adapt the horde_variable that is send to the fronted. One could send an extra entry called "active" with a boolean as value. If for example
active: false
would be in the horde variable, then Reactfrontend knows that it should not show part of the object in the menu.Example of Horde-variable datastructure:
This could be practical, because there are entries in the Horde menu-tree-object, such as "horde- components", which should not be displayed in the menu. The Horde Treeobject has an enty "active = false" to help with this.
The text was updated successfully, but these errors were encountered: