13

If you don't add at least one parent publication when creating it, you will not be able to do so later on. This is one of the restrictions Tridion.


12

By default creating a publication will only add a Building Block folder and Categories and Keyword and it will require you to Create a Structure Group manually. For a publication to act as a parent (or Base) it must have a Root structure group.


12

SDL documentation at this link states: Key A text value that is unique across the BluePrint and that can be used to associate an external resource to the Keyword, for example a product ID. So I guess this answers your question. :) Main idea behind keywords is to classify content across publications with same ID. Therefore, changing its key is not ...


11

It has always been a requirement in Tridion to have a Structure Group to enable Blueprinting. The right question to ask is "why doesn't Tridion create a structure group by default when I create a new publication?" and the answer is a complex and lengthy one... The minor version of the reason why is that, back in the day when Tridion popped out of Arjan Van ...


11

You may want to consider using the Child Publications Only Resolver eXtension from the SDL Tridion World site that was developed by Bart: http://sdltridionworld.com/community/2011_extensions/childpublicationsonlyresolver.aspx You still enable the Publishing Target for the parent, but the parent's items are removed using a Custom Resolver.


10

The classic concept of BluePrinting does not change whether you use DD4T, CWA, or a classic Tridion DWT-based implementation. The only difference with DD4T is that instead of publishing rendered markup (i.e. baked HTML, Java, .NET or whatever server-side language), DD4T's templates publish XML (e.g. when you look at a component's source, just with a bit ...


10

As David said, there is no change to the authoring process for the editors and the Blueprint model is the same. In terms of how the CD looks depends on your requirements and capabilities in terms of scaling and deployment set up. You could have a single web application pointing to a single Broker database which all publications publish to in the model ...


9

In terms of BluePrint design and authoring, nothing needs to change... The process for creating schemas, components and pages etc. remains the same, and the methodology of using multiple BluePrinted publications to, for example, localise and/or translate content remains valid and can be identical to that which you know and love. Architecture wise - things ...


9

To do this you would have to use the content porter tool. Export your content from the cms, when importing you can manage the mapping of the publications. I've personally had trouble with it in the past so I typically modify the package to change the WebDAV paths for the dependencies. Do so with extreme caution though :) Be aware that if the child ...


9

I guess the easy answer is "No, you can't. Live with it." :) The hard answer is that Tridion already has a rather powerful (and complex) conflict resolving algorithm that takes blueprinting into account, and adding the possibility of merging different blueprint trees - which is pretty much what you're asking for - would make that complex logic a lot more ...


8

I was recently asked by a client how you could do something similar. My response to this made the following assumptions: I would have a group or several groups of users that I need to disable their ability to (un)publish a defined set of pages The only place I needed to limit the users ability to (un)publish was in the UI My response contunued with the ...


8

Not a solution to your problem, but OOTB it's possible to add new 'Publication types' directly in the Tridion.ContentManager.Config file as part of the CM machine, a snippet is shown below: <publicationTypes> <!-- Constraints: 1) id and name attribute is unique. 2) id > 1024. Numbers below 1024 are reserved. 3) ...


8

I like Harald's blog post (referred to by Nuno above). But note that the DXA import PowerShell script also supports importing into existing Publications (see the script's parameters). Get-Help .\import.ps1 -detailed


8

Lets start with a few (short) answers: Q: is splitting the DXA Master publication supported A: in short: no. slightly longer: depending on what you expect under supported, but as you already mentioned, if you split it up by doing partial imports, future upgrade import scripts won't know where your items are and might import them in the wrong location. Q: ...


7

There is a simple solution without GUI extensions, if you would drop the requirement that all products have to be in the same folder. Please realize that you need to weigh this against the pain of having to write a GUI extension! Create a special folder for the pages you want to hide in the child Localize this folder in the child and remove all the ...


7

It's not possible to filter items as part of the blueprint process, if your child inherits from a publication, it will receive everything from that publication. You've a couple of ways to solve this: Create the page/content you need in your child publication(s) Create the page in your parent but do not publish the page Write your own logic to ensure that ...


7

When you are talking about best practice in the WCM space it is very vague as this entirely depends on the Business Context and End User experience. Also, above what you are saying may be correct depending on the actual requirements or it may be an overkill. You need to consider following points: Do you have schema which are common to all or majority of ...


7

Tridion Translation Manager requires separate publications. I expect your initial convenience of only having to set up one publication would not turn out very convenient after a short while, but you can of course always copy-paste translations around. :)


6

It always has been a requirement of a BluePrint structure to contain all root items, hence a root Structure Group is also required. The exact reason why I don't know, it's just a given fact. The reason why there isn't a root Structure Group by default in a new Publication, is because in the R5.0 days there were customers who didn't use Tridion for a ...


6

Those Items have the same name and location but were created in different publications right? In that case from a functional point of view those items are different and will be consumed from the same publication (The one that you are creating inheriting from both), that is the reason the Blueprint won't allow that, which is the correct and expected behavior ...


6

In 2011 and up you have the BluePrint Hierarchy option under the BluePrinting context menu, in 2009 this was part of the Where Used option in your context menu. Opening the Where Used in 2009 you will see an additional tab called BluePrint hierarchy which shows the exact same information as you have in 2011 and up. It really is only the location which has ...


6

The Blueprint facilitates localization and translation in Tridion. You certainly can dump all your pages into one publication, but, as Lars mentions, this setup will bite you hard not too far down the road. It seems that what you are looking for is a way to manage your website pages in one publication. A common practice is to setup a main (master) ...


6

To be able to add a Child Publication, you must first create a Structure Group in the Parent Publication (normally an empty Structure Group). This is mentioned here: Tridion 2013 creating a BluePrint structure Alternatively, there are known issues with later versions of the Chrome browser. You may want to try this in another browser. If this fixes the ...


6

In conjunction with BluePrinting, use Folder level security and share only the content that each Group needs to see.


5

Moving items across Publications will always require you to write some code, as you noticed you can use copy/paste only inside a Publication and not across Publications. So you will have to create a new item (as a copy of the original) and update all the links from the original to the new item. There are no ready made database script to perform these kind ...


5

One day, I will remember to create the Root SG in the base!


5

ECL keeps track of Stub Schemas by AppData attached to the Schema The AppData name starts with ecl:stubschema Apparently this AppData was deleted somehow and therefore ECL lost track and tried to recreate the Schema causing the issues you describe.


5

The Distribution URL supports a query string parameter, "sl", which specifies what subtitles to show (presumably if available). See the Online Documentation This value could be held in Publication Metadata or other configuration and appended onto the Distribution URL as appropriate by templating. This could also work for Voice-overs and Backslides.


4

Definitely avoid Page localization, unless it is necessary to localize the URLs (I wish Tridion had a better solution for this), and also avoid content metadata (eg SEO data) in Page metadata, for the reasons you and Ram list already. Personally I don't really like the approach to have separate metadata components for all pieces of content - it seems clumsy ...


4

Consider starting with what your authors' perspective on products to create the content model or relationship between products and channels (publications). The business decision or logic at the right context will then give you the best approach. Central control might imply metadata and CD queries. If maybe the same set of authors manage all products in a ...


Only top voted, non community-wiki answers of a minimum length are eligible