-
Notifications
You must be signed in to change notification settings - Fork 9
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
Manage my own Translation entity extending Model\Translation #28
Comments
@pom-user Technically, it should not make any difference if you used another entity class than the one provided by the bundle. I guess the only thing is to make sure that your class implements the TranslationInterface. Then you will probably only need to change the asm_translation_loader.model.translation.class parameter. |
@xabbuh Should be move the class parameter as a default into the Bundle config? |
@xabbuh Finally found the time to try and it works perfectly, thank you. |
@victor-paumier You're welcome. What do you actually mean with automatic creation of the default entity? |
@xabbuh I deleted the old translation table in my DB but if I execute doctrine:schema:update --force, the table is automatically re-created even if I use my own entity. |
@maschmann I implemented this modification so the bundle is now easier to extend. |
@quentinsikana Would you like to create a pull request? :) |
@xabbuh I did it! :) |
Is it possible to manage my own Translation entity instead of using the bundle's one? In a lot of case it would be really better for me to have the possibility to link other entities with this one.
Or is there some technicals reasons which force use to do it like that?
Thx
The text was updated successfully, but these errors were encountered: