Starting in Symfony2: Course 2 (2.4+)

Oh right above these comments ! sorry, i've found that ! :P

Hey keefekwan!

Yes, there is a CSS file missing, which means that if you're coding along, the registration form works fine, but doesn't look as nice as in the screencast. Thanks for catching that! I've opened up an issue and we'll fix it and make it look pretty again for the next version: https://github.com/knpunive...

Cheers!

Thanks for commenting on this. I ran into the exact same problem and was wondering the exact same thing. My css skills are still on the new side, so hopefully 2.4+ comes out soon. :P

Actually if you take the login.css file and copy the text into a register.css file and replace .login with .main-block you end up with something that doesn't look entirely terrible. Particularly if you just want something that will get you through the tutorial.

Hi Edison!

So glad to hear you're going through all the tutorials - you won't regret it :).

A few things about your situation:

1) Most of the time, routes match only on URL. If you have a route whose path is /create, then if you go to /create, it will match. Good work on using router:debug to investigate this.

2) Sometimes - and this is totally optional - you might decide to say "Hey, I'd like /create to only match on POST requests" (e.g. form submits). That is what the "_method: post" thing in the route is doing. This means that if you go directly (e.g. by just putting /create in your URL and hitting enter) to the URL, you will get this "Method not allowed" exception. You have matched the URL, but this URL only allows POST requests, and you are using a GET request.

3) Why is this happening in your case? Well, since this is a form submit, you probably *do* want to respond to only POST requests (though in practice, if you also allowed the route to respond to GET requests, it would simply look like the user filled out the form blank and submitted - so they would get validation errors and the form would re-render, so no big deal). My guess is that you're missing the method="POST" part of your <form> tag, which is causing the form to submit via GET, causing this error.

I hope this helps you discover discover your issue.

Cheers!

YESSSSSSSSSSSSSSSSS! You are the Best! Haha wow. :)

1st. Thanks for your rocket answear, you always do that!
2nd. You solved my problem, you were right, in my <form> tag was the solution!

Cheers!

Hey James!

Aw, I'm really really happy to hear about your success. The third episode will hopefully be done within the next week and a half. BUT, it's a free upgrade, and the differences should be pretty small - so if we're holding you up, I'd go ahead and grab episode 3 now :).

Cheers to you!

Hey Ryan,

Any updates on the 2.3 screencast?

Hi James!

We've just updated Episode 3 with the new, much nicer format and updated it for 2.2. We'll also do the same for episode 4 this week. The updates for 2.3 will come after that :). But, again, don't wait - there fortunately haven't been that many changes with the new versions of Symfony (mostly new features, that are outside of the project we're building). When we do update, we'll point out some new feature and some other small changes. That's nice, but not worth waiting for if we're making you wait.

Cheers!

Awesome Ryan, *insta-purchase*, thanks! :)

The fixes (https://github.com/knpunive... are up on live on the site! Woo - thanks!

Hi there!

Sorry for the issues, but we can definitely get things working :). A few things:

1) The issue from going from episode 1 to episode 2 is actually do to a minor change that we made between episodes 1 and 2 to the routing. It's a small change, but if you're following straight from episode 1 to 2, then some URLs will have changed. We should

Sorry for the issues, but we can definitely get things working :). A few things:

1) The issue from going from episode 1 to episode 2 is actually do to a minor change that we made between episodes 1 and 2 to the routing. It's a small change, but if you're following straight from episode 1 to 2, then some URLs will have changed. We'll be fixing in the future - so apologies. What you should do is download the code for episode 2 and use the "start" directory as your new starting point. For example, in episode 1, you have URLs like `/event`, but in episode 2, that same page is actually at `/`.

2) More broadly, Symfony follows some very specific (and configurable) rules after a successful login. Some of it is explained here: http://symfony.com/doc/curr.... But basically, it tries to redirect you to the last page you tried to visit before hitting the login page. If there isn't any (i.e. you clicked directly to the login page), then it falls back to just "/". If that's not what you want, that's configurable in a few ways (shown in that entry).

Hopefully this gets you going again! If you have any other issues, just ping us here :).

Cheers!

Hi Ryan, Thanks for this. I struggled so much with it and tried so many different things to get it to work that I probably messed it up more than I helped. In the end, I scraped everything and restarted lesson 1 from the beginning to have a 'clean' copy. I saw what you mentioned about the "/event" becoming "/" and I made the change - just about to restart lesson 2 now. I don't know how close you are to Fabien Potencier but I would suggest that the file routing.yml in app becomes approuting.yml which would distinguish it from the bundle routing.yml file and avoid some potential confusion.
Regards.

Edit 1
Still does not work with the change. What I do is I listen to the video, pause it and do all the changes as they appears on the screen (basically I do every click she does and expect to see the same page, errors, etc). Right now, the lesson breaks down at 9:10. First, I'm losing the background - I have the login form on the top left on a blank white screen (seems like it cannot find the '::base.html.twig'); second on typing user and userpass, I get a link to "/" which shows me the event page whilst the video shows the /new page. If I press "create new event", I get: An exception has been thrown during the rendering of a template ("Unable to generate a URL for the named route "event" as such route does not exist.") in EventBundle:Event:new.html.twig at line 6. And of course it does not exist because I changed it to "/" to make the first part of the program to work.

