Chapters

21 Chapters | 2:23:48 |

01

Hello Symfony

6:13
02

Meet our Tiny App

5:13
03

Routes, Controllers & Responses

8:24
04

Wildcard Routes

7:46
05

Symfony Flex: Aliases, Packs & Recipes

8:50
06

Flex Recipes

7:51
07

Twig ❤️

6:05
08

Twig Inheritance

8:02
09

Profiler: Your Debugging Best Friend

7:28
10

Assets, CSS, Images, etc

10:36
11

Generate Urls & bin/console

7:57
12

JSON API Endpoint

4:58
13

Smart Routes: GET-only & Validate {Wildcards}

4:56
14

Service Objects

5:38
15

The Twig Service & Profiler for API Requests

6:04
16

Setting up Webpack Encore

5:12
17

Packaging JS and CSS with Encore

6:05
18

Installing 3rd Party Code into our JS/CSS

5:51
19

Stimulus: Sensible, Beautiful JavaScript

5:01
20

Real-World Stimulus Example

8:50
21

Turbo: Supercharge your App

6:46

> Symfony 6 > Harmonious Development with Symfony 6

09.

Profiler: Your Debugging Best Friend

|

|

Autoplay

Previous Challenge

Next Challenge

Login or Register to check out the script

16 Comments

Sort By

Login or Register to join the conversation

webcommenterdude 4 years ago

A lot of time wasting on packs and recipes. Get to the point.

2 |

Victor SFCASTS webcommenterdude 4 years ago

Hey Webcommenterdude,

Sorry if this video was boring for you because of long explaining of the installation process. Unfortunately, that is something we have to cover so other users do not get lost in it. Though, even in this short video we covered some new installed features like Symfony Web Debug Toolbar and VarDumper component. I bet the further chapters would be more interesting for you ;)

P.S. Keep in mind that this is the intro course into the Symfony 6 and is mostly designed for beginners. Yeah, if you already know Symfony and works with it - I agree, it might be less interesting for you... but you can rewind some known for you parts :)

Anyway, thank you for your feedback! We will definitely consider this in our future tutorials and try to spend less time on explaining simple things like the packs and recipes. We just wanted to cover it well now, and do not focus too much attention on it further in this course... and in further courses as well.

Cheers!

1 |

Benanamen 3 years ago

One issue I had was the debug bar kept trying to load and would not. A .htaccess is required in the public directory for it to work.

` <IfModule mod_rewrite.c>

   RewriteEngine On
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteRule ^(.*)$ index.php [QSA,L]

</IfModule>`

1 |

MolloKhan SFCASTS Benanamen 3 years ago

Hey Benanamen,

Thank you for sharing it. If you install the library symfony/apache-pack it will generate the .htaccess for you. You can read more about how to configure a web server for a Symfony app https://symfony.com/doc/current/setup/web_server_configuration.html

Cheers

|

Jan-Makarewicz 6 months ago

