For example, a computed field without a UI will not have a useful way for the user to act on a conflict; and it is computed, the new value being saved is going to be the correct one. There should be configuration, or an alter hook, to allow specific fields to be skipped, or always use a specific strategy.

The example for this on Drupal.org is field_issue_last_status_change.

Comments

drumm created an issue. See original summary.

drumm credited xjm.

drumm’s picture

drumm
he/him
Location NY, US
commented

xjm pointed out this behavior via Slack.

hchonov’s picture

hchonov
Primary language Bulgarian
Location Burgas
commented

Is it correct that this is targeting the 7.x-1.x branch ?

drumm’s picture

drumm
he/him
Location NY, US
commented

Yes, that is the version Drupal.org uses. I think I may have seen equivalent functionality in one of the 8.x-* branches, we should make sure it is there to help smooth Drupal.org’s upgrade path. The project page is promising:

Conflicts which will be auto merged:
…
-changes in fields to which the user does not have access
--fields with no edit access
--fields not part of the entity form display

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented

Cross-posting as I ran into this with computed fields in D10 #3566032: autoMergeNonEditableFields() clears computed entity reference fields I hope the fix is in the right direction.