10

The thing is that Directory will actually be created on the presentation system and Tridion has no knowledge of what kind of system it could be (Windows, Unix, anything that can run Java). It might be the case that the presentation file system does not allow such characters in the folder name. So to avoid broken deployments Tridion plays it safe and allows ...


8

You should use OrganizationalItemAncestorsFilterData The CoreService API reference (which you can download from here) has a good example on how to do this: OrganizationalItemAncestorsFilterData filter = new OrganizationalItemAncestorsFilterData(); IEnumerable<IdentifiableObjectData> list = client.GetList("tcm:1-2-64", filter);


7

It is is possible to allow additional characters to be used for Directories and Filenames. However your filesystem obviously needs to allow it, and you are required to modify the Tridion System Schema. To modify the system schema, you must edit the cm_xml_usr.xsd file, located inside ..\Tridion\bin\ and modify the regexp pattern inside the name="FileName" (...


4

It is is possible to use international characters in Structure Groups and Filenames. However you filesystem obviously need to allow it, and you are required to modify the Tridion System Schema. To modify the system schema, you must edit the cm_xml_usr.xsd file, located inside ..\Tridion\bin\ and modify the pattern regexp inside the name="Directory" node to ...


3

If you are publishing your pages to the content data store database, another approach would be to create the page with a unique filename and associate a metadata field to it where you store the actual filename (including the relative url to it, for example: /section/subsection/page1.php, /section/subsection/page1.xml). Then to ensure those fields are unique ...


2

I see what you're trying to do but I'm not sure how to get nested Structure Groups via the Content Delivery API in a way similar to Categories and Keywords. Edit: Reading RamG's previous question, I don't think it's possible except via the CD Webservice: https://stackoverflow.com/q/12202380 One approach (hack) might be first getting Pages and then getting ...


2

To achieve this Use-Case, you need to create a Disable Publishing Template as I mentioned in the How to make page not publishable? answer. For your quick reference, below are the Steps to Create a "Disable Publishing" template: Get the user specific message from the Generic component Throw an exception with the "User Specific Message" Message should state ...


2

You have stated that you are aware of this feature with regard to Structure Groups, but have you considered simply cutting and pasting the relevant pages to a structure group where publishing is disabled? This would have an added benefit of making it very clear to everyone which pages were expected to publish and which weren't.


2

To make a specific Page not publishable you will have to create either an event handler or a custom resolver. Personally I would say an event handler would be the best fit for this. Here is an example event handler I wrote a while ago to prevent publishing pages that contained the text "do not publish" in the title. This code is using the SDL Tridion 2011 ...


2

You can localize and unlocalize SGs just like any other item in Tridion. Right-click->Blueprinting->Unlocalize. If you don't see this as an available option, it is possible your rights and permissions restrict localization actions. From your description, it is possible that the localized SG is not the problem. Have you opened your Default Finish ...


2

Just a quick info, in the answer below I will be using the "TMS" acronym for translation management systems. The "actual" SDL TMS I will write with bold letters. Each translation workflow in Tridion corresponds to a workflow in a translation management system (TMS) (be it WorldServer or TMS (am unsure about LanguageCloud)). These workflows are made ...


2

AS the others have indicated not out of the box. Given your requirements (or the reasons for them) aren't too clear I'd offer the following high-level considerations you can always store pages in a SG and make the SG non-publishable if actually publishing is the issue you could catch the publication of these specific pages in an extension point (deployer/...


2

Structure Groups by definition affect the url of the containing Pages, so to put it simply, no. If it's just for logical grouping then you can explore Bundles as they're just a container for items (they have other features like Workflows but that is irrelevant in this case) but they do not affect the url. You could try and override the url of the Pages at ...


2

Sorry to disappoint you, but no, you can only create Structure groups and pages withing a Structure group. Page will always have url based on its structure group path. If you want some pages not seen in certain publications, you might consider organizing them via Blueprint, so that they are seen in some publications, and not in others. UPDATE: Based on your ...


2

[TcmTemplateTitle("XML")] public class XMLTemplate : TemplateBase { public override void Transform(Engine engine, Package package) { base.Transform(engine, package); OrganizationalItemItemsFilter filter = new OrganizationalItemItemsFilter(engine.GetSession()); filter.ItemTypes = new ItemType[] { ItemType.StructureGroup, ...


2

"Resolve shared items with BluePrint mapping" is the setting that will let us have the desired results. By default, this option is not checked.


2

Images do not have a URL until they are published, as mentioned by @Nuno. In your code you'll need to publish the binaries to get a URL you can use either the AddBinary or the PublishBinary method to publish binaries. I'd recommend AddBinary, as shown below: ItemFields metadataFields = new ItemFields(objSG.Metadata, objSG.MetadataSchema); foreach (...


2

As @Bart correctly said, "In Tridion you can't have multiple Pages with the same filename in a single Structure Group". You may be able to achieve this (admittedly a bit hacky), would be to use a generic page extension for your templates like ".page", and then include your real extension in the name, so you end up with something like "/rootsg/subsg/mypage....


1

In Tridion you can't have multiple Pages with the same filename in a single Structure Group, uniqueness of the Page is determined on the filename without its extension, there is no way around this limitation (one could argue that it is wrong, but it is how the system currently works). Through a storage extension, you might be able to change what is ...


1

The structure group name can contain a . but the StructureGroup directory name cannot contain a .. Since the CM runs on Windows, only windows OS valid paths are allowed in SG directory name. If you try create a SG with directory name that begins with . you will end up seeing the following:


1

You can recursively call objSG.OrganizationalItem, till it no longer returns a Structure Group, but a Publication (then you know you have reached the top). You will have to build the path via this (expensive) method yourself, so you might want to consider rewriting the entire function in a TBB using the TOM.NET API. You still have to do the same process, ...


1

If your TBB has a link to tcm:3-3460-4 and you mention that doesn't exist, then somewhere along the lines something strange has happened, especially since you mention that tcm:5-3460-4 does exist. It should be impossible to delete a parent Structure Group and also not possible to link to non existing items. The easiest solution I can think of is to just ...


1

You can't use the Taxonomy APIs to fetch Structure Group data, simply because of the fact that they're two totally different things stored in totally different ways. In Tridion 2011, the only thing you could do on the .Net side of the CD API is query on that published Structure Group data: // Get all pages to construct navigation in this SG and its child ...


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