Hello,
I have a problem seeing the Web Debug Toolbar - I am following SF6 SymfonyCasts tutorial in the March 2026, so quite late (but I like it :) ) - so it is obvious that my installed packaged are newer than the ones Ryan was using (In the first step, "Hello Symfony" I specified the Symfony version to use latest 6.x (and I think, the only one currently supported..) branch, with symfony new mixed_vinyl --version=6.4. This is all the difference I did.
The problem is there is no WDT down in the Symfony-powered site, (dump($variable) in PHP code does not work either - though in Twig code and dd in PHP works), there is a link 127.0.0.1:8000/_profiler/ - which leads to https://127.0.0.1:8000/_profiler/empty/search/results?limit=10 - strange that this profiler is very limited to what I saw in the tutorial video, and also what I saw and used during reading Fabien Potencier's book about Symfony 6.
I read other comments here, I thought user therouv had similar issue - but I have extends clause in my homepage twig page, so it is not this.
Also, in the output HTML source (in Firefox right mouse click -> "Wiew Source") in the bottom of the source, there is:

<div class="sf-toolbar sf-display-none" role="region" aria-label="Symfony Web Debug Toolbar" data-frankenphp-hot-reload-preserve>    <div id="sfwdt9335df">        <!-- START of Symfony Web Debug Toolbar --><div id="sfMiniToolbar-9335df" class="sf-minitoolbar" data-no-turbolink data-turbo="false">    <button type="button" title="Show Symfony toolbar" id="sfToolbarMiniToggler-9335df" accesskey="D" aria-expanded="false" aria-controls="sfToolbarMainContent-9335df">

and a lot of JavaScript mode.
Please help me on this issue - or advise, should I rather jump into Symfony 7 SymfonyCasts. I would like to also take this course tho, I like the "bottom-up" tutorial style of this series (as opposed to "up-to-bottom" from Fabien Potencier's book (not worse or better, just different - the book was a quick introduction, to have an app in production in few minutes, this one is to get know Symfony's from atoms going to particles :nerd: )

|

Victor SFCASTS Jan-Makarewicz 6 months ago

Hey Jan,

We do recommend our users download the course code from the video page and follow the tutorial from the start/ directory there. This way, you will have the exact set of packages that the course author has. But if you really want to follow our courses on the newer Symfony version - that's up to you and totally possible too, but you may need to keep in mind that it might be a bit different from what you see on the video because of the different version.

Hm, the code snippet you mentioned already means that you should have the Web Debug Toolbar (WDT) in your project and it should display well. The only reason why you may not see it is that you don't have a <body> tag in your HTML output. Make sure your template has the default html/body tags layout, because that WDT is added exactly before the closing body tag. if you see less tabs in the profiler - that's most probably because you're missing some packages that Ryan has in his project. The more Symfony packages you install - the more tabs will appear in the WDT.

The dump() in PHP code is tricky - it's not something like dump and die like with dd(). Instead, it collects the dump and show it in the WDT or in Profiler for that request, but it does not block the page execution. That's why you won't see it on the page, only in the WDT or profiler :)
I hope this clarifies things for you! If you still have any questions - please, don't hesitate to ask. You can also share some screenshots that will help a lot. For this you can upload a screenshot to an image hosting e.g. Imgur and then just link to it in the comments :)
Cheers!

1 |

Brentspine 3 years ago

Thanks for the tutorial, I like that you explain recipes and composre in greater detail than in the tutorial for Symfony 5, where it was more like magic when the debug tool was installed. (It still is magical though 🪄)

|

MolloKhan SFCASTS Brentspine 3 years ago edited

Hey @Brentspine

Thanks for your feedback, and yes, recipes feel like magic, but it is good magic, they save so much time adding configuration

Cheers!

1 |

Krystian-S 3 years ago

Hi, I have problem. When i try install debug by "composer require debug" i receive:

In FileLoader.php line 172:

Container extension "debug" is not registered in C:\Users\surow\Symfony Projects\mixed_vinyl\config/packages/debug.yaml (which is being imported fr
om "C:\Users\surow\Symfony Projects\mixed_vinyl\src\Kernel.php").

In ContainerBuilder.php line 214:

Container extension "debug" is not registered.

Please, help.

|

MolloKhan SFCASTS Krystian-S 3 years ago edited

Hey @Krystian-S

Do you already have a config/packages/debug.yaml file but the library it's not installed yet? Try removing the config file, and clear the cache manually just in case rm -r var/cache

Cheers!

|

therouv 3 years ago

Followed the steps exactly and yet the toolbar does not appear on any of my browsers.
I've restarted the server, reinstalled the debug-bundle, made sure web_profiler.toolbar is set to true and that APP_ENV=dev... and still nothing.

What is wrong?

The /_profiler/ path works on the browser, but the toolbar is not appearing anywhere.

|

Victor SFCASTS therouv 3 years ago

Hey Therouv,

Hm, did you make sure that the recipe for that package was executed? Sometimes you should allow executing it manually, but sometimes you. may allow it in your composer.json file. Though it might be forbidden in your composer.json and so no recipe was installed. Though, /_profile/ path works for you - I'd guess that the recipe was installed, but would be good to double check anyway. You can remove and install. the package again and look closer to the composer's output - it should have some recipe executed there.

Also, the very important requirement for the WDT to appear is that you should have <body> tag rendered on the page where you want to see it. Please, make sure you have a valid HTML markup on that page, especially the base html/head/body tags and that there are no any misprints or missing closing tags or brackets or quotes. I bet the invalid HTML syntax on that page prevents that WDT to show for you.

Also, try to clear the cache, i'd recommend you to remove the cache dir manually with rm -rf just in case. Sometimes it might be just. a simple cache problem.

I hope this helps!

Cheers!

1 |

therouv Victor 3 years ago HIGHLIGHTED

Also, the very important requirement for the WDT to appear is that you should have <body> tag rendered on the page where you want to see it. Please, make sure you have a valid HTML markup on that page, especially the base html/head/body tags and that there are no any misprints or missing closing tags or brackets or quotes. I bet the invalid HTML syntax on that page prevents that WDT to show for you.

That was it! I forgot to extend the block from base.html.twig. It works now.
Thank you!

2 |

Victor SFCASTS therouv 3 years ago

Hey Therouv,

Ah, yeah, I got this problem as well before ;) Glad to hear we found the problem :) And thanks for confirming the root of the problem!

Cheers!

|

unknown 3 years ago edited

Comment was deleted.

MolloKhan SFCASTS unknown 3 years ago

Hey Yuuki,

you mean on the commit message, right? That was made on purpose :)

Cheers!

|

Symfony 6

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=8.1",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "symfony/asset": "6.0.*", // v6.0.3
        "symfony/console": "6.0.*", // v6.0.3
        "symfony/dotenv": "6.0.*", // v6.0.3
        "symfony/flex": "^2", // v2.4.5
        "symfony/framework-bundle": "6.0.*", // v6.0.4
        "symfony/monolog-bundle": "^3.0", // v3.7.1
        "symfony/runtime": "6.4.3", // v6.4.3
        "symfony/twig-bundle": "6.0.*", // v6.0.3
        "symfony/ux-turbo": "^2.0", // v2.0.1
        "symfony/webpack-encore-bundle": "^1.13", // v1.13.2
        "symfony/yaml": "6.0.*", // v6.0.3
        "twig/extra-bundle": "^2.12|^3.0", // v3.3.8
        "twig/twig": "^2.12|^3.0" // v3.3.8
    },
    "require-dev": {
        "symfony/debug-bundle": "6.0.*", // v6.0.3
        "symfony/stopwatch": "6.0.*", // v6.0.3
        "symfony/web-profiler-bundle": "6.0.*" // v6.0.3
    }
}

Previous Challenge

Next Challenge