Web Debug Toolbar & the Profiler!

Make sure you've committed all of your changes - I already did. Because we're about to install something super fun! Like, floating around space fun! Run:

composer require profiler --dev

The profiler - also called the "web debug toolbar" is probably the most awesome thing in Symfony. This installs a few packages and... one recipe! Run:

git status

Ok cool! It added a couple of configuration files and even some routes in the dev environment only that help the profiler work. So... what the heck is the profiler? Go back to your browser, make sure you're on the article show page and refresh! Voilà!

See that slick black bar at the bottom of the page! That's the web debug toolbar! It's now automatically injected at the bottom of any valid HTML page during development. Yep, this JavaScript code makes an AJAX call that loads it.

Oh, and it's packed with info, like which route was matched, what controller was executed, execution time, cache details and even information about templates.

And as we install more libraries, we're going to get even more icons! But the really awesome thing is that you can click any of these icons to go into... the profiler.

Hello Profiler: The Toolbar's Powerful Sidekick

OoooOoo. This takes us to a totally different page. The profiler is like the web debug toolbar with a fusion reactor taped onto it. The Twig tab shows exactly which templates were rendered. We can also get detailed info about caching, routing and events, which we'll talk about in a future tutorial. Oh, and my personal favorite: Performance! This shows you how long each part of the request took, including the controller. In another tutorial, we'll use this to dig into exactly how Symfony works under the hood.

When you're ready to go back to the original page, you can click the link at the top.

Magic with The dump() Function

But wait, there's more! The profiler also installed Symfony's var-dumper component. Find ArticleController and go to showAction(). Normally, to debug, I'll use var_dump() to print some data. But, no more! Instead, use dump(): dump the $slug and also the controller object itself:

            
            37 lines
            
            src/Controller/ArticleController.php
        
                                                    ... lines 1 - 8
                            
            class ArticleController extends AbstractController
            
            {
            
                                                    ... lines 11 - 21
                            
                public function show($slug)
            
                {
            
                                                    ... lines 24 - 28
                            
                    dump($slug, $this);
            
                                                    ... lines 30 - 34
                            
                }
            
            }

Ok, refresh! Beautiful, colored output. And, you can expand objects to dig deeper into them.

Tip

To expand all the nested nodes just press Ctrl and click the arrow.

Using dump() in Twig

The dump() function is even more useful in Twig. Inside the body block, add {{ dump() }}:

            
            31 lines
            
            templates/article/show.html.twig
        
                                                    ... lines 1 - 4
                            
            {% block body %}
            
            {{ dump() }}
            
                                                    ... lines 7 - 29
                            
            {% endblock %}

Tip

If you don't have Xdebug installed, this might fail with a memory issue. But don't worry! In the next chapter, we'll install a tool to make this even better.

In Twig, you're allowed to use dump() with no arguments. And that's especially useful. Why? Because it dumps an associative array of all of the variables you have access to. We already knew we had title and comments variables. But apparently, we also have an app variable! Actually, every template gets this app variable automatically. Good to know!

But! Symfony has even more debugging tools! Let's get them and learn about "packs" next!

Leave a comment!

2019-11-13 Victor Bocharsky

Hey Random,
Ah, probably it was more complex than just upgrading the WDT. Thank you for confirming that package upgrade helped you.
Cheers!
2019-11-12 Random Random

Just updated the packages with "composer update", everything solved. Why haven't I thinked about that earlier.. Thanks anyway for the help and the effort !
2019-11-12 Random Random

