Skip to main content

Resolve CSS Images in Output TBB

This week's TBB is Resolve CSS Images in Output TBB. This template identifies unresolved image references inside CSS selectors "background: url('tcm:x-yy')", publishes the MMC and replaces the reference with the resolved URL.

I got this TBB from my colleague Eric Huiza, so he gets the credit for it ;)

Name
Render Css Images In Output TBB
Type
·    Template in .NET Assembly
Description
Used to:
·    Resolve references to Multimedia Components TcmUris inside CSS syntax;
·    Publish the MMC and replace the TcmUri reference with the resolved URL;
Notes:
This generic TBB uses the Output item to search for references to MMC TcmUris (or WebDav URLs) inside CSS ‘background’ selectors.
If such MMC TcmUri is identified, the MMC is published (to the mapped Structure Group) and the returned URL replaces the TcmUri reference.
The Output item is rewritten with the resolved URLs.
Parameters
n/a
Applicable to
Any template where an Item called ‘Output’ exists in the Package

The Code

[TcmTemplateTitle("Resolve Css Images In Output TBB")]
public class ResolveCssImagesInOutput : ITemplate {

    private const string CSS_IMG_REG_EX = @"background(-image)?:(\s)*(transparent)?(\s)*(url[\s]*\([\s]*(?<url>[^\)]*)[\s]*\)[\s]*)+";
    private readonly Regex cssImgRegEx = new Regex(CSS_IMG_REG_EX, RegexOptions.IgnoreCase);

    public void Transform(Engine engine, Package package) {
        GenericUtils utils = new GenericUtils();
        Item outputItem = package.GetByName(Package.OutputName);
        string css = outputItem.GetAsString();

        foreach (Match match in GetBackgroundEntities(css)) {
            string uri = match.Groups["url"].Value.Replace("\"", string.Empty).Replace("'", string.Empty);
            string localUri = utils.LocalizeUri(engine, uri);
            Component imgComponent = engine.GetObject(localUri) as Component;
            if (imgComponent != null) {
                Binary binary = utils.PublishBinary(engine, package, imgComponent);
                css = css.Replace(uri, binary.Url);
            }
        }

        outputItem.SetAsString(css);
    }

    private IEnumerable<Match> GetBackgroundEntities(string css) {
        return cssImgRegEx.Matches(css).Cast<Match>().
            Where(w => w.Groups["url"].Value.StartsWith("\"/webdav") ||
                w.Groups["url"].Value.StartsWith("'/webdav") ||
                w.Groups["url"].Value.Contains("\"tcm:") ||
                w.Groups["url"].Value.Contains("'tcm:"));
    }
}


Comments

Popular posts from this blog

A DD4T.net Implementation - Custom Binary Publisher

The default way to publish binaries in DD4T is implemented in class DD4T.Templates.Base.Utils.BinaryPublisher and uses method RenderedItem.AddBinary(Component) . This produces binaries that have their TCM URI as suffix in their filename. In my recent project, we had a requirement that binary file names should be clean (without the TCM URI suffix). Therefore, it was time to modify the way DD4T was publishing binaries. The method in charge with publishing binaries is called PublishItem and is defined in class BinaryPublisher . I therefore extended the BinaryPublisher and overrode method PublishItem. public class CustomBinaryPublisher : BinaryPublisher { private Template currentTemplate; private TcmUri structureGroupUri; In its simplest form, method PublishItem just takes the item and passes it to the AddBinary. In order to accomplish the requirement, we must specify a filename while publishing. This is the file name part of the binary path of Component.BinaryConten

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

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