Most likely your Dynamic Component Template output type is set to HTML Fragment. This instructs Tridion to not do anything with the rendered output as it is plain static HTML.
Change your template output type to REL when storing DCPs in the database, or JSP Scripting if storing them on the filesystem.
You mention this"Also if I put ASP code in the CT this ASP code is showed in the page as text."
If you want to have asp code (i assume you mean asp.net code) and link resolving (which also uses an asp net server control) in a dynamic component presentation, then you should make sure to publish this dcp as an ascx control, not just as a html text fragment. ...
You could test for specific Schema's for example
if (c.Link.InternalLink.Schema.Title == "Multimedia Schema Title")
This would give you more control if the desired output is different based on Multimedia type (e.g. image, document, video, podcast, etc..)
You could also use
Yes, there is. In the cd_link_conf.xml of the (Session-enabled) Content Service there is a OverrideDiscoveryService attribute. If you set that to true, the Content Service will switch back to old-style link resolving using the mappings defined in cd_link_conf.xml and if you don't define any mappings in there, you will get relative URLs.
Unfortunately, the ...
The link in pankaj's answer does have some great points, if that doesn't resolve it, I'd recommend adding the following information to your question:
The DWT code where you perform the HREF to your component link
Confirm the link you wish to link to is published
The language you are using to publish the content asp, rel, etc
An overview of your CD ...
It would be good if you could supplement your question with what you have tried and what research you have done so far!
Will Price has excellent posts on Tridion Developer site related to this here:
Cleaning and Extending Dynamic Linking
Extending Linking for .NET
In essence, there are two parts to this:
Ensuring that URLs without a filename or extension ...
What you can do is create new classes for the 'missing' functionality from the original Tridion.ContentDelivery.Web.UI assembly
you just need to create the class that inherits from the base class
public class ComponentPresentation : Tridion.ContentDelivery.Web.UI.ComponentPresentation
and if you don't override anything, you'll have this available in ...
Since DXA 1.1, Component Links to Multimedia Components are resolved as Binary Links (so a direct link to the MM Component's binary content).
I see you have tagged dxa java, which means that you will need DXA 1.2 (the first official DXA Java release).
The short answer is 'yes' and 'yes'.
The long answer: in your cd_storage_conf.xml you can specify the item type mapping DynamicLinkInfo to use a Content Delivery Database (FKA the Broker DB). While keeping all your other mappings to file system, this ensues that only your linking (i.e. Component, Binary and Page) info will end up in the CD DB.
As Will's articles suggest, using a custom Tag Renderer is one way to do this. It's a clean approach, but does require advanced CMS knowledge and programming skill to implement.
A really really simple approach is to create each Page within its own SG with "index.aspx" or "default.aspx" being the page filename, hence relying on the dafault.aspx/index page ...
Alternatively, you could choose a different prefix for your custom functionality.
It will be more obvious that it's your code and thus less confusing and easier to troubleshoot.
If you use TCDL for your links, you can create a tag handler that transforms tcdl:ComponentLink to your prefix instead of "tridion". If you are instead outputting tridion:...
It appears the Deployer does not resolve tcdl tags inside out, which means it does not support nested tags unfortunately.
However when looking at your construct I would say that is sounds rather expensive to use a Dynamic Component Presentation, just for a single label value.
I would personally create a labels Component and publish that as a resource ...
Whomever did your implementation of Tridion decided that the design of your site would have this limitation of a maximum of two banners.
This is in no way a Tridion limitation, but an implementation choice. Unless someone here was involved in your implementation I strongly doubt you'll find the answer on this site. You should connect to the admin team on ...
Error reading contents of xml file: formdata.xml for session TWF_B1FD2C99DCD508DA73725176F4BA7FE130E06C4F, Premature end of file., Premature end of file.
It looks like above error causes due to the formdata.xml contains invalid XML.
So when it reaches to getComponentPresentation, function gets values as text and not the tcm id.
And also I suspect that:
The fact that you are seeing the correct <tridion:ComponentPresentation runat="server" ... /> tag indicates that the Language of your Publishing Target is set up correctly (ASP.NET) and that your Deployer is configured to transform the Component Presentations' TCDL tags to the correct (.NET) format.
It is difficult without seeing the rest of your ...
I've found a solution (without tridion).
I've added another scheme to the template which was rendered with the component I tried to delete, then I unpulbished the component again and this time it also unpublished to rendered with thing which let me delete the component.
Then I had to unpbulish the template with the extra scheme > remove the scheme and ...
AFAIK, when you create component links in the RTF field, Tridion does not generates the binary link.
You may refer the Process Download Links in Output extension for this purpose.
This was written for SDL Tridion 2011, but hopefully may work for SDL Tridion 2013 as well.
If your website has multiple base URLs, you should indeed configure CD Linking to use relative URLs (as a matter of fact, I don't see why you would ever want to use absolute URLs).
Using absolute URLs with multiple website base URLs just won't work; CD Linking doesn't know your current context and hence can only select an arbitrary base URL.
No need to change the log level on log4j.properties and logging.properties.
As @Eric mentioned, you need to update log level on logback.xml
Sample Logback file looks like,
<?xml version="1.0" encoding="UTF-8"?>
<!-- Properties -->
<property name="log.folder" value="c:/tridion/log"/>
Looks like you are missing an association between the prefix "tridion" and the "Tridion.ContentDelivery.Web.UI" namespace. You could add it at the top of every page or just declare it in your web.config like so (applies to all pages then):
The TextOnFail value is usually set in the TBB's.
To create a TridionLink from a dwt TBB the following code is needed:
<a tridion:href="@@Component.ID@@" tridion:textOnFail="true" class="bottom">
Tridion will transform the code above into a server control (.net or java) based on your env.
In this case the textOnFail is hardcoded, But the value can ...
As far as I have seen, most people place the snippet at the top of the Page Layouts. I understand the point you are making by not embedding the taglib - but out of the box this functionality doesn't exist. I would actually suggest writing a 'language agnostic' TBB that either checks the extension of the page being published, or the output type of the ...
If you are talking about rendering a component link in your page, the fact that the data comes from a component link in your page metadata is irrelevant. Your template is responsible for emitting component linking code, and for specifying the page and component which should be used.
So if you render the component link from the page metadata using the id of ...
I was also facing the similar problem and resolved with the below steps:
We need to use Default Multimedia schema and Chose Multimedia type "PDF" while creating the component. Attach this multimedia component to the 'Internal Link' field of Link schema and publish the relevant page.
Once the page is published you can check and confirm the published content ...
The .NET controls you mention are still shipped and configured the same way.
Since the error is about the tag 'tridion:ComponentLink' not being recognized, I would suggest you check the relevant web.config file on your site and ensure that the 'tridion' prefix is configured correctly:
<add tagPrefix="tridion" ...
When you are using REST setup for CD API's, you don't need cd_storage_conf.xml at client side.
To make sure that Content Service location can be found by clients,
Register "ContentServiceCapability" in Discovery service.
Provide Discovery service URL in Web.configof your client application
Provide ClientId and Client secret (for OAuth) in Web.configof ...
The exception seems to be self explanatory. You are passing an invalid tcm uri.
A tcm uri is of the following format: tcm:publicationId-itemId-itemType
As explained by Will Price in his blog post here: http://www.tridiondeveloper.com/cleaning-and-extending-dynamic-linking
If you are using TCDL tags and want to change their behavior, the best solution then, is indeed to extend the linking functionality at the TCDL level, by creating our own TCDL tag.
It's very easy, you just need to create a .jar file with ...
Looks like you have a classic "index page with summaries/teasers pointing to detailed article pages".
My understanding is that the origin attribute is there to exclude the current page from the Dynamic Linking algorithm, i.e. it is the URI of the page that list the dynamic link (this page). But when you're rendering a DCP used in multiple pages linking to ...