Hi Dan,

I haven't had a look at Umbraco 4.5 yet and if the syntax changed, so I assume 4.0.* syntax will still work.

Where is the image coming from? Has every one of your pages you are looping through a property with an alias 'photo', which is a media picker?

If so, the following should work:

<xsl:variable name="thumb" select="umbraco.library:GetMedia(data[@alias='photo'], 0)" />

<img src="/brochure{$thumb/data[@alias='umbracoFile']}" alt="current()/@nodeName" />

Other than nodes which have a virtual url media items refer to a physical file on the server, the address of which is stored in the data node with the alias 'umbracoFile'. 

Hope that's what you were after,

Sascha

Sascha,

Your assumption is correct, 'photo' is a property of the pages i'm looking at in the for-each.

I could certainly hardcode /brochure, and replace the ~, but I'd like to fetch the application name.

If I were in a template or user control, for example, i could use

<%= VirtualPathUtility.ToAbsolute("~/media/278/kevinp.jpg") %>

Or simply set the img tage to runat="server".

What I really is a way to do that in the xslt file.

Thanks for your help,

Dan

Oh, I see, obviously you can't use the runat="server" tag in XSLT scripts.

How bout this: create a custom XSLT extension dll with the following method:

public static string GetVirtualMediaUrl(string mediaUrl){

return VirtualPathUtility.ToAbsolute(mediaUrl);         //maybe you need to prefix this with '~'?

}

Then, in your xslt, you can use

<img src="[yourPrefix]:GetVirtualMediaUrl($thumb/data[@alias='umbracoFile'])" />

Otherwise I'm out of my depth I'm afraid... :)

Hi Daniel,

Just for clarifying this, what changes did you make to a default installation? Since you're using a virtual directory, is that only for the media section, or for the complete umbraco installation? Especially in regard to using GetMedia(), cause it shouldn't make a difference if you're using a virtual directory, the GetMedia() should still fetch the correct path of it, right?

Looking forward to your answer!

Cheers,

/Dirk

This is clearly an oversight in 4.5. Could anyone make a Codeplex work item that we need to include support for virtual urls in xslts then I'll add it to 4.5.1 when I'm back from vacation!

Thanks guys,

To answer Dirk's questions,

We've got the entire umbraco installation running in a virtual directory.

umbracoHideTopLevelNodeFromPath is set to false in the web.config, but thats the only change I think might be relevant.

Codeplex entry: http://umbraco.codeplex.com/workitem/28050

@Daniel Nolan What steps did you do to get umbraco to run in a virtual directory?

@Anders Burla Johansen All you need to do is to assign the folder where Umbraco is running as an application in IIS. Umbraco 4.5.1 will have much better support for virtual directories. 4.5.0 have a number of virdir related bugs!

@Niels And thats the only thing? Not change anything in the web.config? Sounds as easy as using umbraco :)

I will wait for 4.5.1 then :p

Sorry to ressurect this post but I've hit a very similar issue. Using 4.5.2, I'm finding that if the images were not initially saved in a virtual directory, then the ~ is stripped out.. intentionally:

if (SystemDirectories.Root == string.Empty)
                            _relFilePath = _relFilePath.TrimStart('~');

I've had a client loading a tonne of data in under a staging server which was not running under a Virtual Directory, and it now needs to be moved to a Virtual Directory for the live site and none of the image paths work correctly.

Anyway got any ideas on resolving this?

is working on a reply...