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.
Hooks for greater customization needed, please
  • I would like to be able to more easily customize Uploadifive. For one, I'd like to control the markup generated for a file queue item. I can see this working as an "event"-like function, only it's passed some key information like the file and its place in the queue, and is expected to return markup. If not supplied, use the default markup. It would also be expected that the returned markup would have elements with certain class names, like for the progress bar or the close button, in order to gain that functionality.

    I'd also like to have hooks available that lets you process various events in greater detail. For example, if the user cancels an upload, it just happens What would be great is if another user-defined function could be called after the the close button is clicked, but before anything else happens. The function would be passed relevant info but the key would be that it's required to return true or false; a false would cancel the default behavior. This could give us an opportunity to use logic to determine what to do next. And if returning false, we could then provide a custom prompt to the user (with our own prompt), and then manually cancel the upload if the user confirms.

    Another example: I'd like to customize the "you exceeded the file limit" notification, rather than using the old-school JavaScript alert. An event for this would be great; perhaps if an event is not set the standard messaging can occur; if not, it's suppressed and the developer can handle it however they like.

    I'm about to dive into the source code in order to make my desired changes. I'd rather not have to do that; I'd like to see some extra options and events that let me just configure a bit more than required to achieve the design I need.
  • OK, I just discovered the "overrideEvents" option. This helps me out on the too-many-items event. So that's good. It almost gets there on the item cancel; it appears that while I can override the default behavior of the item fading away, the item is cancelled regardless. I could be wrong on this; can anyone confirm?