Hello, I tried to update the bundle, it does not resolve anything.
I use Symfony 4.3.6 with
[ir@ir-pc DiscordBotsManager]$ composer info symfony/web-profiler-bundle name : symfony/web-profiler-bundle descrip. : Symfony WebProfilerBundle keywords : versions : * v4.3.7 type : symfony-bundle license : MIT License (MIT) (OSI approved) https://spdx.org/licenses/MIT.html#licenseText source : [git] https://github.com/symfony/web-profiler-bundle.git 6ce12ffe97d9e26091b0e7340a9d661fba64655e dist : [zip] https://api.github.com/repos/symfony/web-profiler-bundle/zipball/6ce12ffe97d9e26091b0e7340a9d661fba64655e 6ce12ffe97d9e26091b0e7340a9d661fba64655e path : /home/ir/Documents/Developpement/Web/DiscordBotsManager/vendor/symfony/web-profiler-bundle names : symfony/web-profiler-bundle autoload psr-4 Symfony\Bundle\WebProfilerBundle\ => . exclude-from-classmap requires php ^7.1.3 symfony/config ^4.2 symfony/http-kernel ^4.3 symfony/routing ~3.4|~4.0 symfony/twig-bundle ~4.2 symfony/var-dumper ~3.4|~4.0 twig/twig ^1.41|^2.10 requires (dev) symfony/console ~3.4|~4.0 symfony/dependency-injection ~3.4|~4.0 symfony/stopwatch ~3.4|~4.0 conflicts symfony/dependency-injection <3.4 symfony/form <4.3 symfony/messenger <4.2 symfony/var-dumper <3.4
2019-11-11 Victor Bocharsky

Hey Random,
Hm, it sounds like you should upgrade the WebProfilerBundle, try to execute: "$ composer update symfony/web-profiler-bundle". Btw, what version of Symfony do you use? And what version of "symfony/web-profiler-bundle" package, you can know it with "$ composer info symfony/web-profiler-bundle". Also, is it your personal project or you downloaded this project from this course page? If you downloaded it, in which folder you're in: start/ or finish/ ?
Cheers!
2019-11-08 Random Random

The problem is there ! I have no accountAdministration variable in my JSs, I have inspected a littlebit the code in my nav's developer console and I noticed that the error comes from the code that the debuger inject into my page for the toolbar...
for the 500 error, I digged up and found this :
https://imgur.com/30XzwlA
and so I went ahead and searched for this exact file into my vendor folder, and it is present
I don't understand what is happening, I tried to remove my vendor folder and to run composer install to install everything back, does not resolve anything.
2019-11-08 Victor Bocharsky

Hey Random,
Looks like the error message you give us is JS error. Where do you have that "accountAdministration" property? It seems that somehow you're trying to call this property on a variable that's null. Please, make sure that the object exist, like add an if statement to make sure it's not null, and if it's not - only then call "accountAdministration" on it.
About the 500 error in your console - check your logs! I suppose you're loading your application in "dev" mode, if so - check the var/log/dev.log file, you can tail it with:
$ tail -f var/log/dev.log
They try to reproduce the error and see the logs, they would have more context about what exactly went wrong and why you see the 500 error. Then, when you know the reason behind of it - you would just need to fix it :)
Cheers!
2019-11-07 Random Random

Hello, I ran into issues with the debug pack since yersterday and I can't sort out how to debug it out. It's so fookin annoying:
When I navigate to my webserver (with bin/console server:start), the bar have a text indicating me : An error occurred while loading the web debug toolbar.
and when I look to the console I have a couple of errors like :
GET http://127.0.0.1:8000/_wdt/822837 500 (Internal Server Error)
and
Uncaught TypeError: Cannot read property 'accountAdministration' of null at HTMLDocument.<anonymous> (index.js:formatted:4271) (anonymous) @ index.js:formatted:4271
Help !! Thanks in advance. Don't hesitate to ask if you need something from my code (also present on github)
2019-09-18 Vladimir Sadicov

Which webserver do you use? Do you have correct html markup? I just tested your composer.json and it works
2019-09-17 Oscar Ishen

My composer.json:
{ "type": "project", "license": "proprietary", "require": { "php": "^7.1.3", "ext-ctype": "*", "ext-iconv": "*", "sensio/framework-extra-bundle": "^5.4", "symfony/console": "4.3.*", "symfony/dotenv": "4.3.*", "symfony/flex": "^1.3.1", "symfony/framework-bundle": "4.3.*", "symfony/twig-bundle": "4.3.*", "symfony/web-server-bundle": "4.3.*", "symfony/yaml": "4.3.*" }, "require-dev": { "symfony/profiler-pack": "^1.0" }, "config": { "preferred-install": { "*": "dist" }, "sort-packages": true }, "autoload": { "psr-4": { "App\\": "src/" } }, "autoload-dev": { "psr-4": { "App\\Tests\\": "tests/" } }, "replace": { "paragonie/random_compat": "2.*", "symfony/polyfill-ctype": "*", "symfony/polyfill-iconv": "*", "symfony/polyfill-php71": "*", "symfony/polyfill-php70": "*", "symfony/polyfill-php56": "*" }, "scripts": { "auto-scripts": { "cache:clear": "symfony-cmd", "assets:install %PUBLIC_DIR%": "symfony-cmd" }, "post-install-cmd": [ "@auto-scripts" ], "post-update-cmd": [ "@auto-scripts" ] }, "conflict": { "symfony/symfony": "*" }, "extra": { "symfony": { "allow-contrib": false, "require": "4.3.*" } } }
2019-09-17 Oscar Ishen

