Skip to content
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

[Bug] Recent articles in content menu in backend empty for non-root #7487

Closed
ToBe998 opened this issue May 18, 2018 · 6 comments
Closed

[Bug] Recent articles in content menu in backend empty for non-root #7487

ToBe998 opened this issue May 18, 2018 · 6 comments
Assignees
Labels
bug A bug that has been verified

Comments

@ToBe998
Copy link
Contributor

ToBe998 commented May 18, 2018

Inside Bolt's backend, on the content menu (the dark part on the left, starting with "overview") shows entries for each contenttype. When you hover over a contenttype there, it will shows a link for the contenttypes overview and a link to create a new item.
Below those two, you can see a list of the most recently edited articles.

Problem
The list is correctly showing recent items when logged in as a root user, but is empty for non-root users (in my example a chief-editor.

The permissions.yml is untouched in this example.


  • Relevant Bolt Version: 3.4.7
  • Install type: Composer install
  • PHP version: 5.6
  • Used web server: Apache 2.4
  • For UX/UI issues: Chrome

Reproduction

  • Make sure you have a couple of edited items in at least one contenttype
  • Login as *root user and hover over that contenttypes menu -> The recent items show up
  • Logout
  • Login as user with chief-editor role and hover over that contenttypes menu -> The recent items are empty
@ToBe998
Copy link
Contributor Author

ToBe998 commented May 18, 2018

I did some debugging and could at least see that:

  • The recent items get loaded from storage and added to the menu entry
  • The items get the permission "contenttype:"
  • The items arrive inside the menu builder

that's as far as i got

@bobdenotter
Copy link
Member

I can confirm this behaviour. I'll see if I can figure out where it goes wrong.

Good find, @ToBe998 👍

@bobdenotter bobdenotter self-assigned this May 18, 2018
@bobdenotter bobdenotter added the bug A bug that has been verified label May 18, 2018
@bobdenotter
Copy link
Member

Turns out this is a duplicate of the dreaded "Configuration error: Permission 'everyone' is not granted to any roles. You should add a role for this permission to permissions.yml. (5 minutes ago)" issue..

screen shot 2018-05-18 at 17 12 25

Still digging..

@ToBe998
Copy link
Contributor Author

ToBe998 commented May 22, 2018

Is there some hack for the permissions.yml to fix this in Bolt 3.4 too?

@jadwigo
Copy link
Contributor

jadwigo commented May 23, 2018

Probably by adding a single line to your permissions.yml as in the change: 7963589

global:
    checks: [ admin, developer ]

@bobdenotter
Copy link
Member

@ToBe998 In addition to that, add everyone: [ everyone ] to make other users also see the "latest entries".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug that has been verified
Projects
None yet
Development

No branches or pull requests

3 participants