Skip to main content

A DD4T.net Implementation - Custom Binary Publisher (part 2)

In previous post Custom Binary Publisher, I presented the main logic needed to publish our Multimedia Components using custom code in DD4T .net. In this post, I present the Template Building Blocks (TBB) that call the custom binary publisher.

If you take a closer look at the code, you will notice it is basically the same code as the existing TBBs PublishBinariesComponent and PublishBinariesPage. I just created a separate PublishBinariesHelper class that uses the CustomBinaryPublisher described earlier. Calling methods PublishMultimediaComponent and PublishBinariesInRichTextField will call the overridden method PublishItem.

public class PublishBinariesHelper
{
    private readonly CustomBinaryPublisher binaryPublisher;

    public PublishBinariesHelper(Package package, Engine engine)
    {
        binaryPublisher = new CustomBinaryPublisher(package, engine);
    }

    public void PublishAllBinaries(Component component)
    {
        if (component.ComponentType == ComponentType.Multimedia)
        {
            component.Multimedia.Url = binaryPublisher.PublishMultimediaComponent(component.Id);
        }

        PublishAllBinaries(component.Fields);
        PublishAllBinaries(component.MetadataFields);
    }

    public void PublishAllBinaries(Page page)
    {
        PublishAllBinaries(page.MetadataFields);
    }

    private void PublishAllBinaries(FieldSet fieldSet)
    {
        foreach (IField field in fieldSet.Values)
        {
            switch (field.FieldType)
            {
                case FieldType.ComponentLink:
                case FieldType.MultiMediaLink:
                    foreach (IComponent component in field.LinkedComponentValues)
                    {
                        PublishAllBinaries(component as Component);
                    }
                    break;

                case FieldType.Embedded:
                    foreach (FieldSet embeddedSet in field.EmbeddedValues)
                    {
                        PublishAllBinaries(embeddedSet);
                    }
                    break;

                case FieldType.Xhtml:
                    for (int i = 0; i < field.Values.Count; i++)
                    {
                        field.Values[i] = binaryPublisher.PublishBinariesInRichTextField(field.Values[i]);
                    }
                    break;
            }
        }
    }
}

Next, we create the actual TBB classes that use the PublishBinariesHelper -- CustomPublishBinariesComponent and CustomPublishBinariesPage, which extend their DD4T counterparts PublishBinariesComponent and PublishBinariesPage.

public class CustomPublishBinariesComponent : PublishBinariesComponent
{
    protected override void TransformComponent(Component component)
    {
        PublishBinariesHelper helper = new PublishBinariesHelper(Package, Engine);
        helper.PublishAllBinaries(component);
    }
}

public class CustomPublishBinariesPage : PublishBinariesPage
{
    protected override void TransformPage(Page page)
    {
        PublishBinariesHelper helper = new PublishBinariesHelper(Package, Engine);
        helper.PublishAllBinaries(page);
    }
}

Finally, use the custom TBB classes in your Component Template and Page Template, instead of the default DD4T PublishBinariesComponent and PublishBinariesPage TBBs.


Comments

Unknown said…
This comment has been removed by the author.
Unknown said…
I am unable to extend PublishBinariesPage an PublishBinariesComponent. The nuget package used is DD4T.Templates.Base, DD4T version 2.0.8. Should I use the base classes instead?

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven