Debugging & Packs

Hey Maxime,

It sounds like a CORS problem... or probably your assets are just not available. Could you open the URL that is failed with net::ERR_ABORTED error in a new tab? Did you see the same 404 error or you can load the asset successfully?

Cheers!

Hey Lijana Z.!

Yea... this stuff is the worst. We don't have any plans to cover this, but I'll add it to our idea list - it's a question we DO get from time-to-time.

Good luck!

Hey yao!

Ah, interesting! So, don't worry about this :). This deprecation is not caused by your code, but bu SensioFrameworkExtraBundle. So, it needs to be fixed in that bundle (and then eventually you can upgrade to the fixed version). In fact, this was fixed a few days ago in that bundle (https://github.com/sensiolabs/SensioFrameworkExtraBundle/pull/594) and is available in the latest version of the bundle. Try running composer update sensio/framework-extra-bundle to get the latest version.

Cheers!

Hey Maxim M.!

Hmm... yes, I think that would work just fine :). As you mentioned, your project depends on symfony/debug-pack, and it depends on symfony/profile-pack, so you should be able to remove symfony/profiler-pack and have no changes.

To test it, run this:

composer remove symfony/profiler-pack

If we're correct, then you will ONLY see symfony/profiler-pack being removed - you will not see any other libraries being removed.

Cheers!

Yes, the "composer remove symfony/profiler-pack" command really works.
Removed "symfony/profiler-pack": "^ 1.0" from the composer.json project. As needed.
And in the /vendor directory there is symfony/profiler-pack, as required.

Thank!

Hey Czar P.!

You're 100% correct. Without the debug-pack installed, dump() in twig does exactly what you said: it's a var_dump(). The reason I didn't get a memory error is because I have XDebug installed, which makes var_dump() a bit prettier, and avoids recursive memory issues. But, either way, the debug pack gives us a much better situation anyways :).

Cheers!

Sir weaverryan I'm a fan of your work in the Sf community! Appreciate the enlightenment on XDebug. I just installed it and it worked like a charm (now my output matches the previous video). Actually, I was originally just concerned with the dump behavior throwing off other learners before they get to this chapter.

Hey Czar P.!

Ahh, thank you! Made my morning :).

> Appreciate the enlightenment on XDebug. I just installed it and it worked like a charm

Awesome! Super happy that worked!

> I was originally just concerned with the dump behavior throwing off other learners before they get to this chapter

When you saw your message, i had the same thought! I wish I had thought about that when originally recording it. If we get another message about this, we'll add a note to the video.

Cheers!

Make at least a note with the text that in the previous lesson xdebug was used instead of var_dump.
This is confusing when learning, because it seems that something is not working as the author of the video and it needs to be fixed.

Hey Maxim M.!

I think that's an excellent suggestion - it confuses too many people (understandably). We'll add a note.

Cheers!

Hey Ramsey Jiang

What you mean with that you made controller's dump uglier?
When you dump something in a controller, don't you see a new input at your profiler's bar?

Cheers!

Hey MolloKhan
You know, at the previous chapter, I could use dump in my controller. I could view a background color is black of that dump. In the twig, I also could use dump, but the dump is as the php var_dump.

After I viewed this chapter, the dump in my controller as the php var_dump. the dump in my twig, it has a black background color.

Now do you make sence what I mean in my question?

Hey Ramsey Jiang!

Hmm. This should not be the situation. You're 100% correct that, before this chapter, the dump() function in Twig was using var_dump. That is Twig's default functionality. But when you install the debug-pack, Symfony replaces this with the VarDumper component implementation (that is responsible for the pretty, black background).

But in PHP, the dump function is provided by the VarDumper component. If that component is not present, then the dump() function should not exist. And, of course, if it IS present, the VarDumper always prints "pretty". I can't think of how the dump() function would ever produce the uglier, var_dump version of the code :/. Just in case, try clearing your cache:

php bin/console cache:clear

If that doesn't work, could you post your controller code? I know it's simple - but I'm really not sure what the issue could be :).

Cheers!

