Dropzone: AJAX Upload

Hahaha, thank you @Aries!

Hey Ernest R.

I guess everything is looking good here but what about JS? Have you stopped original browser event? You button just submits form that's why you are redirected. You should stop the original submit event with event.preventDefault() depending on how you are doing ajax request!

Cheers!

Hi Vladimir,

I finnaly discard using ajax for create the register, was not worth it for just one field i have to enter.

I tried using the event.preventDefault(), and could stop the submit, but i wasn't able to used inside the class as is used in the example, so i used in the document.ready, but after that i couldn't execut the ajax call, no error, no warning, i guess i wasn't pointing correctly to the mark.

My js script ( added a id to the form)

`
$(document).ready(function() {
document.getElementById("js-add-page").addEventListener("click", function(event){

              event.preventDefault()

});

var pageList = new PageList($('.js-page-list'), $('.js-add-page'));   

});

class PageList
{

constructor($element, $form) {
    this.$element = $element;
    this.$form = $form
    this.pages = [];
    this.render();
    
    this.$form.on('click', '.js-add-page', (event) => {
         console.log('test')
    });

    this.$element.on('click', '.js-page-delete', (event) => {
        var getDelMessage = document.querySelector('.js-del-message');
        var delMessage = getDelMessage.dataset.delMessage;
        confirm(delMessage);
        this.handlePageDelete(event);
    });

    $.ajax({
        url: this.$element.data('url')
    }).then(data => {
        this.pages = data;
        this.render();
    })
}

handlePageDelete(event) {
    const $li = $(event.currentTarget).closest('.list-group-item');
    const id = $li.data('id');
    $li.addClass('disabled');

    $.ajax({
        url: '/admin/delPage/'+id,
        method: 'DELETE'
    }).then(() => {
        this.pages = this.pages.filter(page => {
            return page.id !== id;
        });
        this.render();
    });
}

render() {
    const itemsHtml = this.pages.map(page => {
        return `
        <li class="list-group-item d-flex justify-content-between align-items-center" data-id="${page.id}">
        <span class="drag-handle fa fa-reorder"></span>
        <input type="text" value="${page.slug}" class="form-control js-edit-filename" style="width: auto;">
        

        <a href="/admin/editPage/${page.id}">
            <span class="glyphicon glyphicon-pencil"></span>
        </a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

        <a class="js-page-delete" ><span
                                        class="glyphicon glyphicon-trash text-red"></span></a>
    </li>
    `
    });

    this.$element.html(itemsHtml.join(''));
}

}
`

Thanks Vladimir.

hm... $('.js-add-page') is a form element, so you should listen to submit event instead of click something like this

this.$form.on('submit', (event) => {
    event.preventDefault();
    console.log('test')
});

cheers!

Hey Anton,

This comment might be useful for you, please, take a look at it: https://symfonycasts.com/sc... . But really, having nice JS library that helps to handle multiple uploads is enough. Fairly speaking, upload files one by one technically has less possible problems, and if you have a nice JS library with nice UI and UX - that's perfect. You should not care about how it works behind the scene - all the job is done by JS library. What you do care is UX and that handling single file uploads on the server side is just easier. So, as for me, the ideal scheme for uploading multiple files - have a JS library with nice UX that allows users to select multiple files at once and that uploads those files one by one to the server side where your PHP script handles those uploads.

I hope this helps!

Cheers!

Hey Roberto S. !

Great question :). I cheat.. and I feel great about it :). If I have an upload on some sort of an entity, I *always* will save the original object (e.g. Article) first. It just makes life MUCH simpler. There are bundles out there that have really cool fanciness to save files in a temporary location that you can then read when your form actually submits... but I've never thought it worth the trouble. For an Article, it would look like this:

Add a step 1 where the user at least needs to set a "title" so you have *something* to add to the database. You'll then need to put any "NotBlank" annotations you want in some validation group that will only be activated on the 2nd step. Btw, for that "step 1". I've even seen it where it looks like 1 form, but first you only see the title. Once you type that in, it saves via AJAX and the rest of the form loads.

In the end, the problem you're referring to simply is a tricky one. That's why I like to cheat. There are bundles that can help (I think https://github.com/1up-lab/... has this), but it ultimately comes down to some tricks. For example, you could also allow your related objects to save with a null article_id... store THEIR ids in the session (or, more fancy, return their ids back, and put them in the form as hidden fields) and set them when the form FINALLY saves (and have a process to clean up old records for forms that NEVER got submitted successfully).

Let me know if this helps :).

Cheers!

Hey Skylar!

Hmm, maybe? :) There are two parts to that:

1) First, you'll need to base64 encode the uploaded file data so that it can be sent. That *does* appear to be possible: https://stackoverflow.com/q...

2) Then you need to teach Dropzone to send JSON, instead of the normal format. I'm not sure that's possible. Someone forked the entire library to add it - https://github.com/slothbag... but they changed a lot of core code to make it possible. Someone else "sorta" did it - https://github.com/rowanwin... - but that's a bit of a hack: they are *still* sending a traditional form submit, but with JSON as one of the keys (it's not *really* a JSON formatted request).

So... it looks like... kind of :). If you want an "pure" JSON upload endpoint for some other use (beyond Dropzone), the easier solution might be to have your endpoint support both JSON input and normal, form-submitted input (from Dropzone).

Cheers!

Hey sasa1007!

Haha, we could! But this form would just have one field... and that field would be an instance of an UploadedFile object. So, I'm not sure the form would give us much in this case. But, what do you think?

Cheers!

Hi!!!!

I'm glad that You understand my comment in the right way :-), I enjoy watching this tutorial.

So my idea is to create one entity - Medias, and only in Medias to upload files. Medias will be related to every entity that we need picture (Blog entity, User entity....). From user perspective, user can upload more picture at once in Medias (somehow), and then he can use those pictures (one or more) for blogs or blog or other entity where picture is needed. And at the end I want to copy that entity, and logic for upload from project to project and reuse that, and of course I want to use symfony components(forms). And now when I use symfony forms dropzone trow error that he can find url.

Hey sasa1007!

Makes sense! Honestly, what you probably want is a setup like what we have here - where you use Dropzone outside of a a form to create the Medias and relate it to whatever object you need (you would need to send up some additional flag in the URL to say which object the Media should be related to). But, there are so many variants on how you can want this to look and work.

So, are you creating a traditional Symfony form then adding a Dropzone inside of it? By default, Dropzone will use the action="" of your form tag as the upload URL. You can by passing a url option when you initialize Dropzone. But then, Dropzone isn't really using your form... it's still uploading independently of your form.

That's a long way of saying: what exactly are you trying to accomplish by putting it into a form? What is the user flow you imagine?

Cheers!

Cheers!!