Skip to main content

Resolve Static Links TBB

By Unknown
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('\\', '/');
}


Labels:

Comments

Post a Comment

Popular posts from this blog

Running sp_updatestats on AWS RDS database

By
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...
2 comments
Read more

Toolkit - Performance

By
This post if part of a series about the File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents performance data that was captured for each major functionality with and without caching Linking, CP Assembler, Component Presentation Factory, Dynamic Content Queries, Model Factory. The data was captured on a 2014 Macbook Pro 15", 16 GB RAM, 2.6 GHz Intel Core i7 running OS X El Capitan. Test methodology: each test was run for 3 minutes and the total number of successful Toolkit API calls was measured. Then the number of calls per second was computed 'with cache' and 'without cache' test runs. Then a cache boost factor was calculated by diving (the number of API calls with cache) / (number of API calls without cache). Each cache test was executed 3 times, with different cache time-to-live values of 1 second, 5 seconds and 0 seconds (eternal cache, no expiration). The rationale is to see what impact different cache expiration/evi...
Post a Comment
Read more

REL Standard Tag Library

By
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...
2 comments
Read more