Skip to content

Commit d150087

Browse files
Update 16/umbraco-cms/extending/filesystemproviders/README.md
Co-authored-by: Esha Noronha <[email protected]>
1 parent d146ef9 commit d150087

File tree

1 file changed

+1
-1
lines changed
  • 16/umbraco-cms/extending/filesystemproviders

1 file changed

+1
-1
lines changed

16/umbraco-cms/extending/filesystemproviders/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ By default the MediaPath scheme used by Umbraco is the `UniqueMediaPathScheme` t
149149
{% hint style="info" %}
150150
The folder generated by `UniqueMediaPathScheme` is not strictly unique, as it's based on the first eight characters of the GUID for the media item. In practice, with randomly generated GUIDs, a collision is unlikely.
151151

152-
There is an increased possibility of generating colliding paths if creating media programmatically and setting keys using version 7 "ordered" GUIDs via `Guid.CreateVersion7()`. As such these should be avoided - `UniqueMediaPathScheme` will throw an exception if it detects they have been used. Any manually created keys should use `Guid.NewGuid()`.
152+
There is an increased possibility of generating colliding paths if creating media programmatically and setting keys using version 7 "ordered" GUIDs via `Guid.CreateVersion7()`. As such these should be avoided. `UniqueMediaPathScheme` will throw an exception if it detects they have been used. Any manually created keys should use `Guid.NewGuid()`.
153153
{% endhint %}
154154

155155
You can create your own logic for the path by implementing `IMediaPathScheme` and setting it during composition with:

0 commit comments

Comments
 (0)