I guess progressing throught the lessons(even with the above-mentioned change) is not an option and for the sake of not wasting too much additional time, I will resort to copy the 'start' files' and see if I can get this to work. That said, it is not very helpful if you cannot continue from where you left because, as a beginner, it is not evident what parts have been changed in the background. (also, not your fault obviously, but the error messages are hardly helpful: an error message on line 1883 on a class that I have never seen does not really tell me where is the problem)

Additional notes: Using the start files is also not straightforward as you have the JMS security bundle in the AppKernel.php and nowhere in lesson 1 or 2 these files are used. Not hard to remove from the kernel but just copying the files will generate an error as the bundle won't be found.

System: Windows 7 64 bits with IE9.

Edit 2

To use the 'start files' you will have to:
1- delete any references to JMS in the AppKernel.php
2- delete any references to JMS in the security.yml
3- delete reference to trust_proxy_headers in the config.yml

Once you've done that, you now access your application with ".../web/app_dev.php/" instead of
".../web/app_dev.php/event"

Hey there!

Ok, let's see if I can help out :).

1) The missing assets aren't a missing or not-found "::base.html.twig" - if that file is missing, you'll get a big error. Instead, I think your CSS files just aren't being loaded. Be sure to run this command:

php app/console assets:install

Normally, this is run automatically for you when you run "php composer.phar install", but the very first time you run that command, it may fail right at the end if you haven't already copied app/config/parameters.yml.dist to app/config/parameters.yml. That's actually totally fine, but make sure you run the above command, it'll probably fix your CSS files :).

2) Yes, a few things change between episode 1 and episode 2 - that's something we'll fix in the future. Until then, use the "start" directory from episode 2 to work from. The changes between the episodes are actually pretty minor: we added some stylesheets and tweaked the names and paths for a few routes. That's not much, but it is enough to mess you up and give you the errors you're seeing - so apologies!

3) I was able (just now) to download the "start" directory for episode 2 and get things running without any issues. You're right that we don't use the JMSSecurityBundle, but it is included in the composer.json file and downloads just fine. Based on what I'm seeing, it almost looks like you upgraded your Symfony app to Symfony 2.3, in which case the JMS stuff is *not* included, and you would need to remove the trust_proxy_headers. That's fine, but hopefully it helps to know why that error would be happening :). If you use the "start" directory, you'll get a copy that will work just fine.

Cheers!

Hello!

I have same problem: I have seen in video 2
".../web/app_dev.php/" is showing event list, but in episode 1
".../web/app_dev.php/event" did that, so I tried to change my code to do
exactly as the code in episode 2 does, but no results. Then I tried to
copy the code from "start" folder from episode 2, no results again -
blank page have been showed then.(I also tried all the steps below Edit
2)

