You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to run the migration on a Craft 4 site running craft 4.14.1, using Hyper version 1.3.5, the php craft hyper/migrate/typed-link-field command is giving me the following warning:
Preparing to migrate field “linkTo” (bfa89be4-0822-403c-b831-7f427692f644).
> Unable to find owner Matrix field for ID “182”.
> Field “linkTo” migrated.
When I migrate the content everything seems to work, but I wanted to check to make sure if there were any issues with our database that we should be resolving before moving forwards.
Tricky to say! It could be that this field is legitimately no longer in use on your site, and hence any error related to it doesn't matter, but it's worth double checking.
Can you look up your linkTo Typed Link field, or use it's ID of 182 and check to see if the owner Matrix field still exists? You can do this is a long-winded way by checking the context column in the fields database table. That'll reference a Matrix block type, which references a Matrix field. If the relations that hook all those things together has broken down (there's no Matrix field, or Matrix block type), then you're probably safe to disregard this, as the field is seemingly orphaned anyway.
Describe the bug
Hi,
I'm trying to run the migration on a Craft 4 site running craft
4.14.1
, using Hyper version1.3.5
, thephp craft hyper/migrate/typed-link-field
command is giving me the following warning:When I migrate the content everything seems to work, but I wanted to check to make sure if there were any issues with our database that we should be resolving before moving forwards.
The error comes from the codebase here:
hyper/src/migrations/MigrateTypedLinkField.php
Line 170 in 4f7d5f9
Steps to reproduce
Craft CMS version
4.14.1
Plugin version
1.3.5
Multi-site?
No
Additional context
No response
The text was updated successfully, but these errors were encountered: