-
Notifications
You must be signed in to change notification settings - Fork 638
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
[3.1] Project.yaml import fails if SuperTable fields are present. #3558
Comments
I've just attempted this with a fresh installation, a handful of fields and plugins and the transferring of the config file breaks the site.
|
Can you send the project.yaml file over to [email protected]? Unable to reproduce the issue mentioned in your comment. |
As far as the original issue - how did you copy the |
@andris-sevcenko I don't mind placing it here for reference:
The file was placed in the config folder before running Craft's setup process. |
Ah, before. That's not supported yet. |
Duplicate of #3291 |
Any thoughts on #3558 (comment)? |
I've tried loading it before, after, replacing the content of the existing yaml file as well as deleting and fully replacing. Changes are detected but never applied. |
I installed a fresh Craft 3.1-beta.4, replaced the contents of the What do you mean with "Changes are detected but never applied."? |
I managed to get the yaml file working for the fresh installations by transferring the data in blocks (site groups, sites, email etc) and updating in batches. I've worked out that the issue with transferring my existing site's scaffolding (original issue) is down to custom fields such as super table, not being compatible with 3.1 yet. No error was thrown, I presume it failed because of the super table field and just stopped. |
Would it be possible to run the yaml file through some sort of validator before starting the update? This would then error if the yaml file isn't compatible. |
It's all pretty involved and it's not really possible to wrap up in a transaction, either, because adding new fields adds new columns to tables and MySQL instantly commits any active transactions on schema changes... Thanks for pinpointing it, though. I'll keep this one open and edit the original title and text to reflect the real issue. |
@andris-sevcenko I think this can be closed? SuperTable had done it's updates. And seems to work flawlessly now? |
You are correct! |
Description
When using a project.yaml file generated by an existing site on a fresh installation, the contents of the .yaml file aren't being transferred - sections, fields, globals etc don't then exist in the CP.
I'm not seeing any errors that would suggest an issue with the config file.
EDIT:
Additional info
The text was updated successfully, but these errors were encountered: