With the layout ready to go, we are ready to consider how to display posts in a variety of useful ways, so that both reporters and developers can easily sift through what has already been reported, the report’s status, and any discussion regarding that report.

To begin, let’s start by quickly supply the reporters a list of their own reports.  That way they can track the status on those reports as well as respond to any enquiries for further details.

Onwards!

Lisa,

At the beginning of the new “by_author” template, you have the code

instead of

Did I miss something along the way?

Thanks Much!

Jesse

Woops.  When I was first laying the template groundwork, I had used doctype.  As I wrote the article, I chose to make it more generic and, well, forgot to update my own templates. 

I’ve updated the articles and my templates.  Thanks for pointing it out, Jesse.  I should have caught that sooner!

I just wanted to make sure I didn’t miss something important!

I’ve said it before - These are so helpful for me!  I check my rss reader every day to see when you add another episode!

Lisa,

Do you plan to add any conditionals to check if a user is logged in?  I noticed that if you aren’t logged in and you click on the “My Bugs” link, it displays an error because it is looking for the logged in user.

Jesse

We’ll see; and of course, people can customize this beyond the tutorial - the tutorial is just intended as a starting point and learning tool, after all. =)

I’m not sure if it’s a typo, or if it’s intended to be this way, but if the whole point of this specific tutorial is using segments to break the report down on a user by user basis, and we’re using {segment_3} to filter out the bug list based on the username provided, then shouldn’t:

not be:

Otherwise, even if we did put in a different username, we’d still have it display out logged in username at the top?

If I’m missing something, disregard, but either way, thanks for the great tutorial so far!

Joe

Edit: Oops! Forgot to format the code segments appropriately!

Nope, it’s not a typo.  Remember, much of this tutorial is about learning the process. Not only will we create things, but some things may change down the line if needed as we hit them.  I am not indicating if this is one of them, but this particular tag is included here in part to alert people to its existence.