Problem/Motivation
We now have three defined roles in Umami; Administrator, Author and Editor. The Recipe content type has field_author, which is an entity reference to User, but does not restrict by role, and allows selection of the anonymous user.
We could also use this issue to discuss whether this field is unnecessarily complecting the system. We could just have the author of the node in the system be credited as the author. The only value in having a separate field I am aware of is that it allows one user to input content and credit another author instead. This is a valid use case but is niche. moved to #2991473, we should fix the problem here, and debate removal in a separate issue.
Proposed resolution
Either
- remove field_author altogether, and replace its representation in the front end with the actual author
- keep field_author but restrict it in config to only allow users with the Author role and to actively disallow the anonymous user.
- do option 2) which should be a quick config change, and open a follow up to discuss 1)
Remaining tasks
All the things
User interface changes
TBD
API changes
None
Data model changes
TBD
Comments
Comment #2
eli-tFollowing initiative call, have split the removal of field_author to #2991473 so we can fix the bug here and discuss removing the field in parallel there.
Comment #3
eli-tUpdate title to represent decided course of action.
Comment #4
parijke commentedWouldn't it be the simplest to only allow persons with the role of author to create recipies? In that case you can use the user's authored by field to reference the user who deserve the credits?
Instead of manually reference an author?
Or am I missing something here?
Comment #5
eli-t@parijke good spot, implementation of #2991473: Remove the field_author from Umami recipe content type means this is no longer necessary.