Cyril Duchon-Doris

Does the javascript really fire on `nested:fieldAdded` ? If you add a line `alert('it fires')`, do you see the message when you click the add a task button ?

Duplicate of #346

Err, why do you have both `form_for` and `nested_form_for` ? Use one of them, but not both. `nested_form_for` is gonna use the helpers provided by this gem (So you can...

I had solved this problem by sending everytime all the form_builders variables in the nested partials with a different name : `level1_f`, `level2_f`.... Therefore i could generate appropriate IDs using...

Might be related to this one ? https://github.com/ryanb/nested_form/issues/288

Try to specify data target : ``` { :target => "#your_association-#{f.index}"} ``` And don't forget to wrap your fields inside a tag with the `.fields` class (You might want to...

I have the same problem. In my case it's more tricky because I use tables nested in a table. My nesting scheme is like this : Etude has_many :phases Phase...

Okay. So if you have a look at the main .js of the gem, you'll see that everything is based on a particular class "fields" that you MUST add if...

Thanks for the fix it works like a charm !

Sorry for the long wait. I still have problems on byebug (9.0.5), will try to use your master branch for a while to see if this happens again.