9

As it was not possible to have a separate application use the SAML Authentication module (see Rick's answer) I had to take a step back and re-think how my custom pages work. Because the custom pages are using the core service, what I really wanted was to make sure that core service calls were done in the context of the authenticated user of the Tridion UI. ...


8

You can't delete the component while it is added as a component presentation to a page. The solution is simple: you should not delete the page, but you should simply remove the component presentation from the page. Once that's done, you can delete it (unless the component is still used elsewhere, or if it is published with a dynamic component template)


8

IIRC, the current implementation for SAML 2.0 authentication uses ASP.NET Session State, which requires: Use of Sticky Session on your Load Balancer (to prevent the same ASP.NET Session ending up on multiple CMS servers) Use of a single Web Application So, creating your own separate Web Application may not work. Can you create a Virtual Directory instead ...


7

No, there is no built-in option to secure a custom page via Tridion itself (i.e. to its users and groups). Some might say that this makes sense, as a custom page is really just a URL that is loaded in an iframe, so if you know the URL then you can probably by-pass Tridion anyway. Of course, if you're hosting your custom page within the same system/...


6

it does get stored on DB from SDL 8.6. you can find the details [APP_DATA] table CM Database. You can use the following code to read the value using core service: var client = CMSession.GetInstance().CoreServiceClient; var appData = client.ReadApplicationData(null, APPDATA_CUSTOMPAGES_ID); if (appData != null) { var ada = new ApplicationDataAdapter(...


6

Yes I've come across this before, is it possible for you to use a URL shortening service or physically reduce the length of the URL? Failing that you could create a local page that immediately redirects to your long-URL page


5

I've done solutions for this in the past... and as usual, there's many ways to peel this cat. While I still believe that component linking, functionally, is really what you need (even if people think it's not what they want), I agree that for certain pages you could use page linking. Solution that works So what I've done quite successfully in the past is ...


5

As Harald said, it is not needed to delete the page to remove the component. Also, if you remove the component presentation from the page, again you would not be able to delete the page and will receive the error "Item is in use". This is because this item although you have removed from the Page but from the Current version only and the older versions of the ...


5

Your question isn't completely clear, but I will try and answer the best I can... I don't understand, which user do you want to track, the one who is doing the checking-in? If yes, you can always get the currently logged in user with the following two snippets: string user = HttpContext.Current.User.Identity.Name; //or string user = global::Tridion.Web.UI....


5

Since you are using SDL Tridion 2013, I'm assuming your are also using DXA 1.6 (as that is the latest release supporting 2013). In the documentation there is a chapter about developing new website elements, which also describes how to create custom models. A custom Page Model example you can find below: package com.sdl.dxa.modules.test.model; import com....


5

The user running the thread (e.g. the IIS Application Pool user) is the only one who needs to be an impersonation user. That way you can call Impersonate, passing in the username, and all subsequent actions will be done as that user.


4

I'll answer the second question first how we can reuse the Tridion search functionality in a Custom Page. Take a look at Core Service, and GetSearchResults (and other related methods for retrieving the results of a search). For filtering take a look at SearchQueryData which is passed in the previous method. As for the first question, Is the same ...


4

As Lars explained in this answer, you can create MM components using EclService. You can access it via mountpoint in Core Service.


4

Check file permission on the Preference folder and custompages.xml Ensure Network Service account has read/write to Preference folder and full control on custompages.xml


4

If we try to understand the HTTP then the HTTP protocol does not place any a limit on the length of a URI. Servers (IIS in your case) are able to handle the URI of any resource they serve, and are able to handle URIs of unbounded length. You will get 414 Error (Request-URI Too Long) status if a URI is longer than the server can handle. You may try by ...


3

Unexpected characters almost always is an encoding issue, and those are very common unfortunately since by default SDL Tridion sets everything to Windows Default, which is CP1252. To change the encoding to UTF-8, you need to make sure that it is set through the entire publishing flow. So starting with the Publication Target, then the Publisher, Transport ...


3

By the sample you put there it doesn't look like your component's XML is well formed (but that could just a mistake copy/pasting here). I would recommend that you create a component first "manually" in the CM, then look at it's real XML, then try to duplicate it in your app. If you're using Tridion 2011 (or 2013 with Legacy Pack), you can check the ...


3

Your HTML seems to be non-compliant. It should have a Namespace declaration in the tags. If you have any issue using XML, you can use answer from frank in the Stack Overflow post How to set content to a component without loading XML in SDL Tridion using core services?.


2

As usual with Tridion, there's about 100 different ways to do this :) I'll start with a simpler one (but with dependencies on your environment) and then a more complex one that should work anywhere. Note: for approach #1 to work you need to use the Tridion Content Database (aka Broker DB) on your delivery side, and ideally have all your 19 publications ...


2

Mr. Huiza has written an article explaining how to use the Tridion Search API to get the list of published items. (in 2013 this is Solr underwater) This would be the fastest way and also return a list of the items with title and id properties. Then you would need to get each item with client.ReadData if you wish to perform actions or get more data. This ...


2

You can find working examples of how to do this on the Tridion practice web site. Check these out: https://code.google.com/p/tridion-practice/wiki/CreateTestContent https://code.google.com/p/tridion-practice/wiki/Baconator


2

You have tagged this question with dxa and in there we also actually use Page links for our include Pages. Since there is no item link field in a Schema possible yet (working on that ;o), we decided to use the relative URL of the Published Page in a text field. No matter what you use, the link will remain an unmanaged link, which is something you need to ...


1

it does get stored on DB form SDL 8.6. you can find the details [APP_DATA] table CM Database. you can use the following code to read the value using core service var client = CMSession.GetInstance().CoreServiceClient; var appData = client.ReadApplicationData(null, APPDATA_CUSTOMPAGES_ID); if (appData != null) { ...


1

Custom pages are stored in CustomPages.xml from below path %TRIDION_HOME%web\WebUI\Editors\CME\Preferences\


1

@Atila already answered most of the API Details for getting version history comment details. As I understand you are doing custom power page for check in / check out the others checked-out items, alternatively you can use this GUI Extention very specific groups can be configured to see that content menu to AdminCheckIn with specific admin privilege ...


1

I realized that the custom page you create in Tridion is just a link, so I created a complete new solution in Visual Studio using WebApi and once it worked locally I uploaded to the server and create a Custom Page (a link) to that new solution (which I moved to the server as published code).


1

With the second option, you'll likely still want a reference from either the linking Component or the Page. This will let you know which Components to update when the page is moved (via the Event System). Technically you don't need to generate new paths or IDs until publishing the linking items. Page IDs would be preferred to keep dynamic page links in ...


1

Please check following Publication Target is set to UTF-8 Delivery weibsite's web.config has following <globalization fileEncoding="UTF-8" requestEncoding="UTF-8" responseEncoding="UTF-8"/>


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