-
Notifications
You must be signed in to change notification settings - Fork 1
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
Error when trying to push content to remote server #247
Comments
Hi, We had an issue (with the config property on non-windows builds), but it was fixed in uSync.Forms v13.4.1 so if you upgrade to that it should be OK ? |
That did the trick! Thanks. |
We did see an issue after pushing actually, where any form with the same name seemed to have merged with each other. The structure was:
Forms with duplicate names in Folder B moved some of their fields/workflows into the form with the same name in Folder A, and vice versa in some cases. Unique named forms were unaffected. Does the form sync/comparison need to have a unique name? |
@karltynan I think i fixed this issue when working on KevinJump/uSync.Forms#22 if you can check and let me know. |
Describe the bug
When trying to push to a remote server, I get the following error:
I have a new root node (+ children) on staging I'd like to promote to production. No other nodes on staging are on production, I am just moving this one for now.
Not sure if it is something to do with the FormPicker or not? I do recall at some point in the past seeing an error/warning in uSync area about the form picker did not have a valid mapper (or similar).
The only other thing that might be worth noting, but doesn't feel applicable, is we have enabled external login providers.
We have seen this working before, so not sure if this is something new.
Version (please complete the following information):
Screenshots
The text was updated successfully, but these errors were encountered: