Twig Templating for Friendly Frontend Devs

Thanks for the typo catch! We've updated activity 1 :)

Hi Dennis!

Can you explain a bit more what you'd like to see and why? Are you referring to the Twig filters - i.e. having a page to see the before and after affects of applying the filters? Or are you maybe talking about the activities? If you have a few minutes, I'd love to chat - you can email me at ryan@knplabs.com.

Thanks!

Nice catch! We've got that updated :)

Hey Danny!

I just hit you up by email, but in case anyone else has the same question, make sure you change the URL to execute the index.php file - so in your case, http://localhost:8888/twig/start/index.php. That file then executes templates/homepage.twig (so make sure you rename homepage.php to homepage.twig - we do that in the first chapter).

Also, to code along locally, you'll need to download Composer (https://getcomposer.org/dow... into the root of the project (i.e. the "start" directory) and then run "php composer.phar install".

Cheers!

Hey again!

I wanted to make things even a little easier, so I've just updated the code download. If you re-download, you won't need to worry about the "Composer" step above. The README.md in the code download also has details on how to get everything up and running. If you have any issues, let me know and we'll make sure we get them ironed out.

Cheers!

Hey Steve,

Probably you left a challenge as not answered or not viewed chapter, look for checkboxes opposite chapter titles in the table of content. If you're still can't find a skipped thing, let us know your email registered on KnpU and we'll help you to discover missing thing :) You can send us your email directly to hello@knpuniversity.com or via our contact form https://knpuniversity.com/c... to avoid send it publicly in comments.

Cheers!

Have done that Victor, thank you

Great! Congrats with complete completing of the course ;)

Cheers!

Hi there!

Actually, it's not *really* possible. The reason is that, strictly speaking, Twig just returns text. But to redirect, you need to set a 301/302 response with a Location header. That kind of logic is done in whatever layer is actually *calling* Twig.

The same seems true on your case - when I access a page (and you look up the page in the database, for example), you should determine before calling Twig that this is a page that is just a URL there and redirect in PHP.

Now, technically you *could* redirect in Twig just by writing some JavaScript and printing out the target URL via Twig inside a JavaScript string. That'd work just fine - it's a bit of a hacky way to do it, but I'm not here to judge ;).

Good luck!

Hi John!

It looks like your answer was right - the grading was too tight! I've fixed the issue (https://github.com/knpunive... and it should look good now. The rendered dump will look a little ugly (since we're showing the HTML source, not the rendered HTML) - we'll add a rendered HTML view soon that'll make it look better :).

Thanks for reporting the grading bug!

Hi Ryan, cheers for the update. I think there is another small issue here: http://knpuniversity.com/sc... I don't think the product object has the "postedAt" variable sent to it.

Thanks again John - the activity code wasn't updating correctly. It should be better now, but I'm going make some changes yet to be sure.

Again, thanks for letting us know :)

Hey TorstenMaas!

Great question actually - I've seen this confuse people in the past! Basically, both work, and are identical. BUT, {% include ... %} was the original syntax and {{ include ... }} was added later, and in general, is preferred. Why? Well, since {{ ... }} prints something, it makes sense just to make include() a function that you print... there's really no reason for there to be a special tag (i.e. {% ... %}) for it.

So, you can use either, but {{ include }} is preferred! The challenge should allow you to have either - if you were having issues, it may have been related to a challenge bug in a deploy that we did last night (which is now fixed).

Cheers!

Hey there!

Thanks about the videos :).

So when you're using Twig standalone, it's not concerned with how you create links from one page to another. It really can't be - because it doesn't necessarily know that "about.twig" lives at /about and "homepage.twig" lives at "/". So, it's your responsibility to make the links between the pages.

But, I have a feeling that I'm not actually answering your question :). So let me know if I'm not and pass more information - like what your link code looks like and any errors, etc.

Cheers!

Hello. Thank you for you reply. Correct, my issue is to render the pages. I have created arrays in my app.php file, example:

    echo $twig->render('index.html.twig', array(
     'item'=>array(
            'home'=>array(
                  'title'    =>'Home',
                'url   '=>'/',
              ),
             'about'=>array(
                   'title'  =>'About us',
                 'url'   =>'about-us.html',
               ),
          )
      ));

Main
thing is i'm not sure how to link then from the html, i have tried
adding on the {{ item.about.url }} block, but doesnt seem to pick it up.

I'm sure it's something pretty basic and simple, but have been struggling to make it work.

As a ref I've followed your video Twig-The Basics...

Do you think you could help me out with this?

Thank you very much, really appreciated.

Thank you!

Hi there!

Actually, you're doing everything perfectly. I've copied your code into a gist so it's more readable (code isn't so great in the comments): https://gist.github.com/weaverryan/26c8166d16454b4c0829. And basically, what you're doing is perfect, so it should be working just fine.

Are you getting an error or just no value is printed? Also, try simply putting:

{{ dump() }}

temporarily. This will dump all variables you have access to. This will help you make sure that you have access to the variables that you think you have access to.

Let me know what you find out!