Skip to main content

Enforce Anchor Target TBB

This week's TBB is Enforce Anchor Target TBB. The functionality is to enforce a 'system-wide' anchor target policy. Namely, any fully qualified URLs should open in a new (_blank) target browser window. All other (relative) URLs should open in the same target. More specifically, if there is a target specified for a relative URL, remove it.

Name
Enforce Anchor Target TBB
Type
·    Template in .NET Assembly
Description
Used to:
·    Enforces a certain “target” attribute for the anchor tags depending on their “href” attribute value;
Notes:
This generic TBB expects an Item called “Output” in the Package.
It parses the Output looking for anchor <a> tags. If the anchor’s “href” attribute is a fully qualified URL (starts with “http://” or “https://”), then it adds/replaces “target” attribute with value “_blank”. Otherwise, it removes the “target” attribute, if present.
Finally the transformed Output is saved back into the Package.
Parameters
n/a
Applicable to
Any template where an Item called ‘Output’ exists in the Package

The Code

[TcmTemplateTitle("Enforce Anchor Target TBB")]
public class EnforceAnchorTarget : ITemplate {

    private const string ANCHOR_REG_EXP = "<a[^>]*>";
    private readonly Regex imgRegExp = new Regex(ANCHOR_REG_EXP, RegexOptions.IgnoreCase);
    private readonly TemplatingLogger log = TemplatingLogger.GetLogger(typeof(EnforceAnchorTarget));

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

        foreach (Match match in GetAnchorTags(xhtml)) {
            string anchorHtmlTag = match.Value;
            string anchorHref = utils.GetHtmlTagAttributeValue("href", anchorHtmlTag);
            if (anchorHref == null) // anchor without an href
            {
                continue;
            }

            string target = anchorHref.ToLower();
            if (target.StartsWith("http://") || target.StartsWith("https://")) {
                utils.SetHtmlTagAttribute("target", "_blank", ref anchorHtmlTag);
            } else {
                utils.RemoveHtmlTagAttribute("target", ref anchorHtmlTag);
            }

            xhtml = xhtml.Replace(match.Value, anchorHtmlTag);
        }

        outputItem.SetAsString(xhtml);
    }

    private MatchCollection GetAnchorTags(string xhtml) {
        return imgRegExp.Matches(xhtml);
    }
}


Comments

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