1

(112 replies, posted in News)

I guess this scenario would be specifically for the custom solution.  Having multiple uploaders that target the same container would be a solution but doesn't seem elegant.  Especially since it ends up being the same code that just has a different id for the "add files" button.  It does seem like the only solution now is to add some hacks in order to reuse the same uploader.

Thanks for your assistance.

2

(112 replies, posted in News)

Is there a way to get the add files (browse) button element from the uploader so support for multiple browse buttons can continue.  Example below of old 1.5.7 method.

uploader.bind('Init', function (up, params) {
        if (up.settings.multipart_params.browse_buttons.length > 0) {
                $.each(up.settings.multipart_params.browse_buttons, function (buttonIndex) {
                    plupload.addEvent(this, 'click', function (e) {

                        var input = document.getElementById(up.id  + '_' + params.runtime);
                        if (input && !input.disabled) {
                            input.click();
                        }
                        e.preventDefault();
                    });
                });
        }
    });


I know the params.runtime doesn't return the actual runtime anymore so that'll be removed.  But it doesn't appear document.getElementById(up.id) returns the element of the browse button anymore.

Did the format of that id change possibly?