-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Symfony Profiler Broken in 2.8+ #22671
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
Comments
You are right. We deprecated all profiler storages in #15944. I don't think they will be introduced in the future, so the solution is the one you suggested: create your own profiler storage. In this case, it could be as simple as copying the original Symfony database storage that you used before. |
This is in regards to Symfony Issue #22671 symfony/symfony#22671
@javiereguiluz Thanks for your help. We decided to maintain a copy of the ProfilerStorage Handlers for the foreseeable future. If there's any other advice going forward, we're all ears. 😄 |
Update: We created a composer package with the necessary code to keep these ProfilerStorage Handlers easily installed, configured, and maintained. The package is located here: ProfilerStorageBundle |
Thanks @alexgurrola! |
We have a system of Load Balancers and Web Servers, so we use Database Storage for the Profiler, which has somehow become deprecated and removed in 2.8+, which will keep us from ever upgrading in the future. Is there any alternatives for retrieving this logic or will we be forced to create our own extensions for future use?
Location:
https://github.com/symfony/symfony/tree/2.8/src/Symfony/Component/HttpKernel/Profiler
The text was updated successfully, but these errors were encountered: