In #1497374: Switch from Field-based storage to Entity-based storage there are not yet explicit tests for a field with data shared between two different entity types. That's one of the trickier bits of the patch so we should really have explicit coverage. Given that patch is 580kb and blocks several others, and it's been manually tested for this case, I'm going to commit it without those tests, but adding them should block both release and a beta so we don't get nasty surprises later.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jibran’s picture

Issue tags: +Field API, +Entity Field API

Tagging.

catch’s picture

Title: Add explicit tests for fields shared between entities » Add explicit upgrade path tests for fields shared between entities
yched’s picture

Status: Active » Needs review
FileSize
11.06 KB

Patch - didn't test locally, let's see if I got everything right.

Status: Needs review » Needs work

The last submitted patch, field_upgrade_test-2078507-3.patch, failed testing.

yched’s picture

Status: Needs work » Needs review
FileSize
2.12 KB
12.31 KB

- Silly mistakes in the test d7 dump data (the shared field was marked 'deleted').
- There was indeed a problem with the upgrade path... A shared field got split in separate fields per entity types, but instances didn't point back to the correct field.

Status: Needs review » Needs work

The last submitted patch, field_upgrade_test-2078507-5.patch, failed testing.

yched’s picture

Status: Needs work » Needs review
FileSize
1.83 KB
12.23 KB

I changed the way we test field values, and it doesn't work (text values come up with the extra 'safe_*' property currently).
Reverted to the previous way.

swentel’s picture

Status: Needs review » Reviewed & tested by the community

Marvelous, RTBC when green.

Dries’s picture

Status: Reviewed & tested by the community » Fixed

Committed to 8.x. Thanks.

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