@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Posted2 days 13 hours ago by Francis Greaves (themetman) on:
Hi @yorkshirepudding!
Nothing in admin/reports/fields or admin/config/development/configuration/single/export
There is a field in the database though.
Should I just copy the item...
Posted2 days 19 hours ago by Francis Greaves (themetman) on:
That is not a core field so my guess is it must exist, though perhaps it is a field defined but without any instances.
A few places to check:
admin/reports/fields - is it...
Posted2 days 20 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
Comments
Yes, the easiest way do do this would be with Layouts. You can add a "Visibility condition" to the menu block that checks a User's role.
Start on the Layouts UI at admin/structure/layouts, and click "Manage Blocks" for the default layout.
For whichever menu you'd like to hide, click on the "Configure" link at the right.
When the modal opens, csroll down to the "Visibility conditions" section at the very bottom, and pop it open. Click on "Add visibility condition"
Then select the User: role option.
Then select the user role "Authenticated" if you only want people who are logged-in to see the menu!
Note that you will need to repeat these steps for all layouts where you want the block limited by role.