Or, if you'd like to avoid the calls in xslt, register for save events on documents, check doc type and set a read-only property (label) with filesize of upload -> bit of a hack, but all work is done in backend and can be retrieved in xslt quite fast.

If you don't like to show the bytes field on the doc type, think @ismayat has done some work on hiding properties from a user (think it was done in jquery talk)

Might be quite some overhead tho...

Cheers,

/Dirk

Thinking about Dirks suggestion....

Maybe your event handler just checks if there are any properties of type Upload and then appends "_umbracoBytes" and updates the properties accordingly.

Therefore if your upload control was called 'ImageFile' the event handler would set 'ImageFile_umbracoBytes' to the filesize property.

This should then make the solution quite flexible.

I think it's better to do this check once and cache the values than check the filesize every page load.

Thanks, guys! I was pulling my hair out on this one and you all presented the voice of sanity and good advice when I needed. Thanks!

I'm marking Thomas' answer as the solution because it is the one I used on the site. It was quick and easy to implement, right inside my xslt macro. Performance is very good and I'll be caching this macro heavily as well.

If performance does ever become an issue I'll create an event handler to write the upload size for each control as Dirk and Chris suggested, as that will maximize performance.

Here's the relevant bits of the xslt macro for reference:

<xsl:template name="downloadSize">
    <xsl:param name="productVersionNode" />
    <xsl:variable name="filePath">
        <xsl:choose>
            <xsl:when test="string(data[@alias='uploadStandard']) != ''">
                <xsl:value-of select="data[@alias='uploadStandard']" />
            </xsl:when>
            <xsl:when test="string(data[@alias='uploadPortable']) != ''">
                <xsl:value-of select="data[@alias='uploadPortable']" />
            </xsl:when>
            <xsl:when test="string(data[@alias='uploadPortableU3']) != ''">
                <xsl:value-of select="data[@alias='uploadPortableU3']" />
            </xsl:when>
            <xsl:when test="string(data[@alias='uploadSlim']) != ''">
                <xsl:value-of select="data[@alias='uploadSlim']" />
            </xsl:when>
        </xsl:choose>
    </xsl:variable>

    <xsl:if test="string($filePath) != '' ">
        <xsl:text>(</xsl:text>
        <xsl:value-of select="ps:uploadFileSize($filePath)" />
        <xsl:text> kb)</xsl:text>
    </xsl:if>
</xsl:template>

<!-- =========================================================== -->

<msxml:script language="CSharp" implements-prefix="ps">
    <msxml:using namespace="System.IO" />
    <msxml:assembly name="System.Web" />
    <msxml:using namespace="System.Web" />

    <![CDATA[
    public String uploadFileSize(String filePath) {

        if ((filePath != null) && (filePath.Length != 0)) {
            String localFile = HttpContext.Current.Server.MapPath(filePath);
            if (File.Exists(localFile)) {
                FileInfo fileinfo = new FileInfo(localFile);
                return (fileinfo.Length / 1024).ToString();
            }
        }
        return null;
    }
    ]]>
</msxml:script>

<!-- =========================================================== -->

cheers,
doug.

I agree that I would like to see the file upload data type store the extra details inside the single data element, rather than across several others.

IE, use xml to save all the properties, various thumbs, etc. 

Thought, Doug, I like your approach! :P

You may want to use my multiple file uploader

Download it here. http://our.umbraco.org/projects/backoffice-extensions/multiple-file-uploader

Thanks

is working on a reply...