Typed Link Fields not migrated when stored within Vizy field

[walshmichael]

Describe the bug

Migration of Typed Link Field content to Hyper when within Matrix fields does not appear to work.

When running the CLI content migration reports successful. Indeed other content types are migrated as expected and no errors are outputted via CLI or logs.

On review of the CMS content after, any Vizy field that is within a Matrix field has not been migrated. Original data/schema is still intact within the database.

Example 1 (Entry):

Before.

[{"type":"vizyBlock","attrs":{"id":"vizy-block-9JMEYOys3B","enabled":true,"collapsed":false,"values":{"type":"type-YaTWjDnVA8","content":{"fields":{"linkItem":{"ariaLabel":null,"customQuery":null,"customText":"This is a button example","target":"","title":null,"type":"entry","value":"67"}}}}}}]

After.

[{"type":"vizyBlock","attrs":{"id":"vizy-block-9JMEYOys3B","enabled":true,"collapsed":false,"values":{"type":"type-YaTWjDnVA8","content":{"fields":{"linkItem":{"ariaLabel":null,"customQuery":null,"customText":"This is a button example","target":"","title":null,"type":"entry","value":"67"}}}}}}]

Example 2 (Url):

Before.

[{"type":"vizyBlock","attrs":{"id":"vizy-block-slvf2i63O5","enabled":true,"collapsed":false,"values":{"type":"type-YaTWjDnVA8","content":{"fields":{"buttonColor":"default","linkItem":{"ariaLabel":null,"customQuery":null,"customText":"Find out more","target":"_blank","title":null,"type":"url","value":"https://www.google.com"}}}}}}]

After.

[{"type":"vizyBlock","attrs":{"id":"vizy-block-slvf2i63O5","enabled":true,"collapsed":false,"values":{"type":"type-YaTWjDnVA8","content":{"fields":{"buttonColor":"default","linkItem":{"ariaLabel":null,"customQuery":null,"customText":"Find out more","target":"_blank","title":null,"type":"url","value":"https://www.google.com"}}}}}}]

Steps to reproduce

1. Start with Craft CMS 4.14.11.1 and Typed Link Field 2.1.5
2. Install Hyper 1.3.7
3. Run craft hyper/migrate/typed-link-field
4. Run craft hyper/migrate/typed-link-content
5. Confirm content within Matrix field and Vizy has not been migrated in admin.
6. Inspect matrix database table to confirm dataset has not changed.

Craft CMS version

4.15.6.1

Plugin version

1.3.7

Multi-site?

Yes

Additional context

No response

[engram-design]

Just to be clear, your field setup is Matrix > Vizy > Hyper (Typed Link)?

[walshmichael]

That is correct, yes.

[walshmichael]

Not sure if this is the root cause but hopefully helpful.

Looking at the convertModel function - once Vizy content for migration is found, does not appear to look for any of the value fields in my schema. Is this a difference in schema versions somewhere?

$linkValue = $oldSettings['linkedUrl'] ?? null;

In the case of a Url link the value is stored in value not linkedUrl.

if ($link instanceof ElementLink) { $link->linkSiteId = $oldSettings['linkedSiteId'] ?? $oldSettings['siteId'] ?? null; $link->linkValue = $oldSettings['linkedId'] ?? null; }

In the case of a Entry link, the value in my schema is stored in value not linkedId.

[walshmichael]

We have been able to resolve this.

For anyone who stumbles upon this ticket and might need to understand the issue, from our perspective the following was occurring.

1. Hyper migration does have a function that attempts to migrate Typed Links in Vizy fields. It uses the Vizy content service for this, however appears to miss the fields due to a comparison that uses a flattening of nested fields which results in keys such as 1.attrs.values.content.fields.linkItem.type. These keys are matched against the field handle (values.content.fields.linkItem for example) with a str_ends_with which misses, due to the trailing .type.

2. Hyper then tries to flatten a resultant match and convert the model for field updates. Again, the flattening appears to produce keys that never match due to the trailing .type.

3. Hyper convertModel is looking for what must be a different Typed Link schema than our database uses, so fields such as linkedUrl, linkedId, etc cannot be found. We null coalesced these to find the old schema values if the new ones are not there. Standard fields are stored as value, siteId, type, etc. Extra settings like target and customText are stored in a JSON packet with the key payload for the new schema, we needed to look instead in the old schema for simply target, customText, customQuery, etc.

[engram-design]

Appreciate the write-up @walshmichael !

I'm not sure if Typed Link has (again) updated their schema, but last time I look at this, they were deffinately using linkedUrl and linkedId for the "value" of links...

I'll be reviewing Vizy-handled content shortly.

[walshmichael]

Thanks @engram-design

Yes it is odd. The lenz_linkfield table certainly used linkedUrl and linkedId in our database, however the Vizy fields being directly sourced from the Vizy JSON objects did not reflect, instead with the other schema.