We are using Beans as part of our site development workflow and have been for almost a year now. We are creating them programmatically and then inserting the blocks onto nodes via an entity reference select field. It's worked well for outputting bands of customizable content.
However, while the individual Beans are creating appropriate permission options (create, edit, view, delete; permissions.png) they don't seem to be applying to what's available to them in the select list for entity reference field (select field.png). Whenever the "add" option is selected for a role on one Bean, a user with that role now has the ability to add all of the Beans.
Is the problem that the permissions set really only apply via the Blocks list (/admin/content/blocks)? If so, does anyone have an idea how this can be carried over to the inline entity reference?
| Comment | File | Size | Author |
|---|---|---|---|
| select field.png | 96.95 KB | dgeezy@gdeezy | |
| permissions.png | 56.58 KB | dgeezy@gdeezy |
Comments
Comment #2
dgeezy@gdeezy commentedClosing this as we switched to the Paragraphs module for our purposes.
Comment #3
damienmckenna+1 for going with Paragraphs, it's the better option when you just want embedded content in nodes.