No worries, thank you for helping - holidays for me too - but isolating and find myself here
Its a steep learning curve for me. There is nothing in the logs. I edited the .env file and opened dev tools and tried again - but i cant see any errors in the network tab - but not sure if i am looking correctly… this is what i see…
It looks like on Suite8 the Module Menu Filters don’t apply at the beginning. (This may be by design. I personally like the new way, but we don’t use many modules.) In your initial view each module has its own dropdown. The modules are not grouped by sales, marketing, etc in the new version like they were in the old version.
When you save and deploy, I don’t know if it is trying to change anything since the menu filters weren’t applied at the beginning. Since nothing is being updated/changed that might be why there are no errors. (I haven’t had the blank page when I tried it, so I’m not sure about that part.)
The Display Modules And Subpanels section in Admin will still allow you to hide and show certain modules from the users. So that section of the amdin panel is changing the nav-bar still. But that won’t help you with grouping them in dropdowns in the the navbar.
I’m trying to look more into the navbar in Suite8. I’ll post again if I find anything helpful and upgrade safe.
When on Version 7.12.2 Sugar Version 6.5.25 (Build 344), when we update the Module Menu Filters it would update the /custom/include/tabConfig.php along with other files. In Suite8 the /custom/include/tabConfig.php file is updated when we adjust the Module Menu Filters but nothing is changing.
I’m guessing it has to do with the new navbar settings being saved another place. I’ll keep looking.
I love the progress being made, but wow - as a non developer I’ve spent years trying to get to grips with the old framework - though always tried to keep up to date… but at the moment I’m feeling so complete and utterly lost .
"The first step is to create a standard component. You can place it anywhere, though we recommend following a folder structure similar to the core one. So you could add it to <suite-8-path>/extensions/<extension-name>/app/src/containers/sidebar-widget/<widget-name>"
There might be a a way to use the /core/app/core/src/lib/components/navbar/grouped-menu-item and the information in /custom/include/tabConfig.php to make an extension or something in the custom or extension folder to match the old menu layout you had, but I don’t know if that is possible.
You might have to wait for the Module Menu Filters integrated to the new front-end in a later update. One of the members of the Forum Team or Maintainer can probably help more after the holidays.
I’ll see if I can figure anything else out, but I don’t know if I’ll get any further.
If you want to change it globally, I think you can change it in config.php
'default_navigation_paradigm' => 'm',
to
'default_navigation_paradigm' => 'gm',
Anyway, the blank page is strange… Could you create an issue in SuiteCRM-Core project in github please? just for the blank page error (Update: just saw there is already an issue https://github.com/salesagility/SuiteCRM-Core/issues/46)