Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
I'm using the S3 File System Provider to store media files on aws s3. This works for all the media I've added via the media section, but doesn't for the xliff file that Translation Manager generates when using the XLIFF File Provider. The link to in the backoffice results in a 404 because the file is added to the local media folder instead of uploading to s3. This is likely because Translation Manager isn't using file system providers. Details on how to connect to the file system provider can be found here.
While we are able to work around it with ftp, it does make the tool more difficult to use.
Thank you for your time and the wonderful plugin.
yeah that is on our list, we just haven't gotten to it yet..
but the good news is now we have a user request its going to go higher up and get done sooner :)
we might have something before the month is out (fingers crossed)
Yes, you can add a second user to that list Kevin! Our site is using Azure Blob storage for media (Our.Umbraco.FileSystemProviders.Azure.AzureBlobFileSystem).
We implemented the similar work-around that Jesse does, i.e. configure TM to use a folder other than the default media.
Perhaps Kevin you could add a note to that effect in the docs somewhere until this has been looked at?
Thanks for the update Kevin.
Thought of a better solution to this problem until it's compatible with file system providers. Just pointed the xliff provider at a different directory, which avoids this issue.
I had a similar problem and came to the exact same conclusion/work-around. Only just seen your post as otherwise would have mentioned it sooner!
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted