-
Notifications
You must be signed in to change notification settings - Fork 0
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
Copy form error when configuration key for form storage location is missing from config file #567
Comments
Hi - I'm not able to see this issue in testing having installed the latest version. Could you check please you don't have any cached assets via a hard refresh after "bumping the client dependency version"? Assuming you still see the problem are you able to share what the underlying 500 error is? |
Hi @AndyButland I'm on Umbraco Cloud, When I click the copy button nothing happens and a 500 error is logged. Screen capture below. Full error:
|
Thanks @OwainWilliams - that's annoying, and a little frustrating as unfortunately I still can't seem to replicate it. Part of your stack trace even looks correct - i.e. |
OK, think we've found it... I think you must have this value missing in
This was added in an earlier version to give the option of storing forms in the database or on disk, with the default if not present being to store on disk. So if you add this setting into the file, with a value of false, that should behave as it did when the setting was missing, but will resolve this issue with the copy form function that is currently expecting that setting to be there. We'll patch this for the next release such that it's not required to have in config any more, but meantime as a work around, if you just make sure this setting is present the copy form function should work again without error. |
Just downloaded the new release went to copy a form I dont seem able to - cant click the copy button.
office/backoffice/UmbracoForms/Form/CopyForm:1 Failed to load resource: the server responded with a status of 500 ()
The text was updated successfully, but these errors were encountered: