Geek Answers Handbook

What changes are possible / necessary when transferring Tridion schemas between development environments

I would like to save the definitions of the Tridion schema in an external control system (in this case GIT). To do this, I contact the Tridion content manager via webdav. When I do this, links to other system elements are converted to webdav URLs.

When I have a link to a category, it becomes more complicated as the namespace URI includes an inline link to the publication. Here is an excerpt from webdav viewing one of my schemas:

<xsd:import namespace="tcm:0-3-1/Categories.xsd" schemaLocation="/webdav/01%20Definitions/Categories.xsd"/>

If publication identifiers differ between systems, this will be a problem. My first thought was that looking at the namespace URI is basically opaque, I could just replace it with my own system-neutral value. Unfortunately, it seems that the content manager is parsing the namespace URIs to determine the location of the schema, and if it does not recognize the first part of the string as a URI, the failure persists.

Is there a way to achieve my goal by editing the circuit in some other way? Are there any alternative approaches?

+6
source share
1 answer

I don't know if you can do anything with client-side hook GIT scripts, but otherwise an event handler could do something. When you try to save the schema, you could map the publication that I would make to the published publication.

Not a direct answer, but a suggestion. Perhaps this brings you even more.

+1
source

More articles:


All Articles