What steps will reproduce the problem?
1. Call AddBinary with e.g. a pdf.
2. Call AddBinary with the same component with e.g. an XML stream with a
different mimetype ("text/xml")
3. Retrieve the binary from DD4T, the mimetype of the pdf appears to be
"text/xml", whereas the expected output is mimetype "application/pdf".
DD4T version 1.0 is used with Tridion 2011SP1HR2.
Call to add binary (for the XML file) is as follows:
binary = m_Engine.PublishingContext.RenderedItem.AddBinary(item.GetAsStream(),
CreateIndexDataFilename(filename), variant, comp, mimetype);
In the transport package the "binaries.xml" file contains the following:
<Binaries>
<Binary Id="tcm:163-25731">
<Path>\media\pdf_title_tcm163-25731.pdf</Path>
<URL>/media/pdf_title_tcm163-25731.pdf</URL>
<Type>application/pdf</Type>
</Binary>
<Binary Id="tcm:163-25731" VariantId="searchData">
<Path>\media\pdf_title_tcm163-25731_pdf.indexdata</Path>
<URL>/media/pdf_title_tcm163-25731_pdf.indexdata</URL>
<Type>text/xml</Type>
</Binary>
<Binary Id="tcm:163-25731" VariantId="searchData">
<Path>\media\pdf_fixed_title_pdf.indexdata</Path>
<URL>/media/pdf_fixed_title_pdf.indexdata</URL>
<Type>text/xml</Type>
</Binary>
</Binaries>
Original issue reported on code.google.com by clemens....@hinttech.com on 22 Apr 2015 at 10:40
Original issue reported on code.google.com by
clemens....@hinttech.com
on 22 Apr 2015 at 10:40