I needed to calculate the total storage space used across multiple asset sources during my analysis. One of the most critical sources was the Sitecore Media Library, and after some googling, I quickly realized there wasn’t an easy way to calculate the total size directly from the CM server, without involving SQL queries or manual summations from reports. So, I built a simple and effective Sitecore PowerShell Extensions (SPE) script that gives you the total Media Library size in MB directly from the CM interface. No database access required!

Another goal was scored by the SPE-only Alliance!

The Script

Here’s the full PowerShell script that can be run in Sitecore PowerShell ISE:

Output Example:

Total Media Library Size: 1473.92 MB

I hope this little script helps you start the weekend with one less thing on your to-do list! If you give this script a try, please let me know how it worked for you.

And if you have improvements or tweaks, feel free to share them — after all, that’s what makes the Sitecore community so awesome!

TL;DR – If you want to activate the Content Hub Integration with Sitecore XM Cloud Starter Kit demo, this post is for you!

Full Story

Our team in Arke Brazil recently used the “XM Cloud Starter Kit” to quickly spin up a fully functional demo for our clients. We also wanted to demonstrate the native integration between XM Cloud and Content Hub, which is not enabled by default.

If you try, XM Cloud will show the message “The DAM provider cannot be shown. Try refreshing the page. If the error reoccurs, contact your system administrator.”

The steps to enable the integration, shown in the official walkthrough, require changes in the source control repository linked to our XM Cloud environment.

But since we are using the XM Cloud Starter Kit, instead of starting from our own source code implementation, what should we do to change those files?

Don’t worry, follow the steps below and be happy!

1. Run the pre-requisites from the walkthrough, including the creation of a user in Sitecore Content Hub that has the relevant user rights;
2. Follow the steps to configure and enable the DAM connector in your app; This will create 4 environment variables in your XM Cloud; It’s important that you follow the instructions correctly and input your Content Hub configurations correctly in accordance with your installation
3. The third step, “Configure the DAM connection“, is where we need to update files in our source control repository. For that, let’s find out your source repository, clone it and apply the required file changes:
   1. In XM Cloud Deploy, go to Projects > Click on your project > Click at the Details tab – here is where you find the repository account and repository name linked to your XM Cloud App
      
   2. Clone this repository – if you don’t have permission you’ll need to request to the administrators.
   3. Apply the file changes described in the step 3 of the walkthrough;
   4. Commit your changes, push them, and deploy the solution again
4. Run the final step to Configure CORS for DAM; Without this part, the image picker will display the following error:
   
   

When everything is correctly setup, you will now have Content Hub integration working on your Image Picker!

Happy XM Clouding!