Take a look at this snippet from Bryan's tutorial: http://screencast.com/t/m73Td1jf
Let us know if this helps... - Owen On Sat, Jan 22, 2011 at 1:09 PM, Owen Dall <[email protected]> wrote: > You should be able to just use the Hobo permissions logic in each model. > Hobo should take care of what can be viewed, by whom. > > Unless I am missing something.... > > -owen > > On Sat, Jan 22, 2011 at 11:48 AM, Henry H <[email protected]> wrote: > >> Okay I followed the examples and got a little further, but I'm not >> able to figure out how to limit the index views to only the user who >> owns those items. Am I supposed to define my own index function, use >> the hobo_index command, and add a scoping filter to the controller? I >> tried the following, but it didn't know who the acting user was... >> >> def index >> hobo_index(model,:conditions =>["user_id == ?",acting_user]) >> end >> >> Can anyone post an example? >> >> Thanks, >> Henry >> On Jan 20, 3:47 am, Henry H <[email protected]> wrote: >> > Thanks Bryan. I'll take a look. >> > >> > On Jan 19, 9:22 pm, Bryan Larsen <[email protected]> wrote: >> > >> > >> > >> > >> > >> > >> > >> > > You're looking for the "owner actions". >> > >> > >http://cookbook.hobocentral.net/manual/controllers#owner_actions >> > >> > >http://cookbook.hobocentral.net/tutorials/agility#project_ownership >> > >> > > I know the pdf's have a section corresponding to that agility section, >> > > but I don't know which it is. >> > >> > > Bryan >> > >> > > On 11-01-19 08:30 PM, Henry H wrote: >> > >> > > > I want to built a site which allows multiple users to enter >> > > > information which is only available to themselves. I'm getting >> > > > permission issues which cause errors when I create items which >> require >> > > > the owner to be the current user because the index pages try and >> list >> > > > items from other users. >> > >> > > > I've gone through both PDF tutorials and was able to follow them >> quite >> > > > easily (great job on this folks!). Can someone post a quick example >> > > > of how I should be approaching this particular usage scenario? I'm >> > > > guessing I have to write something custom, but I'm hoping this is >> > > > somehow built into the hobo framework so it's easy to have a user >> just >> > > > see the things they are creating, editing, etc. versus all things >> > > > created by all users. >> > >> > > > Thanks so much, >> > > > Henry >> >> -- >> 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]<hobousers%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/hobousers?hl=en. >> >> > > > -- > > > - Owen > > Owen Dall, Chief Systems Architect > Barquin International > www.barquin.com > Cell: 410-991-0811 > > -- - Owen Owen Dall, Chief Systems Architect Barquin International www.barquin.com Cell: 410-991-0811 -- 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.
