I have noticed that when performing imports that contain media items multiple folders are created if the paths being imported are a different case. For example, if I have the following filepath:
/images/beacons/filename.jpg
Then the folder structure created in the media sections is as follows:
images -> beacons
However if the filepath is as follows:
/Images/Beacons/filename.jpg
Then two different folders are created as follows:
Image(1) -> Beacons(1)
Is there a way of stopping the import routine creating duplicate folders if the case in the file path is different??
Thanks Richard, that would be great, I don't need to ask the client to ensure they are all the same case if you are able to fix it. I am on holiday myself for 2 weeks from this weekend so hopefully it will be fixed for my return :)
Apologies for the late reply, I was on holiday. That is very strange as I am also using version 3.5.3
The import process consists of a top level definition with two child process definitions with the import file being retrieved by URL.
Any ideas why this would be happening on my instance? For your reference, I upgraded CMS Import from an earlier version by installing the latest package, did I need to do anything else? What other information can I provide to try and track down the cause of the issue?
Media Import is case sensitive
I have noticed that when performing imports that contain media items multiple folders are created if the paths being imported are a different case. For example, if I have the following filepath:
/images/beacons/filename.jpg
Then the folder structure created in the media sections is as follows:
images -> beacons
However if the filepath is as follows:
/Images/Beacons/filename.jpg
Then two different folders are created as follows:
Image(1) -> Beacons(1)
Is there a way of stopping the import routine creating duplicate folders if the case in the file path is different??
Good find, will fix this when back from holiday.
Thanks Richard, that would be great, I don't need to ask the client to ensure they are all the same case if you are able to fix it. I am on holiday myself for 2 weeks from this weekend so hopefully it will be fixed for my return :)
What version of CMSImport are you using? Can't reproduce this in 3.5.3.
Apologies for the late reply, I was on holiday. That is very strange as I am also using version 3.5.3
The import process consists of a top level definition with two child process definitions with the import file being retrieved by URL.
Any ideas why this would be happening on my instance? For your reference, I upgraded CMS Import from an earlier version by installing the latest package, did I need to do anything else? What other information can I provide to try and track down the cause of the issue?
Sorry, also meant to provide you with the Umbraco version
Umbraco version 7.4.3 assembly: 1.0.5948.18141
If you can share the exact datasource i can have a look. best to email support@soetemansoftware.nl
Best,
Richard
Thanks, email has been sent.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.