Giters

maschmann / TranslationLoaderBundle

Symfony2 bundle with database translation loader

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

"could not find loader for yml files!" error during command asm:translations:import

inmarelibero opened this issue · comments

commented

hi, on Symfony 3.4.17 and "asm/translation-loader-bundle": "^1.0@dev",

I get the error:

--------------------------------------------------------------------------------
Translation file importer
--------------------------------------------------------------------------------
importing all available translation files ...
searching SonataCoreBundle translations
--------------------------------------------------------------------------------

searching SonataBlockBundle translations
--------------------------------------------------------------------------------

searching SonataNotificationBundle translations
--------------------------------------------------------------------------------

searching SonataAdminBundle translations
--------------------------------------------------------------------------------

searching SonataSeoBundle translations
--------------------------------------------------------------------------------

searching SonataFormatterBundle translations
--------------------------------------------------------------------------------

searching FOSUserBundle translations
--------------------------------------------------------------------------------

In ImportTranslationsCommand.php line 145:
could not find loader for yml files!

during the command asm:translations:import, precisely during the import of searching FOSUserBundle translations

debugging I could saw that it's crashing when processing the file /Users/inmarelibero/www/2makewine/vendor/friendsofsymfony/user-bundle/Resources/translations/FOSUserBundle.nb.yml

commented

after looking into code, I found this temporary solution:

asm_translation_loader:
    driver: orm
    loaders:
        yml: translation.loader.yml
    database:
        entity_manager: default

and it's working, but I hope this (possible) bug will be resolved soon