MappingNotFound Exception issue about vichuploaderbundle HOT 5 CLOSED

If the production logs are not enough, you need a way to get the full error stack.
A quick dirty way could be enabling the profiler in prod.

A more clean, and permanent, solution involves the use of https://github.com/getsentry/sentry-symfony package.

from vichuploaderbundle.

Thanks for your help @garak I can' provide error stack because that issue is triggered during cache/clear during automatic deployment.
I only have the following trace :
Run composer recipes at any time to see the status of your Symfony recipes.

post-install-cmd: @auto-scripts
auto-scripts: Symfony\Flex\Flex->executeAutoScripts
Executing script cache:clear
Executed script cache:clear [KO]
[KO]
Script cache:clear returned with error code 1
!!
!! // Clearing the cache for the prod environment with debug
!! // false
!!
!! // Cache is fresh.
!!
!! // Warming up optional cache...
!!
!!
!! In MappingNotFoundException.php line 17:
!!
!! [Vich\UploaderBundle\Exception\MappingNotFoundException]
!! Mapping not found. The configuration for the class "App\Entity\Map" is prob
!! ably incorrect.
!!
!!
!! Exception trace:
!! at /home/deployer/[PROJECT]/releases/43/vendor/vich/uploader-bundle/src/Exception/MappingNotFoundException.php:17
!! Vich\UploaderBundle\Exception\MappingNotFoundException::createNotFoundForClass() at /home/deployer/[PROJECT]/releases/43/vendor/vich/uploader-bundle/src/Metadata/MetadataReader.php:82
!! Vich\UploaderBundle\Metadata\MetadataReader->getUploadableFields() at /home/deployer/[PROJECT]/releases/43/vendor/vich/uploader-bundle/src/Metadata/CacheWarmer.php:29
!! Vich\UploaderBundle\Metadata\CacheWarmer->warmUp() at /home/deployer/[PROJECT]/releases/43/vendor/symfony/http-kernel/CacheWarmer/CacheWarmerAggregate.php:99
!! Symfony\Component\HttpKernel\CacheWarmer\CacheWarmerAggregate->warmUp() at /home/deployer/[PROJECT]/releases/43/vendor/symfony/framework-bundle/Command/CacheClearCommand.php:141
!! Symfony\Bundle\FrameworkBundle\Command\CacheClearCommand->execute() at /home/deployer/[PROJECT]/releases/43/vendor/symfony/console/Command/Command.php:308
!! Symfony\Component\Console\Command\Command->run() at /home/deployer/[PROJECT]/releases/43/vendor/symfony/console/Application.php:1032
!! Symfony\Component\Console\Application->doRunCommand() at /home/deployer/[PROJECT]/releases/43/vendor/symfony/framework-bundle/Console/Application.php:94
!! Symfony\Bundle\FrameworkBundle\Console\Application->doRunCommand() at /home/deployer/[PROJECT]/releases/43/vendor/symfony/console/Application.php:301
!! Symfony\Component\Console\Application->doRun() at /home/deployer/[PROJECT]/releases/43/vendor/symfony/framework-bundle/Console/Application.php:80
!! Symfony\Bundle\FrameworkBundle\Console\Application->doRun() at /home/deployer/[PROJECT]/releases/43/vendor/symfony/console/Application.php:171
!! Symfony\Component\Console\Application->run() at /home/deployer/[PROJECT]/releases/43/vendor/symfony/runtime/Runner/Symfony/ConsoleApplicationRunner.php:54
!! Symfony\Component\Runtime\Runner\Symfony\ConsoleApplicationRunner->run() at /home/deployer/[PROJECT]/releases/43/vendor/autoload_runtime.php:29
!! require_once() at /home/deployer/[PROJECT]/releases/43/bin/console:11
!!
!! cache:clear [--no-warmup] [--no-optional-warmers]

from vichuploaderbundle.

Ok, I have updates : on my prod server (I forked in an other directory I reproduced it...) I changed the name of the entity "Map" as Carte (Map in French) and now everything is Ok.
I don't know why the word is triggering this kind of thing : (I'm aware about the reserved words but Map as class name is not a reserved words) is it a php settings and in this cas i'm not 100% iso with my prod env ?

Several way to solve my issue :

• Rename my entity by not using "Map" string.
• Find why it's ok with the same code in my others env
• Find why the MetadataDrive cannot read the "Map" word

from vichuploaderbundle.

Finally, this seems a problem not related to VichUploaderBundle. Can we close this issue?

from vichuploaderbundle.

Yes we can close. It was triggered by VichUploader configuration and server sides issues.
Thanks for your help

from vichuploaderbundle.