Right, permissions should be set appropriately on fields that should not be viewable by others.
On Jun 13, 8:58 am, Dean <[email protected]> wrote: > Note that this only hides the menu item. It does not prevent users > from accessing the details of users by guessing the URL. > > Dean > > On Jun 11, 4:33 am, kevinpfromnm <[email protected]> wrote: > > > Do this but you can also add it permission checks as to whether to add > > different nav links. > > > <nav-item with="&User" if="¤t_user.administrator?" /> > > > On Jun 10, 12:09 pm, storitel <[email protected]> wrote: > > > > Copy the definition of main-nav from the taglibs pages.dryml into your > > > application.dryml. Then delete the offending nav-item definition in > > > your application.dryml version. Basically any definitions you put in > > > application.dryml override the taglibs versions > > > > On 10 June, 14:31, Mark Sobkowicz <[email protected]> wrote: > > > > > I've been working through the Agile Project Manager tutorial and trying > > > > some additional things I'd like to use in my application. I'd like to > > > > hide the User tab completely from my users, but have it appear if the > > > > user is an admin (me). I've tried a number of things, but can't get > > > > this to work. It easy to remove functionality so that users can't > > > > actually do anything from the User tab, but can I hide it from them to > > > > clean up the UI? > > > > > Mark Sobkowicz > > -- 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.
