Cleanup blob storage
This time I want to share a small script that I have created and for which I realized it can be usefull in more scenarios. Sometimes I see blobstorages growing at customers side, with files not in use anymore. It can be the result of a job, or because the storage is used by a couple of developers or because Develop and Test are using the same storage, or... On the other hand there is a "known issue" at Episerver side that it sometimes (or always?) doesn't remove the actual blob when removing the media item via code (read "ContentRepository.Delete(..)")(1). For all these cases I have created this small script. Which basically does only copy the blobs which do exist in the Episerver DB to a brand new clean container.
Unmapped? ContentProviders
The greatness of Episerver is that it is extendable in almost every aspect. The way IOC is using does give you a lot of flexibility and you can write for almost every service your own implementation. In the current world a CMS system doesn't stand on it's own. Especially not when you are in marketing / commerce related landscape. The CMS is not the only place where content is served from. A modern website does present content from different sources like; Video platforms, DAM systems, PIM systems or even other "content networks". We do consult on a couple of integrations where we have the need to deliver from these kind of sources. Content Providers to the rescue. In this post I am going to share some challenges we have experienced down the road, especially in relation on the IdentityMappingService.
Language strategies
Something we have seen at every customer (at least with a multi-lingual / multi-country website) the last years is a challenge on how to handle different languages in your CMS. You will be surprised how many strategies are possible and what kind of decisions you can be made. In this blog post I like to share some default strategies and thoughts about how to setup a multi-lingual / multi-country website.