Wallogit.com
2017 © Pedro Peláez
A Symfony2 bundle that provides a form choice and a validation constraint that work with translation domains.
This bundle is no longer maintained. Feel free to fork it if needed., (*1)
This Symfony2 bundle provides a form choice field type and a validation constraint that work with translation domains. You can use all strings of a translation domain as values for a field of your entity. The form stores the translation key in the field., (*2)
For example, we use it with an entity Person that has a field title. We use
a translation domain person_title and maintain all possible titles a person
can have (Mr, Ms, Prof, Dr, and so on) in the translation file. The entity
stores the translation key and the title can thus be translated as needed. We
could even change Mr to Mister without need to change the database., (*3)
This does not replace a choice field that links to another entity. But for simple cases like the above example, you might not want to build an admin interface and store such options in the database., (*4)
php composer.phar require liip/formtranslationchoice-bundle --no-update php composer.phar update liip/formtranslationchoice-bundle
Composer will ask you for the version of the bundle you want to install.
Chose 1.0.* unless you want to lock on a more specific version., (*5)
Load the bundle in your kernel:, (*6)
``` php // app/AppKernel.php public function registerBundles() { return array( // ... new Liip\FormTranslationChoiceBundle\LiipFormTranslationChoiceBundle(), // ... ); }, (*7)
Due to the Symfony2 translator not exposing the translation domains, you need
to use the extended translator provided by this bundle. Add the following to
your project configuration file:
```yaml
# app/config/config.yml
parameters:
#...
translator.class: Liip\FormTranslationChoiceBundle\Translation\Translator
This bundle provides a form widget translation_choice and a validation
constraint TranslationDomainKey that operate on a whole translation domain., (*8)
Warning: When using this, you want to make sure you have complete translation for the used domain, or none at all. This bundle does not merge different languages, but does fall back to the default language if the requested language does not exist., (*9)
The translation_choice field type is based on the core choice and provides
all translations of the specified domain as choices. You can use the options of
the standard Symfony2 choice field type.
It makes no sense to specify the choice or choice_list argument though, as they
come from the translation domain., (*10)
To select the translation domain to use, the translation_domain option is
required., (*11)
/** @var $builder FormBuilderInterface */
$builder
->add('title', 'translation_choice', array(
'translation_domain' => 'person_title',
))
By default, the request locale is used, but you can set the locale option if
you need to override this., (*12)
By default the values are sorted alphabetically. If you don't want them to be sorted use the `sorted' option set to false., (*13)
This bundle provides a validation constraint that ensures that a field has a value that is a key in the specified translation domain. As with all validators, this validator accepts null and empty string as well, so you additionally want a NotBlank validation if empty values should not be allowed., (*14)
use Liip\FormTranslationChoiceBundle\Validator\Constraints as TranslationAssert; // ... /** * @TranslationAssert\TranslationDomainKey(translation_domain = "phone_type") */ private $type;
This bundle is licensed under the MIT license. Please see the file LICENSE for more., (*15)
A Symfony2 bundle that provides a form choice and a validation constraint that work with translation domains.
MIT
form validation symfony2 translation i18n
A Symfony2 bundle that provides a form choice and a validation constraint that work with translation domains.
MIT
form validation symfony2 translation i18n