-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Importing Document type does not work #4788
Comments
I'm seeing this as well. |
Hey guys. I was having the same issue. The above pull request will fix your issue. Also, make sure that you've given write permissions on App_Data\TEMP\FileUploads (although you shouldn't have to do that). |
Yep, same bug with v7 and v8 .udt on clean installed solution @coderpros Thank you! |
@ReVoid my pleasure! |
Hi, |
Hi, |
"ExceptionMessage":"Value cannot be null.\r\nParameter name: path2","ExceptionType":"System.ArgumentNullException","StackTrace":" |
Just tested this on 8.1.0 and still seems to be broken? |
Crap! I've tested it right now on clean Umraco 8.1 and it doesn't works at all, nothing happens after file uploading, no error messages, no exceptions, just nothing! :( @nul800sebastiaan Seems, the issue need to be reopened :( |
When Importing document type (filename.udt) it fails with following error:
Reproduction
Steps to reproduce
1 Create a new document type and add at least one property of any datatype.
2 Export document type. It will generate a file with .udt extension
3 Delete the document type from umbraco.
4 Import document type (Settings > Docuemnt type > click on three dots and click "Do Something Else" button and select Import document type)
5 Select .udt file which you exported in #2.
At this point, nothing happens and Umbraco Trace log fills with the above error.
Expected result
Usually, after the selection of .udt file a new screen appears which shows the new document type name and button to import.
Actual result
After selection of .udt file. The import button greys out and nothing happens.
The text was updated successfully, but these errors were encountered: