-
-
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
Undefined method safe_append= for nil #3916
Comments
Yeah. The stack trace doesn't help, but I'm guessing it's being called from here. |
Does this error still happens after you removed |
The form's contents are not causing the error. I was able to get that exception with just this: <%= active_admin_form_for [:admin, @property] do |f| %>
<% end %> That is, merely having a |
For me, using semantic_form_for and specifying the builder explictly fixed the error <%= semantic_form_for resource, builder: ActiveAdmin::FormBuilder do |f| %> |
@aennchen solution worked for me with the following slight modification to point to the correct url: <%= semantic_form_for [:admin, resource], builder: ActiveAdmin::FormBuilder do |trip_builder| %> |
Using `semantic_form_for` directly causes deprecation warnings since Formtastic requires more custom configuration now. `active_admin_form_for` is not usable in erb templates at the moment (see activeadmin/activeadmin#3916).
Using `semantic_form_for` directly causes deprecation warnings since Formtastic requires more custom configuration now. `active_admin_form_for` is not usable in erb templates at the moment (see activeadmin/activeadmin#3916).
Using `semantic_form_for` directly causes deprecation warnings since Formtastic requires more custom configuration now. `active_admin_form_for` is not usable in erb templates at the moment (see activeadmin/activeadmin#3916).
Using `semantic_form_for` directly causes deprecation warnings since Formtastic requires more custom configuration now. `active_admin_form_for` is not usable in erb templates at the moment (see activeadmin/activeadmin#3916).
Using `semantic_form_for` directly causes deprecation warnings since Formtastic requires more custom configuration now. `active_admin_form_for` is not usable in erb templates at the moment (see activeadmin/activeadmin#3916).
Using `semantic_form_for` directly causes deprecation warnings since Formtastic requires more custom configuration now. `active_admin_form_for` is not usable in erb templates at the moment (see activeadmin/activeadmin#3916).
Using `semantic_form_for` directly causes deprecation warnings since Formtastic requires more custom configuration now. `active_admin_form_for` is not usable in erb templates at the moment (see activeadmin/activeadmin#3916).
Using `semantic_form_for` directly causes deprecation warnings since Formtastic requires more custom configuration now. `active_admin_form_for` is not usable in erb templates at the moment (see activeadmin/activeadmin#3916).
Using `semantic_form_for` directly causes deprecation warnings since Formtastic requires more custom configuration now. `active_admin_form_for` is not usable in erb templates at the moment (see activeadmin/activeadmin#3916).
Using `semantic_form_for` directly causes deprecation warnings since Formtastic requires more custom configuration now. `active_admin_form_for` is not usable in erb templates at the moment (see activeadmin/activeadmin#3916).
I'm closing this as won't fix. |
For anyone coming here, <%=
active_admin_form_for [:admin, resource] do |f|
f.semantic_errors *f.object.errors.keys
f.inputs do
f.input :url
f.input :community_id
end
f.actions do
f.action :submit
end
end
%> Please also note the |
this worked for me thanks |
I just upgraded an app from using Active Admin b794f4b to b3a9f4b. A form that looks like this:
Started raising this error:
Which is confusing since #3486 was supposed to raise an error to make the upgrade path clear. Any idea what the issue might be? Note that I haven't yet tried upgrading Rails to 4.2, or Active Admin past b3a9f4b.
Rewriting the form to use Arbre fixed the issue, but I should've seen a better error message.
The text was updated successfully, but these errors were encountered: