Cocoon | A lightweight theming package for Laravel | Theme library

Your Form should look like this: Basically, you need to close the fields_for loop.

w.WriteHeader(http.StatusCreated) writes the header, cookie is a header, so setting the cookie after writing the header is not-ok.

In other words, any modifications to w.Header() after w.WriteHeader was invoked, will not be present in the HTTP Response Header. http.SetCookie sets the Cookie by modifying w.Header().

ResponseWriter.Header()

Changing the header map after a call to WriteHeader (or Write) has no effect unless the modified headers are trailers.

Related: Modify http.ResponseWriter when passed as a function argument

java.lang.StackOverflowError according to the docs

Thrown when a stack overflow occurs because an application recurses too deeply.

From the stack trace, the recursion can be seen in lines below. ElemTemplate.execute calls TransformerImpl.executeChildTemplates which in turns calls the former thus establishing the recursion:

I'm not really sure what happened and why but I tried doing this on my rails container and I was no longer receiving the said error.

1. docker-compose run --rm bash
2. cd to project directory
3. bundle install

The link_to_add_association needs the form-object (f) from the parent (where the associations are defined). So at the nested level, you need to be aware of the parent-form-object.

Also: we would only want to render the Clone button if the record already exists. Maybe I should explain that better: the form and all Clone-partials are rendered on the server, and thus will not copy fields if they are edited/changed in the form. Is that clear? To be able to do that, we would need more javascript-code, and this might also be a very valid approach, maybe simpler: trigger the link_to_add_association link and in the cocoon:after-insert event we can prefill the fields copied from the to-be-cloned item, if there is one. But, as said, that would be a pure javascript solution.

To remain close to your initial suggestion, your views would look like (I did not copy the entire view)

In your project directory, try installing rails gem install rails -v 4.1.6 and removing the version from the failing gems like (liquid_markdown, gon, etc..) then try running bundle update then bundle clean --force

I think this might be an issue because all the version of these gems are locked inside your Gemfile

Delete the VOLUME line.

The only particularly obvious effect of a VOLUME directive is that it prevents any following RUN command from changing that directory. Declaring a VOLUME in your Dockerfile is almost never necessary (and volumes aren't appropriate storage for source code); you can just delete that line and nothing bad will happen.

You can't call the status method on @development.listings, a collection. You should iterate over the collection and call the method on the Listing instance instead.

You could try to use scale_y_continuous to set your own breaks and labels: