Re: Hiding attributes in Detail view?, posted by Stefan Ritt on Mon Mar 12 20:35:17 2007
|
[quote="Justin Ellison"]The only thing that isn't working as I'd like is when someone views a log entry. Both Bug Number and Bugzilla show up in the attributes.
This isn't a huge deal, it's just showing redundant data.
|
|
Re: Hiding Comments on the Logbook Selection Page, posted by Stefan Ritt on Tue Mar 24 11:44:10 2009
|
Adam Blandford wrote:
|
|
Re: Hide logbook tab when not authorized, posted by Andreas Luedeke on Wed Aug 23 11:36:22 2017
|
Hi Stefano,
I think your assessment is correct: it is not possible to hide a logbook based on your read/write privileges.
And I'm not
even sure that this would make much sense: at least you need to be able to get to the login page of the logbook.
But if you don't have |
|
Re: Hide logbook tab when not authorized, posted by Stefano Bonaldo on Wed Aug 23 20:09:39 2017
|
Hi Andreas,
many thanks for your answer. I partially agree with you, because sometimes "for privacy" of my working group I don't want that
other users (external users) know the existance of the other logbooks. |
|
Re: Hide logbook tab when not authorized, posted by Andreas Luedeke on Thu Aug 24 11:08:43 2017
|
Well, Stefan would need to answer that. But if you are good with C-programming, you might implement it yourself?
There is a way to implement it; but it makes your installation a lot more complicated: you can have two ELOG servers. The first has all logbooks
but requires authentification to read any. The second has only the public logbooks, and they are mirrored from the first. |
|
Re: Hide logbook tab when not authorized, posted by Stefan Ritt on Thu Aug 24 11:46:30 2017
|
Hi Stefano,
that's what top groups were made for. So make a top group for yourself, and nobody will be able to see them without having the proper URL.
Hiding logbooks from the logbook selection page is not possible since when people bring up that page, they are not yet logged in, so elog does not know |
|
Re: Hide logbook tab when not authorized, posted by marijn lucas on Thu Oct 24 16:38:27 2019
|
*** edit ***
I solved my problem by removing the guest options from the logbooks ('Guest menu commands' and 'Guest List Menu commands'), this
forbids any unauthorised user to see the content of the concerned logbooks. This is what I needed. |
|
Re: HelpELCode needs to be present in "Menu commands"?, posted by Stefan Ritt on Mon Jan 9 20:19:32 2006
|
[quote="T. Ribbrock"]Another little issue I came across was this: I'm using "Menu commands" and "Guest Menu commands" in my configuration. When I logged
in and started to create a new entry, clicking on the URL that is behind "ELCode" at the bottom of the screen (and accesses the help for the ELCodes) resulted
in a "command denied". The only way to get around this was to add "HelpELCode" to "Menu commands" - but now it also shows up in the menus, which is not |