a2lix / autoformbundle Goto Github PK

Dead bundle? = dead a2lix/TranslationFormBundle?

After using 0.1-beta.1@dev looks like its working.

Hello, I get this error on shared hosting.

Fatal error: Uncaught TypeError: Return value of A2lix\AutoFormBundle\DependencyInjection\A2lixAutoFormExtension::load() must be an instance of A2lix\AutoFormBundle\DependencyInjection\void, none returned in /vendor/a2lix/auto-form-bundle/src/DependencyInjection/A2lixAutoFormExtension.php:37 Stack trace: #0 /vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/MergeExtensionConfigurationPass.php(71): A2lix\AutoFormBundle\DependencyInjection\A2lixAutoFormExtension->load(Array, Object(Symfony\Component\DependencyInjection\Compiler\MergeExtensionConfigurationContainerBuilder)) #1 /symfony/symfony/src/Symfony/Component/HttpKernel/DependencyInjection/MergeExtensionConfigurationPass.php(39): Symfony\Component\DependencyInjection\Compiler\MergeExtensionConfigurationPass->process(Object(Symfony\Component\DependencyInjection\ContainerBuilder)) #2 /vendor/symfony in vendor/a2lix/auto-form-bundle/src/DependencyInjection/A2lixAutoFormExtension.php on line 37

getting this error

No locales were configured, but expected at least the default locale en. Perhaps you need to add it to your a2lix_translation_form.locales bundle configuration?

using symfony 6 and knp behaviour bundle

Hi there,

I'm using TranslationFormBundle and its working perfectly. In my case; i'm using the TranslationsType in Sonata to add translated field. I want to use a ManyToOne field as translated field; and I do get an error. The error is class xxx doesn't have a field yyy. Where yyy is the ManyToOne field.

After a bit of researching I found a solution. If I remove the following check (https://github.com/a2lix/AutoFormBundle/blob/master/src/ObjectInfo/DoctrineORMInfo.php#L65) everything is working fine.

My question is; can this check be removed? Or why is it there?

Hi i like this bundle and use it for my own "fbeen/simplecmsbundle". But composer complains about the dev-master version. Would you launch the first release for me and update the bundle on Packagist?

Many thanks in advance

The service "a2lix_auto_form.manipulator.default" has a dependency on a non-existent service "doctrine.orm.default_entity_manager".

In my case I have multiple doctrine connections and then entity manager. My default entity manager service name is not default but something like "commonDb". Is it possible to add an option configuration to say witch one we want to target ?

Hi, thanks a lot for this bundle and TranslationFormBundle, it helps me in many projects !

So, I have a little bit complex context. I work with EasyAdminBundle:

I have a VideoBlock class, translatable (and a VideoBlockTranslation class). In VideoBlock class I have a $videoMedia property, which is declared as follow:

/**
 * @ORM\Embedded(class="App\Entity\CatalogMedia")
 */
private $videoMedia;

CatalogMedia extract:

/**
 * @ORM\Embeddable()
 */
class CatalogMedia
{
    /**
     * @ORM\Column(type="string", length=255, nullable=true)
     */
    private $filename;

    private $file;

// ...

It works like a charm, but now I would like to be able to upload a video for each language. Basically, move $videoMedia in VideoBlockTranslation. Well, here is the problem. If I do this, I can't make my form works. The form is configured like this:

// ... EasyAdmin entity config
            form:
                fields:
                    - { type: 'group', css_class: 'col-md-6', icon: 'gear', label: 'Configuration' }
                    - { property: 'name', label: 'Nom' }

                    - { type: 'group', css_class: 'col-md-6', icon: 'image', label: 'Media' }
                    - { property: 'videoMedia', label: 'Vidéo', type: 'App\Form\CatalogMediaType' }

                    - { type: 'group', css_class: 'col-md-12', icon: 'flag', label: 'Traductions' }
                    - property: 'translations'
                      type: 'A2lix\TranslationFormBundle\Form\Type\TranslationsType'
                      type_options:
                          label: false
                          fields:
                              title: { label: 'titre' }
                              content: { label: 'paragraphe' }

If I move videoMedia, under translations...fields, Symfony tells me that it can't find videoMedia property in VideoBlockTranslation class 🤔

May be I missed something, but I think that the problem is under AutoFormBundle and about Embedded properties.

Thanks for helping

Is possible to add support by your bundle in near future?

a2lix/auto-form-bundle 0.1-beta.1 requires symfony/form ~2.8|~3.0 -> satisfiable by symfony/form[2.8.x-dev, 3.0.x-dev, 3.1.x-dev, 3.2.x-dev, 3.3.x-dev, 3.4.x-dev, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.0-BETA1, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.0-BETA1, v3.1.0-RC1, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.0-BETA1, v3.2.0-RC1, v3.2.0-RC2, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.0-BETA1, v3.3.0-RC1, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.0-BETA1, v3.4.0-BETA2, v3.4.0-BETA3, v3.4.0-BETA4, v3.4.0-RC1, v3.4.0-RC2, v3.4.1, v3.4.2] but these conflict with your requirements or minimum-stability.
- a2lix/auto-form-bundle 0.1-beta.1 requires symfony/form ~2.8|~3.0 -> satisfiable by symfony/form[2.8.x-dev, 3.0.x-dev, 3.1.x-dev, 3.2.x-dev, 3.3.x-dev, 3.4.x-dev, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.0-BETA1, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.0-BETA1, v3.1.0-RC1, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.0-BETA1, v3.2.0-RC1, v3.2.0-RC2, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.0-BETA1, v3.3.0-RC1, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.0-BETA1, v3.4.0-BETA2, v3.4.0-BETA3, v3.4.0-BETA4, v3.4.0-RC1, v3.4.0-RC2, v3.4.1, v3.4.2] but these conflict with your requirements or minimum-stability.
- a2lix/auto-form-bundle 0.1-beta.1 requires symfony/form ~2.8|~3.0 -> satisfiable by symfony/form[2.8.x-dev, 3.0.x-dev, 3.1.x-dev, 3.2.x-dev, 3.3.x-dev, 3.4.x-dev, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.0-BETA1, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.0-BETA1, v3.1.0-RC1, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.0-BETA1, v3.2.0-RC1, v3.2.0-RC2, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.0-BETA1, v3.3.0-RC1, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.0-BETA1, v3.4.0-BETA2, v3.4.0-BETA3, v3.4.0-BETA4, v3.4.0-RC1, v3.4.0-RC2, v3.4.1, v3.4.2] but these conflict with your requirements or minimum-stability.
- Installation request for a2lix/auto-form-bundle 0.1-beta.1@dev -> satisfiable by a2lix/auto-form-bundle[0.1-beta.1].

Hello,

I have an entity Person which inherits a Thing entity, based on schema.org pattern.
I also have a PersonTranslation which inherits a ThingTranslation entity.

ThingTranslation entity declares the description attribute.
Person entityTranslation declares the jobTitle attribute.

Then, on the PersonType form type, using ->add('translations', TranslationsType::class works fine.

The issue is when I want to describe both fields. I get the error Field(s) 'jobTitle' doesn't exist in App\Thing\Entity\ThingTranslation.

In A2lix\AutoFormBundle\Form\Manipulato\DoctrineORMManipulator@getDataClass, the association mapping fails to detect the PersonTranslation class.

If I basically replace

Do you think it can have drawbacks ?

I may be related to #17

Thank you a lot.