Multiple role fields on one entity are not properly handled

Well this is good to know, but super edgy. Furthermore I'm not even sure it wouldn't work by design of the Drupal access logic if configured correctly. "Neutral" is the key point here, if there's no clear decision. Then the other field would be "asked".

So let's postpone this for now and before starting to work on this, we should be clear about how it should work and have tests first.

Since we are working on the entire entity through hook_entity_access, instead of defining the access per field instance, this is unfortunately not the case!

So we should convert the code, so that it works as @Anybody describes!

This was actually implemented before but broke, due to recent changes. Currently, if we have the "FALLBACK_NEUTRAL" case, we just skip to the next field. Problem is, that we do not return any access at all, If every field just simply skips this (We could also indirectly have Access:neutral, as we completely skip the hook then, nonetheless, we should set this explicitly).

Please review!

@Grevil: Just made a textual change. Do we have a test for this? If not, it should be added here, before we merge this. Doesn't have to be done now.

@Grevil please create a follow-up for the multi-field tests!

Can be minor, as I think it's totally untypical to have more than one role permissions field!

Done 📌 Create tests for entities using multiple role fields Postponed .

Automatically closed - issue fixed for 2 weeks with no activity.