make sure products controller has an index action. if yes, check rake routes to make sure the route for /products is there.
On Aug 24, 10:33 am, Scorpio <[email protected]> wrote: > It seems I wasn't clear enough... sorry > > I mean i want the site end user (customer) to view only the product > and admin to edit it but once i complete the hobo book chapter > instructions the controller totally disappears from the end user part > of the application so doing localhost:3000/products says there is no > such root and the nav menu item disappears as well > I need the front of the app to be like any other Hobo app for a non > admin user (the ability to click on tabs and view content) and yet > divert editing functionality to the /admin subsite. Hope that > clarified things up a bit. > > You might ask why do i need a subsite at all then ? well ... there > will be admin specific functionality of editing users/orders etc. so I > wanna keep the editing to one admin panel > > On Aug 24, 6:16 pm, kevinpfromnm <[email protected]> wrote: > > > Just to expand on that, you modify the controllers for each so that > > only the appropriate actions are available. For instance, for front > > controllers that shouldn't be editing you might want: > > > auto_action :read_only > > > Which will give just an index method and a show method. > > > On Aug 24, 9:48 am, Henry Baragar <[email protected]> > > wrote: > > > > On August 24, 2010 11:35:40 am Scorpio wrote: > > > > > I've been working to create an admin subsite. The reason I'm starting > > > > a new thread on this yet again is the fact that I do not get any > > > > errors simply the effect is not what I've expected and I need advice > > > > on how to fix it > > > > OK > > > > > I flowed the Rapid rails chapter through analogy with Product and > > > > Category model resources and it all works fine and dandy but I'd like > > > > the user to see a Categories tab as well and yet have an explicit > > > > admin subsite for editing. > > > > To which user are you referring? An "application user" or an "admin > > > user"? > > > The basic idea is that the "application user" does everything through the > > > front site and the "admin users" does everything through the "admin > > > site". > > > > > (It's good that the products tab got hidden all the way because I > > > > don't want to view by product on the user end). How do I make it so > > > > that view is still on the user front and edit is on the admin front > > > > while keeping the code DRY ? > > > > If the "application user" never edits the product, then the edit page only > > > needs to be in the admin site. > > > > If you want a custom tag (e.g. view-page for Product) to be used by both > > > the > > > "application user" and the "admin user", then define/extend the tag in the > > > app/views/taglibs/application.dryml. Any tag that is only for the > > > "application user" should be put into app/views/taglibs/front.dryml; and, > > > any > > > tag that is only for the "admin user" should be put into > > > app/views/taglibs/admin.dryml. > > > > Hope this helps. > > > > Henry > > > > > Thanks in advance (oh my I've been asking a lot of questions lately) > > > > -- > > > Henry Baragar > > > Instantiated Software -- You received this message because you are subscribed to the Google Groups "Hobo 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/hobousers?hl=en.
