-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Forms sometimes become empty #1230
Comments
Having a similar issue with 0.4.3, where the form arbre block returns only the latest input inside f.inputs instead of the whole f.inputs block. |
All form inputs were disappearing after changing f.buttons to f.actions in active_admin 0.4.3 / formtastic 2.2. Things are working again using active_admin master, formtastic 2.1.1 and reverting back to f.buttons for now. |
related to #1224 |
This issue happens in production mode with formtastic 2.1.1 and AA 4b21623 ... I really not have an idea what is the real problem... |
I can confirm that this happens when using f.actions as opposed to f.buttons with Formtastic 2.1.1 and ActiveAdmin 0.4.4. |
Doesn't this have to do with putting a conditional as the last item in the |
@jpmckinney yeah, the correct workaround is avoiding putting conditional as the last item. And I confirm, this is a dupe of #965 |
Closing as dupe. |
When I try render forms, I sometime got an empty page with latest Git master
I set my gemfile to 4b21623 ref because this is a last known good version. I dunno what happened between that and master, but something broken.
Code:
No stacktrace, no info about what happened, just renders an empty form. All requests to models are covered by tests and no problem there.
Env: Ruby 1.8.7 Rails 3.1.3
The text was updated successfully, but these errors were encountered: