11

If you are uploading images to an existing Folder you can specify a schema for that folder in the CME, after it any image uploaded using Webdav in that folder will use the specified schema. Additionally you can use an event system to execute some code in the Save-Initiated event in order to select the multimedia schema, it will give you more control but ...


8

CoreService provides client StreamDownloadClient to download files from Content Manager. You can use following code to get the binary content as a stream, and once you have stream you can read the stream to find the text. StreamDownloadClient streamDownloadClient = new StreamDownloadClient(); Stream tempStream = streamDownloadClient.DownloadBinaryContent(“...


7

This is normally a database maintenance issue. The most important thing is to ensure that the sp_updatestats stored procedure is being run regularly (I have seen this being done 6 times per day on high volume systems). There is an excellent SDL Tridion World article by Julian on Maintaining SDL Tridion Databases too.


7

The behavior you're describing is consistent with the bug introduced by Chrome 36 (and fixed in the upcoming Chrome 38). SDL has issued hotfix CME_2013.1.0.88115 to address it, ask your system administrator to deploy this fix and the problem should go away. Alternatively you can use a different browser while waiting for the hotfix.


6

You can get the bytes of the document/image/... that was uploaded to the multimedia component. I believe you can get it using this code // MMComp contains the multimedia component - you can get this via a call to the GetObject(tcmuri) function if (MMComp.BinaryContent != null) { var bytes = MMComp.BinaryContent.GetByteArray(); } Now, you have the ...


6

It should be possible to make it faster, but it all depends on implementation. Notice ECL supports two ways of publishing. One is as you mention here - the image stays in the DAM, or is published by the DAM. But it does also support publishing the images through Tridion - and this would most likely be considerable slower than what you have now. When you ...


5

A multimedia type is just a definition of a type of binary file you want to handle in Tridion, it's not a piece of content you can use. You're still missing the following 2 steps: Create or modify an existing Multimedia Schema that allows editors to create content with this new Multimedia Type Create a new Multimedia Component - here you can upload a ...


5

Unless, the multimedia that you are trying to upload is huge in size, You may want to check on the health of your DB. You may want to refer these questions: Timeout in the TridionUploadAssembly Content Porter generating SQL connection error


5

DXA follows the behavior that SDL Web (or Tridion if you will) delivers, when using an External URL in a Multimedia Component, at Publish time, the content of the External URL is fetched and published as a binary. So while this might not be what you expected or wanted, this is considered correct behavior at this time. The idea behind this is that the ...


5

Try adding a customMeta under the filter section: customMeta: { key: "ishtype.object.value", value: "ISHIllustration" } You may also be able to do this in code, using the Public Content API (PCA) client. Something like this: var client = ApiClientFactory.Instance.CreateClient(); InputComponentPresentationFilter inputFilter = new ...


5

Support for Scalable Vector Graphics was introduced in Tridion Sites 9.1: https://docs.sdl.com/816112/750876/sdl-tridion-sites-9-5/content-manager-explorer-and-experience-manager-functionality-introduced-in-------------sdl-tridion-sites-9-1


5

Abdul , make sure you add the mime type to the Allowed Multimedia type


4

Actually, both behaviors may be correct. Whenever you unpublish something, Tridion (using the Resolver mechanism) will try to figure out what needs to be unpublished to remove that object from Content Delivery. Basically, it will check what was used to publish that item in the first place, then go about its business of unpublishing it. Items are never ...


4

Definitely the publishing of the pages will be much faster, as you are not publishing the binaries with the page. As introducing a DAM is a change in the architecture, one thing you could evaluate is publish the binaries separately and do not force the republishing of binaries when publish the page. You can still ensure the binaries are updated in the ...


4

From SDL Tridion 2011 SP1 HR1 onwards you could use a BinaryContentProvider. With this extension point you can implement your own logic to handle external URLs on multimedia components. Here you can implement your own logic to authenticate and download the media. This is documented in the TOM.NET API documentation in the IBinaryContentProvider. Also see the ...


4

Looks like a Windows security issue. My guess is that the appropriate user account only has Write permissions to C:\Program Files (x86)\Tridion\web\WebUI\Editors\CME\Themes\Carbon2\Images\MMIcons. If you give the account Modify permissions, the problem should go away.


4

What you are doing in your Template 1 is publishing the Multimedia Component using the RenderedItem.AddBinary() method. However you don't seem to be doing anything with the Binary object returned (which contains the Binary.Url property). Then in Template 2, you are also adding your Multimedia Component to the package, after which the "Publish Binaries in ...


4

In DXA 2.0 (R2 Data Model), Rich Text Field processing is done on CM-side: see method DataModelBuilder.BuildRichTextModel https://github.com/sdl/dxa-content-management/blob/master/Sdl.Web.Tridion.Templates.R2/Data/DataModelBuilder.cs Indeed, only MM Component Links for img tags are "expanded" by the Default Model Builder. If you want to customize the Rich ...


4

Can you go to the Event Viewer on the CM server and grab the entire stack trace for this error? Couple of thoughts: 1)System.OutOfMemoryException seems would be due to lack of actual system memory, despite your config changes. Look up generic Windows reasons and remedies for this. 2) error states "error downloading file...from ...