I really like all these courses and I would like to learn a
lot from them, but I can`t continue lesson if I have this problem. Is
there any solution for this problem?

Best regards.

Hi, by copying all the files from the Start directory and doing the modifications mentioned in EDIT 2 above (assuming Symfony version 2.3.6) you should be able to follow just fine. I have not finished it yet due to time constraints but so far I am a third through it and everything is exactly as in the video. From where I am now in the video all the 'routing issues' are now dealt with as it is now moving into loading users from the databse. Do not copy just a few files here and there, replace whole directories (app and src) all at once (it'll also save you a bit of typing along the lesson!). Best!

Great advice frimousse! frimousse when you start using the "start" directory, are you still accessing the site via by hitting the "app_dev.php" file in your browser? That's very important - because if you don't execute this file, you're executing Symfony in the "prod" environment, and Symfony doesn't show you those errors (which could cause you your white screen problems).

To be sure, one trick you can do (if you have PHP 5.4) is to use PHP's built-in web server. From the command line at the root of your project, try:

php app/console server:run

Then, you can access your site via "http://localhost:8000/app_dev.php". See if this helps out. And if not, feel free to ping back here or email me directly (ryan@knplabs.com) and I'll make sure we get things working :).

Cheers!

Hey Rob!

Thanks for the comment - I really appreciate it! We try really hard to make these tutorials full and complete :). Of course we have this pesky episode 1 to episode 2 transition issue - so sorry about that!

Because of that, I want to make sure everyone is able to get things working. By using the "start" directory from the code download as your starting project before coding with this tutorial, you should be just fine. This means using all of the contents of that directory in place of the project you built in episode 1. In reality, there aren't that many things that changed between episode 1 and 2, but just to be safe, use the "start" directory as your new project.

About the stylesheets in "EventBundle\Resources\views\layout.html.twig" - these were just moved to app/Resources/views/base.html.twig. So you shouldn't need to re-add them to layout.html.twig. But do be careful: if you override the "stylesheets" block in any of your templates (e.g. layout.html.twig or index.html.twig), you'll completely replace the stylesheets from base.html.twig, unless you use the parent() function (see: http://symfony.com/doc/mast....

If anyone has any issues with using the "start" directory in the code download, you can keep pinging us here. I have re-tried it a few times, and everything works perfectly without making any changes. Though if you do have problems, we can work through them together :).

Cheers and thanks!

Sorry, I guess I didn't copy across the new base.html.twig file, and perhaps I was wrong about the app folder. Regardless, it ended in a mess for me; perhaps because I tried to fix it before seeing some of the advice in the other comments on this page and I just made things worse.

I don't want to be negative though, these really are good tutorials. Thanks for making them :-)

Hey @Ant!

These are awesome ideas - we're planning now on how we can show changes or notes to you guys when things (like versions of Twitter Bootstrap) change. Like right now, everything still works fine from start to end, but you'd need to go find the old version of Twitter Bootstrap to match the markup.

To that end, would you have a few minutes to chat about this? I'd like to hear you (or anyone's experience) and see exactly what things we can do to make things the clearest. I don't have your email, but if you do have some time, please email me at ryan@knplabs.com!

Thanks for the comments!

Or 4 versions, one corresponding to the end of each screencast

Hi Rob!

Hmm, that does sound odd, but I'm sure we can debug it and figure out what the issue is! Can you open up an issue here: https://github.com/knpunive... and maybe include a screenshot of what it looks like when you run the tests in the different scenarios?

Thanks!

Hi Ryan, thanks for your offer to help. However, I have resolved the problem.

I re-installed phpunit to make sure all the paths were correct (I'm using MAMP Pro) and updated the phpunit path in the PhpStorm project config. This seemed to fix the initial problem, but I then had an internal server error to do with templating (although the page worked correctly in the browser). After much faffing about, clearing the cache, restarting MAMP and restarting PhpStorm it suddenly started working correctly.

Awesome, cheers Rob!

Hi Nick!

This is because some routes changed slightly between episode 1 and episode 2 of our series. For example, /event/new changed to be just /new in episode 2. So, sorry about that confusion :). There are a few other related comments on this thread about those minor changes.

If you are coding from episode 1 to episode 2 directly, there are a few changes you'll need to make to your code, which I have documented here: https://github.com/knpunive....

If anyone has any issues, don't hesitate to ask!

Thanks!

Hi Mathias Strasser!

A blank page is very strange, and Symfony should at least be giving you an error page. It's probably some small misconfiguration. Can you open up an issue here: https://github.com/knpunive... Then we can work together to see what the problem is :). Obviously, double-check to make sure that you're executing the `app_dev.php` script, so that you see errors. Also, check your `php.ini` configuration to make sure that `display_errors` is set to true so that PHP errors are showing up.

Cheers!

Thanks in advance :)

github.com/knpuniversity/sy...

Hi nglaser power

Yes, you're right :). Both bind() and handleRequest() work, but bind() is deprecated. Fortunately, it won't be removed from Symfony until version 3.0.

But, we do want to keep that updated! I've opened up an issue to track that change and any other form-related changes we may need: https://github.com/knpunive...

Thanks so much!

Hi,

Now, bind redirect to submit.
So why use handleRequest ?

Hey Mathias!

Yes, there were actually 2 changes to bind:

1) bind was renamed to submit
2) Passing a Request object to submit was deprecated. It's still completely valid to pass an array of data to submit (that's its purpose), but if you want to pass a Request object, use handleRequest. The reason for this second change was performance - one function for handing processing the Request object (handleRequest) and another for handling data arrays (submit).

The big takeaway is to use handleRequest almost always. The only exception is if you are passing the array of POST data directly (pretty uncommon), then use submit(). We'll be working to update this screencast with the latest and greatest over the next several weeks too :).

Hope that clarifies!

Hi again nglaser power!

Do you mean calling $user->setRoles() on the fixtures? It *is* true that User::getRoles() must return at least 1 role in order for you to be authenticated after logging in as that user. However, in our implementation of getRoles(), we *always* return at least ROLE_USER, even if the roles property is actually empty in the database. So, you shouldn't need to call setRoles() in the fixtures - having empty roles is ok - you'll always at least have ROLE_USER :). Reference: http://knpuniversity.com/sc...

Are you seeing something different?

Thanks!

Hi John!

Think of an entity as representing each row in a table. Assuming you have a Product entity class, if you create a new Product object and save it, that creates a new row in the product table. When you query for 10 products, you get to Product objects.

Think of the repository as the class that holds query logic. You create methods on your ProductRepository class, for example, like "findAllAlphabetical" that make a query to return some Product objects.

So to your question, you'll likely write custom code in both your entity and your repository. If you need make a new query, create a new function in your repository that queries exactly how you need. But when you're getting information about 1 specific row in some table (e.g. a Product), then you might add a new function to your entity. For example, imagine I have a BlogPost entity with a publishedAt field, which is set to the DateTime when the BlogPost should become published. If it is a date in the future, then it's not published yet. As a convenience, you might create a new function inside your entity called isPublished, which looks something like this:

public function isPublished()
{
    // check if the publishedAt is in the past
    return $this->publishedAt < new \DateTime('now');
}

This custom code is concerned entirely with the data from this 1 BlogPost, so it fits nicely in the repository.

Hope that helps out a bit!