Hot answers tagged

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 ...


11

I had this a while ago and seem to remember it being to do with .ASCX files not being allowed to be uploaded in to IIS via WebDav because of Request Filtering. All of the request filtering features can impact content that is uploaded or download through WebDAV I think that this can be changed in the applicationHost.config file <requestFiltering> ...


9

IE contains a feature which attempts to “Automatically detect settings” by making use of the WPAD protocol to discover a web proxy. This is achieved in the following ways: As part of the DHCP configuration received by the host (or) By performing DNS request(s). The Web Client Service (responsible for WebDAV browsing) will perform auto-discovery more ...


7

We have always had issues with the allowed verbs in the IIS Request Filtering module for our company. Look at the web logs for the IIS site and check for any 400 erros around your webdav path. You can also turn on the Failed Request Trace Logging within IIS and it will give you a deep dive through the stack. If it was working before, the upgrade may have ...


6

The forward slash character is a special one in webserver country. Apache rejects %2F characters outright, while IIS (6 - 7.5) always translates it to an actual slash. If you cannot convince editors to replace the forward slash with something else (which is by far the best thing you can do), then you could do two things: For importing content through ...


6

You can start by using HttpUtility.URLEncode Here you have a nice start list of percent encoded characters, although the RFC (3986) is definite. Also bear in mind that there are a few characters which can't be parsed (the forward slash one) unless you do a whole lot of hacking. Others ( * : % & ) require a fix that Microsoft brought out.


5

I got intrigued by this and did some investigations that seem to confirm your findings... If I create a folder, then put a MM item in it, it doesn't show in WebDAV I also get the same warning in Event Viewer about /webdav/blah blah Using that WebDav Url from a CoreService client does load the object, so nothing wrong there If I do the same thing, but ...


5

It is not possible to pass a Webdav URL and get a TcmId using Aguilla. As an option you can implement a WCF service and register it as a model, then you can call to your WCF service passing the WebDav URL to get a TcmUri. Example: service.GetTcmUri("WebDavURL", function success(data) {}, function error(error) {});


5

You can probably try to work with various rules for what needs to be encoded, and indeed some of us would probably enjoy learning about all the exceptions and edge-cases. For practical work, however, you are much better off using Tridion to find the WebDavURL of an item. If you have the Power Tools loaded, you can simply copy/paste the webdav url from the ...


4

In this particular instance it was a problem with a user in Tridion having a name containing a slash '/'. It threw off webdav.


4

RFC 1738 Uniform Resource Locators lists characters which are regarded as unsafe in any URL. These must always be escaped. Beyond that, specific schemes may have additional characters that need to be escaped. A more recent standard: RFC 2396 Uniform Resource Identifiers (URI): Generic Syntax gives more details of various character sets. You could say that ...


4

You have to manually change ALL of the applications \ virtual folders to have only anonymous authentication. The thing is that changing authentication on the root level doesn't change anything on the virtual folders (applications) down the line, if the security on those is different from the root. So you should go and double check all of them.


4

I don't think anything specific to Webbdav url is changed in Web 8.5. Probably underlying framework is handling url encoding a bit differently. If you do Url decoding of both Webbdav paths, you would see two identical strings.


3

The issue is fixed here in Hotfix TT 87728 Release Notes for Hotfix TT 87728 Version: This hotfix is intended for SDL Tridion 2013 SP1. Problem description: WebDAV http handler failing for folders with names the same as a one of the file extensions defined for multimedia types Hotfix description: WebDAV http handler was wrongly determining ...


3

Step one is to make sure that ASCX is a valid mime type (or a valid extension for an existing mimetype), and has a Multimedia schema using it for the folder you are uploading to. In addition, I have seen Visual Studio create lots of temporary files when copying and saving to WebDAV. In order to make saving to WedDAV work, check the event viewer to see what ...


3

It seems that the reason you want a WebDAV URL on the delivery side is so you can query for this component without having to hardcode the Tcm Id into your CD code. However as user978511 pointed out you'll run into issues. The typical way to handle the scenario you describe is to keep the environment-specific attributes in a config file, just like db ...


3

Just a thought... Could it be that the item you have pulled is part of a BluePrint structure and the item is not localized? That could explain why you can read the file but not write it back?


3

SDL Tridion does not do its own authentication, that is delegated to IIS. The same thing counts for when you are accessing SDL Tridion through WebDAV, as the WebDAV server also authenticates the user via IIS. After a user is authenticated, SDL Tridion handles authorization based on what is configured for that user. If the logged in user has no read rights ...


3

My suggestion is to find this Component XML in the Content Porter package - there you'll see all dependencies and will be able to analyze which of them are missing.


3

Yes, with some caveats on the defaults and authorization. The documentation explains the rules for these defaults. Basically, for a folder with a linked Schema to accept a PDF via WebDAV you need the following: The PDF must match (one of) the Mime Type for the folder's Multimedia Schema The Multimedia Schema's should either have: No required fields ...


3

Ok -accorinding to my client it was down to a clash in domains - there own internal one and the one setup when we configured Tridion. The two used the the same name so Windows was defaulting to the internal domain and treating the mapped drive as an internal drive.


3

There is a long history, and I my mind does not recall R5.0 (and maybe even before that) too well, but you have only ever been able to access content with WebDAV. WebDAV is designed for authoring and versioning documents (like images or text). The fact that a page can consist of multiple component presentations, means it is not really a single document, so ...


3

I would suggest writing an event handler that captures the dimensions when the component is saved. You can choose to put this in a metadata field (if it makes sense to have the data visible to, or possibly altered by, the content people). Alternatively - if your core service application is the only user of the data, you might prefer to add it to the ...


2

Normally it will be a Dependency issue, I think you might have missed a category and/or keyword, kindly check if you have imported those as well.


2

The other option is to use Core Service API to fetch the object and get the TCM ID from the object. Core Service has .Read method which can help you get object from web DAV url.


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 ...


2

When I was browsing about your issue, I come across with the below information and thought that it might be useful to you. The issue might be with the "Require Lock for Writing" setting under WebDAV Settings. It needs to be False if clients are connecting to the share directly in Explorer (via mapped drive or Network Place).


2

My understanding is that in webdav this issue would be there unless you manually have it encoded to some character other than \. Can you share what is the actual path shown in the Webdav? Regarding Content Porter; I am not sure about your blueprinting and folder hierarchy but If you are using Content Porter 2009, then try applying following hot fixes - ...


2

Your approach is not entirely correct. It's true that you will not get the proper WebDAV url until component is saved, but you also can't be sure that url you have in metadata is correct at the time of publishing, let's say component is moved, in this scenario it will not be updated. Better approach will be to do something during publishing.


2

It is correct behavior. AssemblyTbbId follows "managed link concept". On saving process definitions Tridion analyzes all external activities, extracts managed links and converts them to TcmUri. TcmUri-s are saved to database as well (also associations are created for whereUsed-WhereUsing functionality). For getting webDavUrls in Script you need to load ...


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