This forum is a community forum meant for users of the plugin to collaborate and help solve issues with implementation, etc. Unfortunately, as the creator of the plugin, I do not have much time to attend to every request here as this is only a side project and I must work a full-time job to provide for my family. This is how I keep the Flash version free and the HTML5 version low cost.
UploadiFive 1.1.1 has been released which includes a small fix for added support on touch devices including iOS 6 devices.
There's no point in "cancelImg" parameter
  • semenovsemenov
    The "cancelImg" parameter brings a redundant dependency which can be easily avoided. The image should be configured by a user in his CSS file with something like:
    .uploadifyQueueItem .cancel { width: 20px; height: 20px; background-image: ../images/cancel.png; }

    There just isn't any point to have the parameter obligatory.

    Moreover, in some frameworks (e.g. Django) you just can't know the exact location of an image file inside a static script file. In a template, you would write something like {{ MEDIA_URL }}images/cancel.png, which would dynamically put the proper media files prefix (for instance, in dev environment that would be /media/, and in production that would http://cdn.myproject.com/), but you can't write like that in a static script file!
Add a Comment