Follow-up to #2745179: Uncaught exception in link formatter if a link field has malformed data

Problem/Motivation

This should first be triaged and confirmed, but it doesn't appear that link validation is fired when data is imported into D8 link field.

Marking as major because this can lead to system stability issues.

Proposed resolution

Remaining tasks

Reproduce this by migrating in a simple CSV value for a link into a link field. See if malformed links can be stuffed into a node. If it can, then we need to make sure the validation doesn't just fire in the FAPI but also in normal entity CUD operations.

User interface changes

API changes

Data model changes

Comments

heddn created an issue. See original summary.

heddn’s picture

heddn
Primary language English
Location Nicaragua
CreditAttribution: heddn at MTech, LLC commented

It seems like, in general, field validation doesn't occur during a migration. Just confirmed with mikeryan1 in IRC. Also see #2550033: Handle empty fields gracefully

heddn’s picture

heddn
Primary language English
Location Nicaragua
CreditAttribution: heddn at MTech, LLC commented
Status: Active » Closed (duplicate)
Related issues: +#2698083: D6->D8: Migrating links without leading slash leads to fatal error
mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan at Virtuoso Performance commented

It should be simple enough to allow optional validation, though: #2745797: Add option to content entity destinations for validation.