-
Notifications
You must be signed in to change notification settings - Fork 60
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
Forms losing layout in upgrade #1608
Comments
I'm sorry this happened @BrandonJamesBorders. There is a migration that is supposed to take care of this... is there any chance you didn't run the migration before viewing the forms in the front end or form builder? 🙂 |
I don't believe so. Locally I upgraded via the craft CLI, and it happened there. I did not notice (shame on me) and pushed it to production, the pipeline ran the
I restored a snapshot just now and tried to get the error to happen again and was unable to reproduce. 🤷 |
Hmm, that is interesting. So to confirm, you tried duplicating the issue again now but it didn't happen? I haven't seen this happen to anyone else yet, but I've noted this for us to check into. I'm also thinking we will create a fallback to something like Flexbox in the event a formatting template is missing or invalid. I imagine it would be better to get an incorrectly styled form than a broken page. 🙂 |
That's correct. A fallback would be a smart thing to add! |
What happened?
I upgraded freeform from
5.5.10
to5.6.8
alongside a craft upgrade from5.4.3
to5.4.9
.During the upgrade, all our flexbox forms "lost" their layout setting. Forms using other values were not impacted.
Frontend error:
Form settings:
Resaving the form settings with the value "Flexbox" resolved the frontend error.
I inspected a DB backup and noted that this line is probably the culprit in the
freeform_forms
table andmetadata
column.Before:
"formattingTemplate": "flexbox.twig",
After setting it it becomes:
"formattingTemplate": "flexbox/index.twig",
Freeform Edition
Pro
Freeform Version
5.6.8
Craft Version
5.4.9
When did this issue start?
After upgrading from older Freeform version
Previous Freeform Version
5.5.10
The text was updated successfully, but these errors were encountered: