I'm getting the following error using the "Remove" button on an archived job. I also get this error when trying to remove a canceled submitted job (as part of my testing process).
Message: Illegal characters in path.
Type: ArgumentException
Target site: Void CheckInvalidPathChars(System.String, Boolean)
Source: mscorlib
Stack trace:
at System.IO.Path.CheckInvalidPathChars(String path, Boolean checkAdditional)
at System.IO.Path.Combine(String path1, String path2)
at Umbraco.Core.IO.PhysicalFileSystem.GetFullPath(String path)
at Umbraco.Core.IO.PhysicalFileSystem.FileExists(String path)
at Umbraco.Core.IO.ShadowWrapper.FileExists(String path)
at Jumoo.TranslationManager.Providers.SimpleFile.SimpleFileProvider.<Remove>d__17.MoveNext()
is it possible the old job was created before you moved to cloud-based storage of the files? it might be that the path is complete and because the config is now expecting it on azure (or similar) its failing to delete it ?
I will check to see if we haven't done something silly, but that's what pops into my head.
Unfortunately this happens on new jobs as well. I thought maybe it as a trailing slash issue, and removed the trailing slash from the xliff provider's folder setting, created a job, submitted it, canceled, and removed it. The error message showed up again after confirming to remove the job.
Error when attempting to remove archived job
I'm getting the following error using the "Remove" button on an archived job. I also get this error when trying to remove a canceled submitted job (as part of my testing process).
-Tor
Hi
is it possible the old job was created before you moved to cloud-based storage of the files? it might be that the path is complete and because the config is now expecting it on azure (or similar) its failing to delete it ?
I will check to see if we haven't done something silly, but that's what pops into my head.
Unfortunately this happens on new jobs as well. I thought maybe it as a trailing slash issue, and removed the trailing slash from the xliff provider's folder setting, created a job, submitted it, canceled, and removed it. The error message showed up again after confirming to remove the job.
Yeah, just worked out what we missed when we added the storage updates.
So put a new version of the XLIFF provider out to fixe this issue.
https://www.nuget.org/packages/Jumoo.TranslationManager.Providers.Xliff/2.3.5
is working on a reply...