Stack Track:
System.ArgumentException: The relative virtual path '~supload/20210817113134en-USes.xlf' is not allowed here.
at System.Web.VirtualPath.FailIfRelativePath()
at System.Web.Hosting.HostingEnvironment.MapPathActual(VirtualPath virtualPath, Boolean permitNull)
at System.Web.Hosting.HostingEnvironment.MapPath(VirtualPath virtualPath)
at Umbraco.Core.IO.IOHelper.MapPath(String path, Boolean useHttpContext) in D:\a\1\s\src\Umbraco.Core\IO\IOHelper.cs:line 105
at Jumoo.TranslationManager.Connector.Xliff.XliffFileConnector.Check(TranslationJob job)
at Jumoo.TranslationManager.Core.Services.TranslationJobService._93.MoveNext()
Sorry to ping again, just wondering if you had a chance to check had been broken previously?
Also something I never mentioned, the translations work fine in our Dev enviroment but it's when it has been upgraded to UAT that we are seeing this error however I don't believe it's a permissions error as I can see the file being uploaded into the xliff_translationsupload folder.
Thanks for the information. I've also realised that the media folder is setup as a virtual directory, but everything saves correctly within the media folder.
I've followed the steps provided and this is the Provider Properties of the translation job in question.
The File Location seems fine, but for some reason the uploadedFile looks to trim the beginning of the path off (which might be intended). But the path the uploaded file actually gets saved into is /media/xliff_translationsupload/FileName
Translation Manager uploading translated content error
Hi,
I am trying to upload a translated file and am recieving a "The relative virtual path '~supload/20210817113134en-US_es.xlf' is not allowed here."
It seems similar to the upgrade issue found on https://github.com/Jumoo/Jumoo.TranslationManager.Issues/issues/13 however we haven't updated to 8.7.2 and are currently on 8.5.0.0 and haven't changed default translation folder.
Any help would be appreciated :)
Stack Track: System.ArgumentException: The relative virtual path '~supload/20210817113134en-USes.xlf' is not allowed here.
at System.Web.VirtualPath.FailIfRelativePath()
at System.Web.Hosting.HostingEnvironment.MapPathActual(VirtualPath virtualPath, Boolean permitNull)
at System.Web.Hosting.HostingEnvironment.MapPath(VirtualPath virtualPath)
at Umbraco.Core.IO.IOHelper.MapPath(String path, Boolean useHttpContext) in D:\a\1\s\src\Umbraco.Core\IO\IOHelper.cs:line 105
at Jumoo.TranslationManager.Connector.Xliff.XliffFileConnector.Check(TranslationJob job)
at Jumoo.TranslationManager.Core.Services.TranslationJobService._93.MoveNext()
Hi,
What version of Umbraco do you have installed, and are you on a hosted platform (e.g Umbraco.Cloud, azure ?)
It might be related to the things we fixed in the later versions, but i am just having a check now to confirm we didn't break something back then too.
Kevin
Hi Kevin,
Thanks for the swift reply!
We're using Umbraco 8.6.1 and no, we're just using the default self hosted 'version'.
Thanks leon
Hi,
Sorry to ping again, just wondering if you had a chance to check had been broken previously?
Also something I never mentioned, the translations work fine in our Dev enviroment but it's when it has been upgraded to UAT that we are seeing this error however I don't believe it's a permissions error as I can see the file being uploaded into the xliff_translationsupload folder.
Kind Regards
Leon
Hi,
yeah there is nothing noted as being fixed for standard media folder. and as you say it works on your dev environment,
so guessing something media ish must be slightly diffrent between dev/live.
if you go to the translation job you are having an issue with and node the job id (last bit of the URL) .
eg. job 1 would have the url
and then try this on the site
it will return the job object. which will look something like:
what actually matters is the providerProperties setting :
and what it says for fileLocation ? - which should be the media folder ?
also check the settings in the xliff connector ?
default is
/media/xliff_translations
the path should have no
~
in it.Hi Kevin,
Thanks for the information. I've also realised that the media folder is setup as a virtual directory, but everything saves correctly within the media folder.
I've followed the steps provided and this is the Provider Properties of the translation job in question.
The File Location seems fine, but for some reason the uploadedFile looks to trim the beginning of the path off (which might be intended). But the path the uploaded file actually gets saved into is /media/xliff_translationsupload/FileName
Hi,
So it seems issue is caused by the virtual directory. Removing the Virtual Directory and reuploading the translation file causes no errors.
Do you know if there could be any suggested fix/workaround other than to remove the virtual directory?
Just an additional note, we're happy to upgrade to the last version if this will resolve the issue :)
Cheers Leon
Hi Leon,
I can confirm this is fixed in 8.7.x versions of Translation manager (which will work with Umbraco v8.6. versions)
I just recreated it with 8.5.0 - and upgraded and it was fixed (you have to upload the file to the job again once its upgraded but it works).
I think the fixes for cloud/azure media we did also fixed this issue.
Hi Kevin,
Just realised I never came back and confirmed.
Upgraded and it uploads fine now!
Kind Regards Leon
is working on a reply...