Skip to main content

A DD4T.net Implementation - A Simple Publication Resolver

In previous posts I referred to a utility method GetPublicationUrl. This method simply looks up the current request path and returns the first two levels under the root. In my current implementation it is these two levels that identify the Publication.

For example, for URL path /zh/cn/products/abc.html, method GetPublicationUrl returns "/zh/ch/".

In different implementations, it could be that only the first level of the URL path represents the Publication URL, but that is a matter of choice and URL design.

The code below show casts the simple GetPublicationUrl method, which applies a regular expression pattern to the given (current) URL path. The regular expression pattern matches only if the path starts with slash and is followed by two characters, followed by slash, followed by two characters, followed by slash. In this case, it extracts the 2 level nested folders and returns them.

public static class UriHelper
{
    private static readonly Regex PublicationUrlRegex = new Regex("^(/../../).*");

    public static string GetPublicationUrl(string urlPath)
    {
        string result = "/";
        Match match = PublicationUrlRegex.Match(urlPath);
        if (match.Success)
        {
            result = match.Groups[1].Value;
        }

        return result;
    }

    public static string GetPublicationUrl(HttpContextBase httpContext)
    {
        return GetPublicationUrl(httpContext.Request.Path);
    }

    public static string GetPublicationUrl(HttpContext httpContext)
    {
        return GetPublicationUrl(httpContext.Request.Path);
    }
}

Why would such a method be helpful? The reason to use such method is support for multiple website. In Tridion, we represent different websites as different Publications and each Publication is identified by an ID and a URL root. If we know, or if we are able to read this Publication URL, then all our pages become relative to this Publication URL. This makes is very easy to just reuse the same application code in order to serve many different websites (or locales). In my current implementation I used GetPublicationUrl with Navigation, Labels, or simply loading any kind of resource that is configurable in a central repository, and I don't need to worry about which repository or context the resource is defined in.

However, this method only resolves half way a Publication URL. In fact, it doesn't actually do any resolving. It simply provides a context for a given general URL. A proper Publication Resolver would provide mappings between Publication ID and Publication URL and vice versa. But more information about a proper Publication Resolver is available in post Dynamic Publication Resolver.


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