To keep things simple for the moment, I created a file in /home/arthur/ RubySites/depot/app/views/info with a filename of index.html.erb and put the following code into it:
<h3>Info Functions</h3> <a href="http://localhost:3000/info/who_bought";>Who Bought</a> Of course when you click this hyperlink, the file who_bought.html.erb responds with: ActiveRecord::RecordNotFound in InfoController#who_bought Couldn't find Product without an ID So, my guess would be that I need to "test" for the condition where the ID is missing and write some code in that file that loops through the products table and creates hyperlinks such as: <a href="http://localhost:3000/info/who_bought/1.html";>Pragmatic Project Automation</a> for each book title in the database. I have to think about the syntax for all of that...any ideas? Arthur On Apr 16, 10:19 am, Ar Chron <[email protected]> wrote: > eengnerd wrote: > > I've completed the chapter on Internationalization successfully, but > > found out just recently that the "Who Bought" function produces an > > error page that looks very ugly when someone enters a product ID that > > does not exist. My preference would be to design the app to have a > > list of hyperlinks presented when you visit the URL, > >http://localhost:3000/info/ > > that describes the list of "Info Functions" (eg "Who Bought" for > > starters). Then when it takes you there, > >http://localhost:3000/info/who_bought/ > > you would see a list of Book Titles as hyperlinks so that when you > > click on a book title, it redirects you to the appropriate URL for > > seeing a list of customers "who bought" that book. In this way I > > could avoid the user's temptation to use "non-existent" product ID's > > before it becomes a problem. But I have no idea how to go about > > creating these features. I'm open to some ideas. > > > Arthur > > Sounds like the hard part is done, now it's just coding... > > So, where does ...info/ go to? > > You'll need a view for that (info.html.erb?), and you'll have to get > there somehow (think routes) via some controller (which to use... or > create?) > > The list of book titles for 'Who Bought' smells an awful lot like a > generic book 'index' view, with maybe a twist on the rendering in the > erb. > > If a book knows who bought it, listing the people who bought a book > smells like an adaptation of a book 'show' view. > > Just get that info page working, then extend from there. > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