4

Not sure if this is helpful, but one way I've retrieved binaries is by first retrieving an "untyped" component (i.e. templateless publishing), and then using the result to find and retrieve any binaries. The second query for binary(ies) should give a URL where the image can be retrieved: query GetUntypedContent { component(namespaceId: 1, ...


3

The published multimedia content exists in the Broker DB under BINARY_CONTENT table. I've confirmed this by querying for content by their Publication Id and Type. This suggested that the image is not being served by IIS or resolved through the web app. I've already confirmed that IIS serves the appropriate file so it's likely done through the web app. We'...


3

You can't do this through the CME interface unfortunately. This used to be possible using the TOM.Net API. I am not sure whether the same functionality is available through the Core Service. Update: As Rick mentions in his comment below, this is still possible through the Core Service As these are multimedia items, you could use WebDav to take them out ...


3

This is a known issue with Tridion SP1 HR1 (TT79280). A hotfix is available here as part of cumulative hotfix CM_2011.1.1.80080.


3

The /images link is configured in your publication settings. Have a look at the addbinary method in the Tom.net api, this publishes the binary and returns the URL that will be used in the published website, it also ensures the file is deployed with the content when publishing.


3

As Jan mention before you have to implement the your custom IBinaryContentProvider and add your authentication logic to the method public void WriteContentToStream(Uri uri, Stream outStream) { ... }


3

When you publish the item, if the template has a call to AddBinary() the binary will be published, and also some metadata indicating that the binary was published with that specific item. If you publish it again, this time without the binary, when it is deployed, the metadata will be updated, and of course will reflect the fact that the item no longer uses ...


3

When wanting to publish a binary with a different name (allowing you to not have the TCM URI appended), you have to make sure you are using the right AddBinary() method. There are two obsolete AddBinary() methods: RenderedItem.AddBinary(Stream, String, StructureGroup, String, String) RenderedItem.AddBinary(Stream, String, String, String) All other ...


3

Media Manager has a restful service where you can retrieve content as JSON. It is possible to completely bypass having Media Manager send you an outlet, and instead grab the JSON, and render the markup yourself. assume a distribution url https://poc5.dist.sdlmedia.com/Distributions/?o=7045941B-0652-49ED-A5A9-240A91636FE5 Switch out Distributions/o= for ...


2

You are loading a new Publication instead of an existing Publication which is why you do not see the path expected (but get the default path, being /Images). Instead of using: imageBaseUrl = new Publication(_engine.GetSession()).MultimediaUrl; use: TcmUri pubUri = new TcmUri("tcm:0-35-1"); imageBaseUrl = new Publication(pubUri, _engine.GetSession())....


2

Given that webdav is "just" a protocol, implementation of anything that is specific to a server (Tridion in this case) would require a custom client-side UI for this. This means that the answer to your question is "No". You can however control which schema will be used by setting: A default schema in your Publication A specific schema as mandatory on a ...


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