Closed Mopster closed 5 years ago
When using a custom entity, you must provide a mapping for the value
field as well. I wonder whether this worked before 2.3.0.
@craue that looks to have fixed it, thanks!
It might've not correctly picked up my custom entity before. But I was storing values :-)
I'm having issues with version 2.3.0 with PR #50 Installed this version and it broke my app. Getting the following error :
Class "Craue\ConfigBundle\Entity\Setting" sub class of "Craue\ConfigBundle\Entity\BaseSetting" is not a valid entity or mapped super class.
I had a custom Setting class, I had to shorten the
name
to 191 chars for indexing (multibyte).I did not have anything else in my config.yml or other code.
Checking the change and the readme, I changed my code to
and updated the config.yml to contain :
Then made a DoctrineMigration to rename the
craue_config_setting
table toconfig_setting
But after all that, when getting a value, it returns null. I discovered the entity is not being hydrated correctly (value = null). Any changes to the value (setting a value) is not getting saved to the database.
Am I missing another setting somewhere ?