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

Error on Settings form #76

Closed
Atyz opened this issue Mar 17, 2016 · 2 comments · Fixed by #77
Closed

Error on Settings form #76

Atyz opened this issue Mar 17, 2016 · 2 comments · Fixed by #77

Comments

@Atyz
Copy link
Contributor

Atyz commented Mar 17, 2016

Hello and thx for your work these days !

I updated my project, and now I get an error when I want to display the built-in settings form :

The type name specified for the service "form.type.settings_management" does not match the actual name. Expected "settings_management", given "Dmishh\SettingsBundle\Form\Type\SettingsType"

You can quickly get rid of this error by replacing this line in SettingsController.php :

$form = $this->createForm('settings_management', $this->get('settings_manager')->all($owner));

by that :

$form = $this->createForm(SettingsType::class, $this->get('settings_manager')->all($owner));

(and add the corresponding use statement)
And then, delete the corresponding service.

Thx again for your work 👍

@rvanlaak
Copy link
Owner

You are on master, and what version of Symfony are you using? My assumption is 3.0, for which we did not finish the deprecation fixing yet. See #72

@Nyholm
Copy link
Collaborator

Nyholm commented Mar 17, 2016

Awesome @Atyz. Thank you for this bug report. You are correct. That would fix the issue.

Would you mind sending a PR?

Atyz added a commit to Atyz/SettingsBundle that referenced this issue Mar 21, 2016
@Atyz Atyz mentioned this issue Mar 21, 2016
Atyz added a commit to Atyz/SettingsBundle that referenced this issue Mar 21, 2016
Nyholm added a commit that referenced this issue Mar 21, 2016
Make the form more SF3.0 compatible, Fix #76
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

Successfully merging a pull request may close this issue.

3 participants