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
Exporter media sync packs with UmbracoMediaPath don't import the file #202
Comments
I've inspected the contents of the pack file zip, and have been unable to determine a reason for this. Debug logging has not highlighted anything obvious, apart from a couple of missing lines, specifically
Here is a log dump of a failed import:
And this is a successful import
I would be more concerned about the entry |
Hi, Yeah I suspect its probably the part where we make the media location generic again (e.g /media) but then don't put it back properly. We will take a look and see. |
Hi, we have a fix for this now. and will wrap it up in the next release (this week). |
Woah, can't knock the service here! Thanks for the speedy turnaround. |
Hi, Its actually a bit of both, (for v10 anyway) - generally uSync makes things generic to help move them, but we weren't replacing the So the files will be in a sync pack just in the wrong place if that's true - the quick fix is to move the media files on disk (if you can). to the correct folder - and they should appear in the backoffice. |
Closing in 10.6 and 11.2 releases |
Describe the bug
If using a custom media path (
UmbracoMediaPath
), exported media does not allow importing the actual media file. An entry is created in the Media section, but no media (eg image) file exists.Version (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
appsettings.json
set theUmbracoMediaPath
:/mypath/media/ci4hulet/commander-keen.png
Create
to generate and download a sync pack./wwwroot/mypath/media/ci4hulet/commander-keen.png
Expected behavior
The source file should be imported.
Instead, the Media entry is created, but the source file is missing.
Screenshots
The text was updated successfully, but these errors were encountered: