Could you have a look at the sql log in the web debug bar when you are on the 404 page? There you will see the query that is used for fetching the job. What does this query look like? What happens when you try this query directly in mysql (e.g. using phpmyadmin)?
Claudia On Jul 31, 6:24 pm, Mauricio Rivera Schneider <[email protected]> wrote: > Hello, > > I'm working with the Jobeet tutorial and I'm having a little problem in > *day 6*. Everything works fine until I get to the "Secure the Job Page" > <http://www.symfony-project.org/jobeet/1_4/Doctrine/en/06#chapter_06_s...> > section. > > I added the code to the files just like the tutorial says, but I still > *can access* the expired job (I'm _not getting the 404 page_ as it > should). The url I'm using is the > following:http://jobeet.local/frontend_dev.php/job/sensio-labs/paris-france/20/... > > I made sure the ID is the correct in the database, also the fixtures are > correct and so it's the value of "expires_at" field. I verified it > running the SQL code |SELECT id, token FROM jobeet_job WHERE expires_at > < NOW().| > > Also, if I delete the function from the JobeetJobTable I don't get any > error when using the route pattern to access the expired job. > > These are my files: > > JobeetJobTable.class.php :http://pastebin.com/g9C2b8PP > apps/frontend/config/routing.yml :http://pastebin.com/bD7fA9JB > > Thanks in advance for any help you can provide. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
