I noticed when using Features to export all my fields that the nodeaccess_userreference field settings weren't getting saved along with the field itself.

I see that there's 1 variable, nodeaccess_userreference, used for storing settings.

Ideally these settings would be stored in field storage, or at least stored by their field key so those settings could be individually exported.

Comments

mrded’s picture

mrded commented
Status: Active » Fixed

As I can see nodeaccess_userreference attribute is already exportable. Reopen it if I'm wrong

djdevin’s picture

djdevin
he/him
Primary language English
Location Philadelphia
commented
Status: Fixed » Active

Yeah it's a variable but, but that one variable stores the settings for all nodeaccess_userreference fields.

So let's say we have two user reference fields on two different content types, when we package up each content type individually (with features for example) we can't package up the nodeaccess_userreference settings, because that variable captures all settings for all fields and those features would conflict when enabled together. The variable should really be called nodeaccess_userreference_CONTENT_TYPE_FIELD_NAME or instead use the field storage for that field instance so that a specific field's setting can be exported and not contain settings for all other fields.