Search Results

However, the default DD4T controller tries to resolve any url not handled by the binarydistributionmodule, and checks if this URL can be found in the PAGE table. … As the urls of these binaries are not in the PAGE table, dd4t will then return a 404 not found error. …

The answer to this question is not really tridion-related, but can simply be solved using a javascript library. Some plugins are at your disposal (jquery based) http://jquerytools.github.io/demos/ov …

Regarding your question on "Do people typically expose pre-filtered lists of component presentations from their model", I have to say I do like the fact that in DD4T 2 I can create a page model with properties …

You can achieve this easily with DD4T: First, you'll need to create a new component template, and in the component template metadata, specify the name of the controller and action you wish to execute to … This will allow the dd4t componentpresentationrenderer to call the correct action to output your table. …

The problem with multiple doctype declarations can be caused by some standard mvc view behaviour. In your mvc project, you can define a _viewstart.cshtml file. In here, you specify the default mvc "m …

When you get errors like this, it's probable that the dd4t version you are trying to install is built against a different version of the contentdelivery dll. … You can either rebuild the dd4t solution with the tridion dlls you are using (download the source, set the references to your contentdelivery dlls, and build, or you can add the following in your web.config …

YOu should also check the dd4t debug log. DD4T has some built in logging. … value="%date [%thread] %-5level %logger [%ndc] - %message%newline" /> </layout> </appender> <root> <level value="DEBUG" /> <appender-ref ref="RollingFile" /> </root> This will also write some DD4T …

This is explained by Bart Koopman in the following blog : http://www.tridiondeveloper.com/ecl-event-handlers you can add some custom TBB's to your dd4t templates that read the external metadata, and add … these fields to your dd4t xml. …

You can specify the java settings used by your .NET application in two ways : either by making changes in windows registry, or by adding a jvm.xml file with the settings in the bin/config folder of yo …

The problem here is that the DD4T LinkFactory class only looks for regular component links. It only queries the link_info broker table, which does not contain links to binaries. … When we had to implement a similar functionality, we had to customize the DD4T code. …

This function is not a standard functionality that is available in the dd4t dlls, that's why it doesn't work with your setup. The blog post you refer to describes how you can add such functionality. …

Dd4t has some functionality in the tbbs to merge page metadata with metadata from parent items (structuregroups). …

While that solution will work, it's not ideal, as we don't want to modify core DD4T files. … (https://github.com/dd4t/dd4t-2-java/blob/develop/dd4t-example-site/src/main/java/org/dd4t/springmvc/controller/DynamicPageController.java) In line 121, you find this piece of code Page pageModel = …

Regarding the topology mapping and DD4T, the answer is pretty simple : the default dd4t implementation just doesn't use the topology manager for mapping a url to a publication. … DD4T has a PublicationResolver class, which is responsible for detecting the correct publication ID. …

these from the broker render each component, and return the htmlstring to the view Advantage of this is that you could use custom actions to render the components just like you would render any other dd4t …