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
Sometimes workbench does not show “Create Content” in the workbench submenu if the user does not have any edit permissions. I saw this once and it was the first time a user logged in - they had CLA permissions, but no actual permission on a collection.
Not exactly sure what caused or resolved it. Not sure if this is caching or a bad plugin. It’s not clear to me if the “Admin Toolbar Links Access Filter” is playing a role in this or not.
Noticed this again and changed the weight of the menu from 0 to 1. That seemed to fix it, but then I saw the issue again.
There seems to be some way to get it stuck. For example, you can see “Create content” from parts of the site, but then it’s gone when you click on “My Workbench”. Not sure what gets it stuck and not sure if menu order really helps. Essentially, it’s glitchy and I'm not sure of the variables that cause it.
The text was updated successfully, but these errors were encountered:
Sometimes workbench does not show “Create Content” in the workbench submenu if the user does not have any edit permissions. I saw this once and it was the first time a user logged in - they had CLA permissions, but no actual permission on a collection.
Not exactly sure what caused or resolved it. Not sure if this is caching or a bad plugin. It’s not clear to me if the “Admin Toolbar Links Access Filter” is playing a role in this or not.
Noticed this again and changed the weight of the menu from 0 to 1. That seemed to fix it, but then I saw the issue again.
There seems to be some way to get it stuck. For example, you can see “Create content” from parts of the site, but then it’s gone when you click on “My Workbench”. Not sure what gets it stuck and not sure if menu order really helps. Essentially, it’s glitchy and I'm not sure of the variables that cause it.
The text was updated successfully, but these errors were encountered: