Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Works but fails to show the updated value automatically and returns some JS errors in console #571

Open
acrolink opened this issue Mar 11, 2017 · 6 comments

Comments

@acrolink
Copy link

I have implemented best_in_place for a number field inside my Rails app. The inline editing works, it updates the field in the database but fails to show the updated value (i.e. I need to reload the entire page to display the updated value). Moreover, inspecting the Chrome console shows the following:

Form submission canceled because the form is not connected
PUT http://my-site.com/projects/5 500 (Internal Server Error) ... jquery.self-bd7ddd3….js?body=1:10255

Any idea what might be happening here? Thank you.

@acrolink
Copy link
Author

UPDATE

I have managed to eliminate the 500 error by modifying show.json.jbuilder from:

json.partial! "projects/project", project: @project

to:

json.(@project, :id)

I am still getting the Form submission canceled because the form is not connected warning.. But it looks like everything is working as it should now.

@victorhazbun
Copy link

Is this gem working on Rails 5?

@acrolink
Copy link
Author

acrolink commented Apr 3, 2017

@victorhazbun Yes it does.

@duffyjp
Copy link

duffyjp commented Aug 4, 2017

Hi @acrolink, I'd suggest changing the title of this post to reflect just the Chrome warning message: https://stackoverflow.com/questions/42053775/getting-error-form-submission-canceled-because-the-form-is-not-connected

According to the above Stack Overflow, the warning was added in version 56. I'm on 59 now, and still get the message, although the forms aren't broken as reported by users of 56.

@mirelon
Copy link

mirelon commented May 17, 2018

Chrome 66, still getting this issue.
It seems this gem is discontinued.

@ronhornbaker
Copy link

Chrome 68 here, still getting the "Form submission canceled because the form is not connected" warning in the console. Even though users should never see it, it's annoying.

It should be an easy fix: do something like e.preventDefault() on the form submission.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants