Skip to main content

Why Copy-Pasting your Schemas Is Not a Good Idea

I just noticed something concerning -- I copy-pasted a Schema in Tridion 2011 SP1 HR1 and I noticed the UUID namespace of it did not change. In fact I ended up with two different Schemas having the exact same namespace.

So far, I have not found a case where that breaks, but it not look good to me (i.e. that UUID seems like it was put in place for a reason).

For me, the root nodes of the two Schemas are not the same, but some of the fields are. I believe there can be a clash there.

Still thinking for a use case where that breaks...


ingmaru said…
Will be a PITA if you are making use of XSLT templating :) for Compound it's not going to bother you :)
Peter Kjaer said…
This is a good example of a default value setting expectations.
In this case, the wrong expectations. The target namespace does not have to be unique and it shouldn't be changed automatically when you make a copy.

My guess is that the default value is unique mostly because we didn't think people would want it to be a URL. And since you need the target namespace to have a valid XSD, it must have a value from the very beginning. You can't wait for the user to enter a value.

Speaking of the target namespace: it really should have been added long ago as a field on the General tab.

Popular posts from this blog

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

A 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

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