Timeline for ECL Errors Impacting Entire Instance
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 28, 2017 at 14:27 | comment | added | Lars Møllebjerg | What would change in this case if - or / was encoded differently? | |
| Aug 25, 2017 at 14:36 | comment | added | Andy Ross |
@YuriBondarchuk but the issue is with the ecl encoding !2D; or !2F; rather than - or / and this is a limitation of ecl tridion.. sdl is encoding the uri using !2D and/or !2F instead of using regular url encoding %3D
|
|
| Aug 25, 2017 at 11:40 | comment | added | Yuri Bondarchuk | Yes using path as ID for ECL provider is very bad idea. Two reasons fro this: 1) If file will be moved to other directory its ID will change and all previously used links in ECL will break. 2) ID made from path become long very fast and ECL has limit on ID length. If remote system does not provide proper ID. Best way to use "hash of asset path" as ID. This approach will shorten IDs but it still wil have a problem of assets moved in to other directory. | |
| Aug 23, 2017 at 0:18 | vote | accept | Andy Ross | ||
| Aug 22, 2017 at 14:10 | comment | added | Andy Ross | Perhaps we could use a checksum for the image path..I will investigate. | |
| Aug 22, 2017 at 7:47 | history | answered | Bart Koopman | CC BY-SA 3.0 |