Menu changes not permanent

Hey folks. I’m installing and populating a new instance of suitecrm8.

Everything is functioning fine, but for some reason when I set a user to see the “Module Menu Filters” the setting doesn’t persist after they log off / log in.

Is this a known issue?

In essence, I want to clear up what is quite a cluttered menu with all of the actions / features and create custom menus using “Display Modules and Subpanels”. But for some reason I a) can’t set them as default, and b) they don’t remain as default once a user logs off and logs back in.

Any help would be greatly appreciated.

Hi, welcome to the Community! :tada:

Which version are you using, exactly?

Thanks @pgr

It’s version 8.7.1 self-hosted, to be precise.
Installed via Softaculous

Yeah, maybe it is known issue. You can search in this forum.

Thanks for the reply.

I’ve already searched comprehensively on this forum and more widely through search engines galore. I can’t find this issue being discussed anywhere, hence why I added this thread.

The thread you’ve linked me to shows someone asking how to change the menu, and being shown the setting within a user’s profile.

My issue is that these changes don’t persist.

You are right that this might be hard to search for, because there is an element connecting several different manifestations of the same issue: SuiteCRM saves information to user profiles, several features and configurations need this (even though the users are usually not aware of this).

Thanks for the reply @pgr

I don’t quite follow though? Is there a known issue that certain settings don’t persist after logging off?

It all seems a bit of a strange way to configure the main menu. Surely applying it across the site - regardless of the user and their role - is cleaner and simpler?

Since the bug is not fixed yet (to my knowledge) I don’t know the exact extent of it. The bug is about settings changes not sticking across logins.

Different people will stumble with different settings, so the posts look different but I believe the underlying issue is the same, and yes, it is a known issue…

I can’t search right now but maybe somebody else can find this on GitHub post the link here