-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adminimize options are not resetted. #115
Comments
Maybe you have a cache active that store the menu? Adminimize use a cache, if is existent. If not, it run on each load to create the menu so that a reset is not necessary. If you haven't settings in Adminimize or delete the settings globally, also possible on the settings page, it should work and all menu items are visible there a have access by the current logged in user role. Your first screenshot list also no menu items that Adminimize should hide, the array is empty. So if you missed items in the menu, check the capabilities of the role. |
clean cash, clean browser cache.. anything is NOT work. where is the exact db this plugin use? can I delete manually? I cannot find exactly.. I can find some db entries in |
The plugin store alle settings in one db-item, Table |
Hi there, the same issue too! I also tried to use "Uninstall Options," but still, my editor has limited access. |
Some years on, but I have the same issues as above - despite selecting "Uninstall options", deactivating, deleting, reinstalling the plugin, the "Editor" users only see my initial settings for the Admin menu - I don't seem to be able to get them back whatever I do ! |
Version Information
Steps to Reproduce
What I Expected
when login admin page with new user as "editor" role, menus are have to reset
What Happened Instead
but it's not.
by bug Helper, I can check what happen behind it.
please check this screenshots
I guess something corrupted.
I already tried uninstall option, remove plugin, re-install plugin.
also with github master one.
Screenshot or Video
The text was updated successfully, but these errors were encountered: