same error

does anyone have a solution for this? comopser update seems fine, but i'm getting this error when trying to issue doctrine:cache:clear

does anyone have a solution for this? update seems fine, but i´m getting this problem when trying to issue php bin/console doctrine:cache:clear

#31108 (comment)

does anyone have a solution for this? update seems fine, but i´m getting this problem when trying to issue php bin/console doctrine:cache:clear

#31108 (comment)

thanks!

Same error. For the moment we go back to version 4.2.6.

Mailbox spammed by thousands of "same error" mails won't help them to fix it up. ;)

temporary add to requirements "symfony/translation": "4.2.*", to fix this

Thanks @Gemorroj for providing this workaround.
I'll have a look tomorrow, unless someone submits a PR meanwhile.

I have the same issue.

The problem here is that LegacyTranslatorProxy exits, but it implements Symfony\Component\Translation\TranslatorInterface and Symfony\Contracts\Translation\TranslatorInterface that can be not available, thus a fatal error is triggered in that case since is not possible to load the interfaces to complete LegacyTranslatorProxy definitions.

Same error here

see #31156

Hi. This bug report is closed but I still get this exception after updating to 4.2.7.

Is this already fixed, or how can I apply a workaround to update to the latest version?

Fatal error: Interface 'Symfony\Component\Translation\TranslatorInterface' not found in "\testarea_symfony_api\vendor\symfony\validator\Util\LegacyTranslatorProxy.php on line 21

In LegacyTranslatorProxy.php line 21:

  Attempted to load interface "TranslatorInterface" from namespace "Symfony\Component\Translation".
  Did you forget a "use" statement for "Symfony\Contracts\Translation\TranslatorInterface"?

Something like this can help: TomaszGasior/RadioLista-v3@1c8170d

Until new release of framework-bundle you need to fork framework-bundle repository and create your own branch for commit with bugfix.

Or you can just install translator component. ;)

Or you can use this patch: https://github.com/symfony/framework-bundle/commit/9c3f47e28e0ea66b762b99a8573d6d7acaa43244.patch

For example with this patch package: https://github.com/cweagans/composer-patches

composer req symfony/translation

So the idea to solve that issue is to require something we don't need...
Prefer not to do that and wait for a better solution.

the other solution is to install the dev version of FrameworkBundle, which already contains the patch, which will be part of the 4.2.8 release.

@Spomky @stof Or use the cweagans/composer-patches package to patch it for you before they release it.

Then in composer.json:

{
  "extra": {
    "patches": {
      "symfony/framework-bundle": {
        "Fix translator": "https://github.com/symfony/framework-bundle/commit/9c3f47e28e0ea66b762b99a8573d6d7acaa43244.patch"
      }
    }
  }
}

I'm not using "symfony/translation" in my project, But I'm using symfony validator. Up to now it worked fine. Do I have to install "translation" eventhough I'm not using it? Is it so?

@featuriz You can do that for the moment as a workaround until the fix from #31156 is released with Symfony 4.2.8.

@xabbuh "symfony/framework-bundle": "^4.2,!=4.2.7",
Do I have to do this?
Skip 4.2.7

@featuriz Just install translator and update framework bundle.

@featuriz or use the patch approach:

#31152 (comment)