Hey weaverryan

Your first part is 100% correct. Thanks what I have done before this chapter.

The second part, in my PHP, var_dump works, but in symfony4, dump() is not work. I don't why. That's why I ask at here hope someone can help me to fix it. I did cache clear, but the problem is still there.

You know, in my controller, dump() it's not work, it won't output anything. Only var_dump() works. but the output is uglier not prettier. Before this chapter, dump() in my controller works and pretty. My controller code is following:

/**
* @Route("/article/{slug}")
*/
public function testArticle ($slug)
{
$comments = [
'I ate a normal rock once. It did NOT taste like bacon!',
'Woohoo! I\'m going on an all-asteroid diet!',
'I like bacon too! Buy some from my site! bakinsomebacon.com',
];

dump($comments, $this);//dump at here is not work, it cannot do anything. Only var_dump works.

return $this->render('article/show.html.twig', [
'title' => $slug,
'comments' => $comments
]);
}

Hey Ramsey,

Please, make sure you have installed Var Dumper component with:

composer info symfony/var-dumper

IIRC, that this works in dev/test environments only. If you're in prod - it probably won't work. And keep in mind that in PHP files dump() works in a bit different way than in Twig templates: if you dump something in PHP file - you won't see the output on the page, but you can see it in the Symfony Web Debug Toolbar below.

P.S. If your output of var_dump() is just black/white, i.e. not colorful and nice - then you need to install and enable Xdebug PHP extension which makes var_dump() output much nicer.

Cheers!

victor In controller, I want to dump($var);die; - How can I achieve this? Forcing us to render a html template (so that profiler will shown) is not a good solution. What if I am working on AJAX endpoint, no html? If I am not wrong, before we could use it in controller out of the box. Correct?

Well I can create a new Service with the below function:

function mydumper(array $arguments) {
    dump($arguments);
    return new Response('<html><body></body></html>');
}

In this case it works correctly; blank screen + debug bar + my dump inside and nothing else. But is this the right way?

Hey Yahya,

In Symfony 4 there's a "dd()" function which is equal to "dump(); die;" - you can upgrade and use it. But you can totally do like you said, i.e. manually add "die;" after "dump()": "dump($var); die;" - so your output won't go to the Web Debug Toolbar, instead, it will be printed in browser.

But if we're talking about end points that return JSON - probably showing Web Debug Toolbar is not a good idea, because your JSON response is invalid in this case. If you send AJAX requests - you can either find links to profiler pages of those requests (if you hover over AJAX icon in Web Debug Toolbar) or I use Google Chrome Debug Toolbar to open the request and see its content with dumped value, but in this case probably would be better to use var_dump() or print_r() functions instead, because dump()'s output contain extra HTML for syntax highlighting.

I hope it helps :)

Cheers!

@Victor, thank you fy message but I believe I couldn't tell it properly. It is not about dd() or dump();die; It is about viewing the dump :) Here it is: I use Symfony 4.1, debug-pack and profiler-pack, all are installed. I am creating a new controller, ie. UserController and creating a new method, ie. list.

    /**
     * @Route("/users/list", name="users_list", methods={"GET"})
     * @param Request $request
     * @param EntityManagerInterface $entityManager
     */
    public function list(Request $request,
                                     EntityManagerInterface $entityManager)
    {
        $repo = $entityManager->getRepository(User::class);
        $records = $repo->findAll();

        dd($records);
    }

Boom! Blank screen. Before it was shown on the screen. Am I missing something? Check out please, I didn't decide to render a twig template, or respond in json. I just want to see the output of dump() or dd(). Blank screen!

Hey Yahya E.

If you are getting a blank screen, it means that the dd(); statement did execute, but probably your "$records" variable was empty? Try changing it to var_dump('hello', $records); die;
If that's not the case, I believe you require to install and activate "x-debug" in your system so the "dump" function works properly.

Cheers!

MolloKhan @MolloKhan Tonight, I run "composer update" that moves me from v4.1.0 => v4.1.1. Now it works as expected. So we can mark as "solved". Thank you fy help.