Yeah, I see it's installed. But why I don't see the debug toolbar in the browser then?..
My .env has APP_ENV=dev, so I'm running in the dev env.
2019-09-17 Vladimir Sadicov

Hey Oscar Ishen
Probably it's already installed, check your composer.json for symfony/profiler-pack row.
Cheers!
2019-09-16 Oscar Ishen

Running `composer require profiler --dev` not installing packages.
I have output
$ composer require profiler --dev Using version ^1.0 for symfony/profiler-pack ./composer.json has been updated Loading composer repositories with package information Updating dependencies (including require-dev) Restricting packages listed in "symfony/symfony" to "4.3.*" Nothing to install or update Generating autoload files Executing script cache:clear [OK] Executing script assets:install public [OK]
2019-09-09 Victor Bocharsky

Hey Howto!
Are you sure you ran the website in dev mode? What values do you have for APP_ENV env var in .env and .env.local files? Also, please, make sure you have the correct HTML base markup in your template, i.e. it has html/head/body tags, otherwise Profiler won't be added.
Cheers!
2019-09-07 howto

Profiller doesnt work :((
I reloaded pages, opened source pages... and saw nothing
PHP 7.2
Symfony 4.3
I start server with
./bin/console server:run
php -S 127.0.0.1:8000 -t public
profiler was installed like in tutorial
2019-06-28 Diego Aguiar

Hmm, sounds possible. If you run php bin/console debug:router do you see the profiler routes being defined? What happens if you use Symfony's web server instead of Apache?
If you open other pages do you get the same error or there are some pages where you can see the debug toolbar?
We need to discover first where the error comes from
2019-06-27 Mohamed Sharfaz Sairaz

Thanks for the swift reply Diego Aguiar I tied that as well. .htaccess file is present in web directory. This application was working fine when I was running on Ubuntu with Apache <2.4 and PHP 5.6. The missing resource load after page loads completes. Do you think this could be a problem with Apache or PHP configuration?
2019-06-27 Diego Aguiar

Hey Mohamed Sharfaz Sairaz
Are you running on dev environment? Just run php bin/console to see on which env you are running.
Also you can try removing entirely the cache files rm -rf var/cache/*
Oh, and if you are on Apache double check that the .htaccess is on your web directory
Cheers!
2019-06-27 Mohamed Sharfaz Sairaz

Do you know what was the problem. How can I resolve it? I am having same issue, its been a while and I cannot figure it out. I have symfony 3.2 application and upgraded to 3.4. Also updated LAMP stack to PHP 7.2 and Apache 2.4 on Centos 7. Since then I am having this issue.
Cannot find http://vm.host/_wdt/34a9cd
I even tried installing composer require symfony/apache-pack. Nothing helps.
Thanks in advance
2019-01-14 Victor Bocharsky
Hey Ivan,
It seems the system unable to read the session, probably due to permission problems. Try to change your current session save path to a different one e.g. "%project_dir%/var/session", you need this option:
```
framework:
    session:
        save_path: '%project_dir%/var/session'
```
And create that /path-to-your-project/var/session directory. Btw, I wonder what "save_path" value you have before?
I hope this helps.
Cheers!
2019-01-12 Ivan

Hello. Thanks for the tutorial. I cant open the debug toolbar. After clicking on an element on the toolbar I receive the following error:
Twig_Error_Runtime. An exception has been thrown during the rendering of a template ("Warning: SessionHandler::read(): open(C:\Development\xampp\tmp\sess_nn9gqras422muqg9imam0ipa9u, O_RDWR) failed: No such file or directory (2)").
Any advice how to fix this ? Cheers
2018-10-18 weaverryan

Hey @JoJohn Alcher Doloiras!
Yea, I kinda like the autogenerated naming convention too! I don't follow it exactly... but I more or less do - e.g. app_CONTROLLERCLASS_METHODNAME ... or something near this :). I like the app_ prefix because it makes it very easy to search your entire project for that route... if you ever need to.
Cheers!
2018-10-17 John Alcher Doloiras

Makes sense! Can you suggest a naming convention to follow? The autogenerated one looks good enough for me.
2018-10-17 John Alcher Doloiras

Ah, that makes sense. For some reason I thought the `src` directory is namespaced as `Src`. It's all clear now. Thanks!
2018-10-16 weaverryan

And this is *also* why we recommend actually giving your route a specific name, once you actually need to link to it (because we don't want this route name to change accidentally, once we're using it!).
Cheers!
2018-10-16 Vladimir Sadicov

Hey John Alcher Doloiras
It's quite simple. Route name `app_article_show` is autogenerated from root namespace, current controller name and current action. This happens because we did not specify `name` parameter in the `@Route` annotation.
Cheers!
2018-10-16 John Alcher Doloiras

I'm wondering, how did Symfony deduce the route name as `app_article_show`?
2018-10-13 christianstrang

If you run into any memory issues or "ugly" dumped variables, just go to the next chapter, it will "fix" the issue.
2018-09-13 Diego Aguiar

Ha! nice catch man :)
2018-09-13 Gaël Weiler

Thanks for the reply, I manage to find the issue by myself finaly, it was a small mistake but very annoying.
I put:
RewriteRule ^(.*)$ index.php?/$1 [L]
Instead of:
RewriteRule ^(.*)$ index.php/$1 [L]
In the .htaccess, so all my uri became a GET and the Request object was empty :)
2018-09-12 Diego Aguiar

Hey Gaël Weiler
Thanks :)
That's odd. Do you see the nav items active? (in bold white color)
Which Symfony version are you using?
Cheers!
2018-09-12 Gaël Weiler

Hi! Thank you for this course, I didn't where to start with symfony before.
I've got a problem, on the profiler page I can't change panel, when I click on the left nav menu the page reload and stay on the Request/Response panel, any idea where that came from?
2018-08-23 Victor Bocharsky

Hey Silvestr,
Thanks for sharing it! Yes, Xdebug may help but with var_dump() function only, but Geoff was talking about Symfony's dump() function, i.e. VarDumper Component, see https://symfony.com/doc/cur... for the reference.
Cheers!
2018-08-23 Silvestr Hašek

Hi,
In case you got same error whit memory limit just install xdebug and setup it. Its pretty easy and you will be fine,..
2018-08-22 v fu

I found dump() which start infinite loop. Our Dear Sir explain in the next video let's forsake this go to next video Yeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees!!!!!!!!!!!!!!!!!
2018-08-14 Diego Aguiar

Ah, yes, that's a deprecation about using "Routing annotations" I believe you just have to change the import from "Sensio\Bundle\FrameworkExtraBundle\Configuration\Route" to "Symfony\Component\Routing\Annotation\Route"
2018-08-10 Wo

I call it in ArticleController. In the twig template, it's working well :-)
I think it could be good :-)
I have a notification in my profiler, I don't know if there is a link : User Deprecated: The "Sensio\Bundle\FrameworkExtraBundle\Configuration\Route" annotation is deprecated since version 5.2. Use "Symfony\Component\Routing\Annotation\Route" instead.
2018-08-09 Diego Aguiar

Hey Wo
If you installed the "website-skeleton", then yes, all those packages and more will be installed by default
To your question. Where did you call it? inside a twig's template? then you have to look for the dumped content inside the debug profiler tab
Cheers!
2018-08-09 Wo

Hi !! in Symfony 4.1.3, the debugger is already installed adn twig also.
No problem else that when I put dump in my controller, it shows nothing.
How can I resolve this ?
Thanks for your course, it's amazing !
2018-07-02 Victor Bocharsky

Hey Nicklas,
You're right! The dd() helper method was introduced in Symfony 4.1. Thanks for sharing this useful tip for others.
Cheers!
2018-06-30 Nicklas Reincke

FYI: In never versions of Symfony there is now dd($var);. This dump();'s your code and stops further execution. It's the same as dump($var); and then die();.
2018-06-07 Victor Bocharsky

Hey Geoff,
Really weird... btw, did you have any recursion in dumped classes, such as User entity, etc. that is dumped with empty dump() function? And could you try to upgrade your dependencies to the latest versions? Probably there was a memory leak bug which may be fixed lately, if not, probably you need to report an issue about it or do some debugging yourself to find the root of the problem.
Cheers!
2018-06-06 Geoff Maddock

I did confirm that the memory_limit was updated by checking phpinfo, and it did update. I didn't try setting the limit to -1 yet, but I will just to see what happens.
2018-06-05 Victor Bocharsky

Hey Geoff,
I see you tried to increase memory_limit up to 1024M, but are you sure it was applied? Because to take effect you have to restart your PHP-FPM or restart your running built-in PHP web server. To make sure about *actual* memory_limit value you can in the web debug Symfony toolbar hover over Symfony version in the right bottom corner and click on "View phpinfo()" link near your PHP version, then search for "memory_limit". I have "-1" there on my laptop which means no limit at all, you can try this value as well.
Btw, do call this dump() function in dev environment?
Cheers!
2018-06-04 Geoff Maddock

4.1
2018-06-01 Diego Aguiar

Interesting. When you call "dump" without params, it tries to dump all the available variables that you can access in the template, in somewhere must be an infinite loop, or something like that causing a huge memory usage.
What Symfony & Twig version are you using?
2018-06-01 Geoff Maddock

I'm running locally on my desktop in a container. I was using the default setting for memory_limit (128M), and upped the memory_limit to 1024M, but still getting the same error when I call {{ dump() }}
However, I did more testing and if I call {{ dump('test') }} or dump any single, simple variable that was passed, it works. But if I dump a more complex object or with no parameters, it runs out of memory. Does this really require that much memory?
Seems odd because when I dump an object in the controller, it works fine.
2018-06-01 Victor Bocharsky

Hey Geoff,
Oh, you have a memory error. The possible solution - increase your memory limit in php.ini. If you have this problem locally (that is probably true) - it's easy to fix. On VPNs sometimes you have limited memory, which means you need to upgrade to another plan to get more memory. I wonder what memory limit you currently have. Search for memory_limit in your php.ini and try to increase it. Don't forget to restart php-fpm or built-in web server so changes take the effect.
Yes, dump component stores dump-ed data in profiler, but it works only for dumped values in PHP code, not in the templates. To see it - dump something in your controller and find target icon in the profiler.
Cheers!

2018-05-31 Geoff Maddock

Been trying to figure out how to get the dump function to work in twig. No matter which twig template I call it in, it throws a 500 error.
Looking in my logs, it tells me:


[2018-05-31 23:50:02] php.CRITICAL: Fatal Error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 81805312 bytes) {"exception":"[object] (Symfony\\Component\\Debug\\Exception\\OutOfMemoryException(code: 0): Error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 81805312 bytes) at /srv/cadence/vendor/twig/twig/lib/Twig/Extension/Debug.php:48)"} []

Anyone else run into this?

It works in the Controller. I also read somewhere that there should be a place to see the dump'd variables in the profiler, but I can't find such a place.

2018-04-16 Victor Bocharsky

Hey Petru,
See "framework.ide" option: https://symfony.com/doc/cur... . Looks like Windows requires PhpStormProtocol to get it working with PhpStorm, but it should work by default in browser. Anyway, you can change this value to use PhpStorm or any of your favorite IDE / text editor which I think will be much useful instead of just showing it in browser.
Cheers!
2018-04-15 Petru Lebada

Hello,
I clicked on the controller::show in profiler and it gives me an error:
No route found for "GET /myproject/public/_profiler/open" (from "http://localhost/myproject/public/news/why-asteroids-taste-like-bacon")
My dev env is windows and im using apache on xampp
Any ideas how i can fix this?
2018-03-27 Victor Bocharsky

Aha, this "install-recipes" command came from Symfony Flex v1.0.76: https://github.com/symfony/... . And really, to see it you need to run composer *inside* your project dir. Thanks again ;)
Cheers!
2018-03-26 Schyzophrenic

Victor Bocharsky I am using composer Composer version 1.6.3 2018-01-31 16:28:17
Insterestingly, the "install-recipes" option is only available if you run composer in the project directory. Not sure how composer is plugged with symfony but there is definitely something going on here :)
2018-03-26 Victor Bocharsky

Hey Schyzophrenic ,
Thanks for sharing your solution! Yeah, looks like Twig is missing in your system. But what version of Composer do you have? Because I don't see "install-recipes" command in mine :) Probably it comes with a Composer plugin? What's the plugin name?
Cheers!
2018-03-25 Schyzophrenic

If anyone runs through this issue, I fixed it by running
composer install-recipes.
i apparently had a missing recipe for twig (No idea how this occured...)
2018-03-25 Schyzophrenic

Hello,
It seems that running the composer require profiler creates an issue:
Executing script cache:clear [KO]
[KO]
Script cache:clear returned with error code 1
!!
!! In CheckExceptionOnInvalidReferenceBehaviorPass.php line 32:
!!
!! The service "web_profiler.controller.profiler" has a dependency on a non-existent service "twig".
Not sure where this service is supposed to be defined in the new SF4 structure...
Just to add: This is really odd as I created another app to test out and it works well if I go through all the require commands again.
I tried to "remove" and then require again but no luck... Very odd. Any idea?
2018-03-05 Victor Bocharsky

Hey Jeroen,
Thanks for sharing it! Looks like we use Twig v2.4.4 in this screencast
Cheers!
2018-03-03 Jeroen van den Nieuwenhuisen

Edit: This issue is fixed with twig with the new twig version 2.4.6 :-)
The problem is in the file Twig_Profiler_NodeVisitor_Profiler. I change line 56 from:
return sprintf('__internal_%s', hash('sha256', __METHOD__));
to:
return sprintf('__internal_%s', hash('sha256', $this->extensionName));
And after clearing the twig cache it works again.
2018-03-03 Jeroen van den Nieuwenhuisen

I am getting the following error after the command composer require profiler --dev and refreshing the show page.
Twig_Error_Runtime
An exception has been thrown during the rendering of a template ("Notice: Undefined offset: 0").
2018-02-20 Diego Aguiar

Hey @Alvaro
I think your dump format is uglier (or different) because you have not installed "xdebug" on your server, but don't worry about it, in the next video, Ryan teaches how to use the "debug" pack which improves the "dump" format a lot more than "xdebug"
Cheers!
2018-02-20 Alvaro

When insert {{ dump() }} in show.html.twig the content of the array it´s not shown formatted like in the video. Am I missing something?
2018-01-29 weaverryan

What I *should* have done was dump($slug, $this);die; :). The problem is simply that the content from the dump is causing session warnings, which we don't really care about because we're just dumping some debug code. It didn't show up on my screen due to some slightly different PHP settings. Anyways, it's always unnerving to see warnings ;).
Cheers!
2018-01-27 Simon Waldburger

Got the same error. But after installing the next package "debug" (see next lesson) it got fixed!
2018-01-26 Gerard Doets

First of all: Thank you for such a great explanation (and for the startrek references).
I ran into this error, after I added the dump($slug, $this); on line 30 in the ArticleController.php and the {{ dump() }} in the show.html.twig I got an
HTTP 500 error: "Failed to start the session because headers have already been sent by "C:\xampp\htdocs\symfony\the_spacebar\vendor\symfony\var-dumper\Dumper\AbstractDumper.php" at line 181.
"
Thanks!
2018-01-25 weaverryan

Hey Łukasz!
I'm glad you figured it out :). The Web Debug Toolbar should work fine with Apache, but you may need to add the .htaccess file. You can do that by running composer require symfony/apache-pack.
Cheers!
2018-01-23 Łukasz

It was problem with Apache server. It doesn't work together.
2018-01-23 Łukasz

Hello, I have a problem with profiler. 'An error occurred while loading the web debug toolbar. Open the web profiler.' After clicking 'Open the web profiler' shows 404 error page. I have 5 console errors on Chrome 'Failed to load resource: the server responded with a status of 404 (Not Found) ' for '/_wdt/05cb53' directory. Installation process was ended succesfull.
2018-01-17 shing

WOW! super fast reply and top marks!! for really clear explanation. WOW. That cleared up so presumptions in my head. Awesome,Thxs weaverryan
2018-01-17 Bartosz

Great :)
Now everything is clear for me.
Thank You Diego and Ryan.
2018-01-17 weaverryan

Hey @shing!
Hmm, so we should update that page in the docs :). It really *should* be with --dev... but it *really* doesn't matter.
So actually, the --dev flag has nothing to do with Symfony's "dev" environment or what environments it is activated in. All of that is decided in the package's recipe, which installs the exact same way with or without the --dev flag.
Using the --dev flag is purely a *composer* thing. By using it, your dependencies will be added to a require-dev section of your composer.json file. And mostly, that makes no difference: when you run composer install, it downloads all of your dependencies from both the require and require-dev keys. So then... what *is* the point of --dev? Well, you're *supposed* to add libraries to require-dev that you *only* need during development (not on production). Why? Because then when you deploy to production, you can run composer install --no-dev to install ONLY the require deps (but not require-dev). Why would you do this? Because it gives your site a TINY performance boost to not have to worry about autoloading these files.
Phew! So, the tl;dr is this:
A) Recipes always install the same way, and --dev has nothing to do with the recipe system
B) If you use --dev when installing a package that you only need during development, the only difference is that if use composer install --no-dev during deployment, you will get a small performance boost.
Cheers!
2018-01-17 shing

Hi, I did composer require profiler without the --dev flag, which is also what the symfony documentation recommended. (https://symfony.com/doc/cur... Everything seems to be installed correctly. config/bundles reflects that the profiler is in the dev environment.
So my question is that, is there a way to check in the documentation, a flex component is installed with a default --dev flag, or only when the installation's done and check config/bundles for the environment.
Thxs in advance
2018-01-17 weaverryan

Hey Bartosz!
Ah, don't worry! Actually, there is nothing wrong at all :).
1) For the first error - "Failed to start session" - that is because the dumped content (which you can see at the top of the page) is causing problems with the session. But it's not something to worry about :). If you add a die; after the dump(); statement, then you won't see this error (you'll only see the dumped content).
2) For the ugly dump() in Twig, Diego is correct! Your dump() is uglier than mine because you don't have XDebug installed. I would recommend installing this, because it has several minor benefits. But... don't worry too much! If you watch the next video, we install *another* package which actually makes the dump() in Twig even prettier, even without XDebug :).
Cheers!
2018-01-16 Bartosz

Hi Diego, thx for interest in my case :)
First the most simple thing, I use Symfony 4.0.3, Composer 1.5.1 and Firefox 57.0.4. Everything on Ubuntu 17.10.1 with PHP 7.1.11
I'm not strong enough in Symfony to deal with all issues but I have double checked and I'm sure that there is no syntax mistake with double "$" in my code.
I have made completely brand new Symfony project with just one Controller but result is the same... Any ideas?
2018-01-16 Diego Aguiar

Hey @Bartosz
About your first problem, you have a double "$" at your slug variable.
And, about the second one, I'm not 100% sure what is causing it, which Symfony version are you using? Do you have Xdebug enabled?
Cheers!
2018-01-16 Bartosz

I got a problem with dump() function. First example with dump($slug, $this) returns me an error.
Here is first screenshot: https://prnt.sc/i1c8f3
In second case, {{ dump() }} I also have some difficulties.
Here is second screenshot: https://prnt.sc/i1ca9j

TRACK

Symfony 4 >

COURSE

Stellar Development with Symfony 4

Web Debug Toolbar & the Profiler!

Video not working?

Hello Profiler: The Toolbar's Powerful Sidekick

Magic with The dump() Function

Using dump() in Twig

Leave a comment!

	... lines 1 - 8
	class ArticleController extends AbstractController
	{
	... lines 11 - 21
	public function show($slug)
	{
	... lines 24 - 28
	dump($slug, $this);
	... lines 30 - 34
	}
	}

	... lines 1 - 4
	{% block body %}
	{{ dump() }}
	... lines 7 - 29
	{% endblock %}

TRACK

Symfony 4 >

COURSE

Stellar Development with Symfony 4

Web Debug Toolbar & the Profiler!

Video not working?

Hello Web Debug Toolbar!

Hello Profiler: The Toolbar's Powerful Sidekick

Magic with The dump() Function

Using dump() in Twig

Leave a comment!