Open tipue-dev opened 12 months ago
The changes in sub CustomerNavigationBar
may affects also other NavBar modules of the znuny framework and also Znuny packages like FAQ and similar packages (also by third-party developers). These packages needs to get checked/fixed when approving and merging this changes and requires a big note on developer documentation.
Proposed change
EDIT: Extended the fix. The customer frontend in Znuny 7 changed in a way that there are no sub menus by default anymore. The processing of NavBarModule for process tickets doesn't work correctly after this change. It adds an 'empty' menu entry that is clickable and will be highlighted on mouse over.![image](https://github.com/znuny/Znuny/assets/80031303/40fab676-b326-498d-9878-69f185329fe8)
This problem was also the reason for the bug https://github.com/znuny/Znuny/issues/355. This bug has been fixed by hiding the wrongly created empty sub menus. My fix stops the creation of the wrong submenus, so i also reverted the fix for that problem and added some css, so that sub menus now work normally and in a small window.
This all is because the entry for process tickets isn't deleted correctly and the NavBarModule-hash get's a bit scrambled up. Before the NavBarModule for process tickets is checked it looks like this:
After the NavBarModule for process tickets tries to delete the entry for process tickets:
With this fix, the entry get's deleted correctly:
1 - 🐞 bug 🐞
Breaking change
I removed the return of the menu entries, since they are passed as a reference anyways. This might be a breaking change if there are NavBarModule in use that i don't know about, but they would likely also create ghost entries and would have to be changed.
Checklist