Updated Existing Pipeline to Upload image in Azure blob

 We are uploading the media items in azure blob, after user uploads image sitecore. We are storing the url value in CDN file path field in Sitecore.


Step 1 : First we have to create media item templates under our current site. It should inherit the standard sitecore media item template. The path of standard sitecore media item template : /sitecore/templates/System/Media/Unversioned/



We inherited one more base template _baseMediaExternalPath and it has the field CDN file path. It is used to store image url in azure blob. The reason for creating custom media template, each media item should have the CDN file path field.



Step 2 : Then we have to create config file to update existing pipeline. It will patch(run) the processor, after uploaded image has been saved in sitecore.


We have mentioned custom class file path, Name, Path (sitecore media library item) and list of templates, we want to update template of the new media items accordingly. It indicates, basically sitecore will create image item by using default media template. We are just overriding to update custom media template because the each media item should have CDN file path field. Also, our custom media template inherits sitecore default media template. Each templates has Old and New mapping.

Step 3 : We have to create class file to write the logic for upload image in Azure blob after the images has been saved in sitecore.

Path of the class file : Cirrus.Foundation.SitecoreExtensions.Processor.UploadToAzure

Here, we written the logic to update New template by checking Old template id. Also, we are updating the value to CDN file path field.


Step 4 : The media item should be like below,
,


Step 5 : We should declare the Azure blob related details in config file. It is environment specific. These configuration will get initialized when processor invokes custom class file.


Comments

Post a Comment

Popular posts from this blog

Email Experience Manager (EXM)

Image
Email Experience Manager (EXM) To engage with customers in the website, we can deliver the relevant email messages to the customers at the right time. The Email Experience Manager (EXM) helps you create and deliver bulk email campaigns quickly and easily. The email campaign builder has four tabs each of which represents a step in the process. General On the General tab, you specify the campaign name and description along with the sender's details. Recipients On the Recipients tab, you add lists or segmented lists that you have created in the List Manager. You can also add a list of recipients that have been saved to a file. Message On the Message tab, you define the elements of the email message and this tab contains some important controls. Delivery On the Delivery tab, you have the choice to select the message variant and specify options and schedule.
Read more

Federated Experience Manager (FXM)

Image
The Federated Experience Manager (FXM) is an application that allows you to track visitor interactions and generate analytics information on external, non-Sitecore websites with Sitecore. You can use FXM to implement personalization rules, create goals and events, and implement content profiling on an external website. To enable FXM functionality, a JavaScript tag is added to the external websites. It allows the FXM application to connect the external site's components to the Sitecore Experience Platform. FXM has a dedicated Experience Editor that allows you to assign marketing attributes, implement personalization rules. You can access the FXM through the Marketing Control Panel or through the FXM application on the Sitecore Launchpad. When you have applied the FXM JavaScript tag to an external website, you can assign FXM functionality in one of the following ways: Capture Click Action Add Placeholder Add Page Filter Assign Marketing Attributes For reference :  https://vinayakchau...
Read more