Skip to main content

A DD4T.net Implementation - Extending the LinkFactory

In my current DD4T .net implementation, I encountered the requirement of having Rich Text Format fields resolved in a custom way. Namely, I had to check whether the type of a RTF Component link is of a wrapper around the actual Component to link to, and if so, resolve the link to the wrapped Component.

An elegant way of doing to is to extend the default DD4T.ContentModel.Factories.LinkFactory and create a new method ResolveRTFLink(string componentUri):

public interface IMyLinkFactory : ILinkFactory
{
    string ResolveRTFLink(string componentUri);
}

The implementing class would extend DD4T LinkFactory and implement IMyLinkFactory:

public class MyLinkFactory : LinkFactory, IMyLinkFactory
{
    [Inject]
    public virtual IComponentFactory ComponentFactory { get; set; }

    [Inject]
    public virtual IModelFactory ModelFactory { get; set; }

At the same time the class must provide an implementation for ResolveRTFLink method:

public string ResolveRTFLink(string componentUri)
{
    string key = string.Format("Link_{0}", componentUri);
    string link = (string)CacheAgent.Load(key);

    if (link == null)
    {
        link = GetRTFUrl(componentUri);
        if (link == null)
        {
            return ResolveLink(componentUri);
        }
        CacheAgent.Store(key, "Link", link);
    }

    return "UnresolvedLink".Equals(link) ? null : link;
}

private string GetRTFUrl(string componentUri)
{
    ModelBase model = ModelFactory.TryGetModel<ModelBase>(componentUri);
    // custom logic to resolve link to 'model'

    return resolvedLink;
}

The mapping of interface to factory singleton instance is specified using Ninject, in class DD4TNinjectModule.cs:

Bind<IMyLinkFactory>().ToMethod(context => new MyLinkFactory()
{
    LinkProvider = context.Kernel.Get<IMyLinkProvider>()
}).InSingletonScope();

Next, we need to call the method ResolveRTFLink. We do this from a helper class that I shamelessly copied from the DD4T libraries. The only modification is to call my own custom resolve method. As you can see this is an extension method for class string:

public static MvcHtmlString ResolveRichText(this string value)
{
    XmlDocument document = new XmlDocument();
    XmlNamespaceManager namespaceManager = new XmlNamespaceManager(document.NameTable);
    namespaceManager.AddNamespace("xhtml", XHTML_NAMESPACE_URI);
    namespaceManager.AddNamespace("xlink", XLINK_NAMESPACE_URI);
    document.LoadXml(string.Format("<xhtmlroot>{0}</xhtmlroot>", value));

    foreach (XmlNode node in document.SelectNodes("//xhtml:a[@xlink:href[starts-with(string(.),'tcm:')]][@xhtml:href='' or not(@xhtml:href)]", namespaceManager))
    {
        string componentUri = node.Attributes["xlink:href"].Value;
        string url = LinkFactory.ResolveRTFLink(componentUri);

        if (string.IsNullOrEmpty(url))
        {
            foreach (XmlNode childNode in node.ChildNodes)
            {
                node.ParentNode.InsertBefore(childNode.CloneNode(true), node);
            }
            node.ParentNode.RemoveChild(node);
        }
        else
        {
            XmlAttribute href = document.CreateAttribute("xhtml:href");
            href.Value = url;
            node.Attributes.Append(href);
            foreach (XmlAttribute attribute in node.SelectNodes("//@xlink:*", namespaceManager))
            {
                node.Attributes.Remove(attribute);
            }
        }
    }

    foreach (XmlNode node in document.SelectNodes("//*[@xlink:*]", namespaceManager))
    {
        foreach (XmlAttribute attribute in node.SelectNodes("//@xlink:*", namespaceManager))
        {
            node.Attributes.Remove(attribute);
        }
    }

    return new MvcHtmlString(RemoveNamespaceReferences(document.DocumentElement.InnerXml));
}

Finally, all I'm left to do is to call the string extension method whenever resolving an RTF field is required. Namely, this is done in one place only -- in extension methods in class IFieldSetExtenstionMethods.cs as described in post IFieldSet Extension Methods:

public static IList<string> ResolveRichTexts(this IFieldSet fieldSet, string fieldName)
{
    return StringValues(fieldSet, fieldName).Select(x => x.ResolveRichText().ToString()).ToList();
}

public static string ResolveRichText(this IFieldSet fieldSet, string fieldName)
{
    string value = StringValues(fieldSet, fieldName).FirstOrDefault<string>();
    return value == null ? null : value.ResolveRichText().ToString();
}



Comments

Popular posts from this blog

Scaling Policies

This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the

Toolkit - Dynamic Content Queries

This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio

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