Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Symfony debug toolbar not shown - profiler template not found #134

Open
PaddyLock opened this issue Sep 12, 2018 · 2 comments
Open

Symfony debug toolbar not shown - profiler template not found #134

PaddyLock opened this issue Sep 12, 2018 · 2 comments

Comments

@PaddyLock
Copy link

@PaddyLock PaddyLock commented Sep 12, 2018

I am using Symfony 4 with the following

"cache/adapter-bundle": "^1.2",
"cache/cache-bundle": "^1.1",
"cache/doctrine-adapter": "^1.0",
"cache/memcached-adapter": "^1.0",
"cache/psr-6-doctrine-bridge": "^3.0",

When loading a page the debug toolbar shows with "An error occurred while loading the web debug toolbar."

The template is specified in vendor/cache/cache-bundle/Resources/config/data-collector.yml
The template exists in vendor/cache/cache-bundle/Resources/views/Collector/cache.html.twig

cache.data_collector:
    class: Cache\CacheBundle\DataCollector\CacheDataCollector
    tags:
      - { name: data_collector, template: 'CacheBundle:Collector:cache.html.twig', id: 'php-cache' }

request.CRITICAL: Uncaught PHP Exception UnexpectedValueException: "The profiler template "@CacheBundle/Resources/views/Collector/cache.html.twig" for data collector "php-cache" does not exist."

@PaddyLock
Copy link
Author

@PaddyLock PaddyLock commented Sep 18, 2018

I have a temp fix for this by replacing

CacheBundle:Collector:cache.html.twig

with

@WebProfiler/Collector/cache

Is this a known bug?

@egbuk
Copy link

@egbuk egbuk commented Dec 14, 2018

Encountered the same issue with symfony 3.4.20. Tried your temp fix, it kinda helps and it's even possible to move cache.html.twig in the app directory and replace CacheBundle:Collector:cache.html.twig with it's new path. But that's obviously a bad solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants