-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LinkField throws error when running craft\migrations\Install #250
Comments
TomDeSmet
changed the title
LinkField throws error when running craft\migrations\Install
LinkField throws error when running craft\migrations\Install due to Jan 9, 2023
columnSuffix: null
TomDeSmet
changed the title
LinkField throws error when running craft\migrations\Install due to
LinkField throws error when running craft\migrations\Install due to columnSuffix being null
Jan 9, 2023
columnSuffix: null
TomDeSmet
changed the title
LinkField throws error when running craft\migrations\Install due to columnSuffix being null
LinkField throws error when running craft\migrations\Install
Jan 9, 2023
any update on this error, running into the same error code while attempting to upgrade from Craft 3 to Craft 4. |
+1 also had this problem, I could provide an reproducible example (via DDEV) if this would be helpful for debugging |
Ah, just saw #254 - would this also fix this issue? 🙂 (i can test it also next week if test is needed) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What I'm trying to do:
I have some custom project configs that I want Craft to use by default when installing Craft. So these configs are in my project folder of my boilerplate. These configs use Typed Link Field extensively.
What is happening:
If I run
craft/setup
with my project configs in place, it errors every time it comes across a Typed Link Field. I tested it by removing some of those fields and than it just continuous until it reaches another Typed Link Field.Possible leads:
The YAML files show
columnSuffix: null
for the Link field whereas the migration targetsprbospbe
as sufix of the field.Enabling/disabling the new cache option doesn't resolve it, but it seems from the code it may have something to do with it nonetheless.
Logs:
The text was updated successfully, but these errors were encountered: