Skip to main content

Resolve Static Links TBB

This week's TBB is about resolving Component links statically - i.e. at publish time. This is considered terribly bad practice, but sometimes, in the field, it is just what the custmer needs. It really goes against every Tridion principle and it will make the website completely inconsistent (e.g. dead links cannot be prevented).

However, if you need to do it, this it how. The code below reads the 'Where Used' Pages for a Component. It takes the Page publish location URL and constructs a 'static' link to the Page. It will not even check if the page is published.

public string ResolveLinkStatic(Engine engine, Package package, Component component) {
    if (component.BinaryContent == null) { // is Content Component
        XmlElement node = component.GetListUsingItems(
            new UsingItemsFilter(engine.GetSession()) {
                ItemTypes = new ItemType[] { ItemType.Page },
                IncludedVersions = VersionCondition.OnlyLatestVersions
            }
        );
        XmlNamespaceManager nmgr = new XmlNamespaceManager(new NameTable());
        nmgr.AddNamespace("tcm", "http://www.tridion.com/ContentManager/5.0");

        XmlNodeList nodeList = node.SelectNodes("/tcm:ListUsingItems/tcm:Item", nmgr);
        switch (nodeList.Count) {
            case 0:
                log.Error("No page found for resolving Component link " + component.Id);
                return string.Empty;

            case 1:
                return GetUrlForPage(engine, package, nodeList[0].SelectSingleNode("@ID").InnerText);

            default:
                log.Error("Several pages found for resolving Component link " + component.Id + ". Using first page");
                return GetUrlForPage(engine, package, nodeList[0].SelectSingleNode("@ID").InnerText);
        }
    } else { // is Multimedia Component
        return component.Id; // will be resolved later by Resolve Links In Output TBB
    }
}

private string GetUrlForPage(Engine engine, Package package, string pageTcmUri) {
    Page page = engine.GetObject(pageTcmUri) as Page;
    return page.PublishLocationUrl.Replace('\\', '/');
}


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...

REL Standard Tag Library

The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...

Publish Binaries to Mapped Structure Groups

Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...