Sitecore Pilipinas

If you were wondering how a non-bi-directional SPIF works in different use cases, you may want to look at the table below based from my testing. # Sharepoint Changes Supported? SPIF Notes 1 Folder created Y Folder created Do not name the folder or file with special chars like "-" 2 Folder deleted Y Integration folder is deleted This deletes any items in the folder 3 Folder renamed N Rename not supported Refrain from renaming folders in Sharepoint to avoid confusion - it wont get renamed in SC Folder is still connected and any items added or updated under it gets syncd   3.1 Upload File   Y File is pulled into SC similar to #5 Still syncs even though folder name is different 4 Folder Moved? N Folder is deleted Gets recreated as a new folder in the target location and any items under it 5 File uploaded Y File is pulled to SC ...

We recently had a requirement when one of our external vendors required that our media URLs should not include the "~" in the link as their system could not process those correctly. I found a few articles in the web, but most of them would suggest changing the default behavior, i.e. any "new" media item would have the 'new' replacement character though still supporting the tilde "~". Based on the web articles, I started with the following config keys and section: Media.RequestExtension Media.MediaLinkPrefix customHandlers We did not want to change any of the default behaviors, we just needed a way to make Sitecore support the additional URL media prefix. While sifting through the configuration, I chanced upon the following section: <mediaPrefixes>  According to the comment above it: Allows you to configure additional media prefixes (in addition to the prefix defined by the Media.MediaLinkPrefix setting)            The ...