If a user creates a new form in the live environment on Umbraco Cloud this is a metadata change. The recommended workflow for Cloud is that all metadata changes are made in the dev environment first and then promoted to live. In the case where the user creates a form in live, how are we to merge this metadata change back to dev?
The user may then include that form in content on live (e.g. through RTE macro). All of this causes schema issues when restoring content in local/dev environments.
What's the best practice for bringing forms created in live down?
Indeed! But that is part of the flexibility that Umbraco Forms is supposed to bring - giving editors the power to create forms easily themselves. Creating Forms in staging would still result in the same problem.
Restricting forms to only being able to be created in dev... I hope there's a better solution out there that we're missing :)
Creating a Form in Umbraco Cloud Live Environment and bringing this change to the dev environment
If a user creates a new form in the live environment on Umbraco Cloud this is a metadata change. The recommended workflow for Cloud is that all metadata changes are made in the dev environment first and then promoted to live. In the case where the user creates a form in live, how are we to merge this metadata change back to dev?
The user may then include that form in content on live (e.g. through RTE macro). All of this causes schema issues when restoring content in local/dev environments.
What's the best practice for bringing forms created in live down?
Thanks
Simple - Just don't let editors makes forms in LIVE :-)
You can get yourself into a "chicken and egg" dilemma - Which as of yet, I've not come up with a simple "safe" solution to either.
Indeed! But that is part of the flexibility that Umbraco Forms is supposed to bring - giving editors the power to create forms easily themselves. Creating Forms in staging would still result in the same problem.
Restricting forms to only being able to be created in dev... I hope there's a better solution out there that we're missing :)
For anyone that comes across this thread there's an issue on the tracker for this:
http://issues.umbraco.org/issue/UAAS-706
is working on a reply...