| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2058
|
Thu Nov 9 21:22:27 2006 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Problem with large entry size |
| Dimitrios Tsirigkas wrote: |
| Stefan Ritt wrote: | | What about a threshold for the "All" display? If a logbook contains less than, let's say, 500 entries, the "All" link is displayed, and above 500 entries it's hidden. Would that make sense? |
Hi Stefan,
Sorry for the late response, I was away for a few days. Yes, I think that this would make perfect sense, especially if the maximum number of entries was configurable.
Cheers,
Dimitris |
Agree. So I implemented the new config option All display limit. The default is 500. So you can see that at this forum, the All link is not shown any more, since the logbook contains more than 500 entries. The promised performance improvement of the page display will take me some more time, but I will not forget it. |
|
2082
|
Sat Nov 18 11:19:14 2006 |
 | ather khan | ather.khan@cpjeddah.com | Question | | | Attributes according to users | Hi,
Is it possible to have certain attributtes available to certain user in one log boolk.
We have log book where the supervisor assign jobs to employees and we want only supervisor to have assign to attributes available and others only to view it.
thanks,
Ather |
|
2083
|
Sat Nov 18 17:13:22 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Attributes according to users |
| ather khan wrote: | Hi,
Is it possible to have certain attributtes available to certain user in one log boolk.
We have log book where the supervisor assign jobs to employees and we want only supervisor to have assign to attributes available and others only to view it.
|
You cannot restrict the modification if certain attributes, but you can restrict edits in general with the command
Allow edit = <name of admin>
You can also restrict the New, Delete, etc. commands to be only executable by the supervisor. |
|
2110
|
Sat Jan 13 17:35:45 2007 |
 | Exaos Lee | Exaos.Lee@gmail.com | Question | | | How many topgroups can be defined? | I defined 6 top groups in my cfg file as the attachment.
But ... It doesn't work as I wanted.
The 4th and 5th groups need login. But when I clicked the 4th or 5th group, the login isn't needed.
And the 4th and 5th password files are not generated automatically. |
|
2117
|
Wed Jan 17 12:55:07 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: How many topgroups can be defined? |
| Exaos Lee wrote: | I defined 6 top groups in my cfg file as the attachment.
But ... It doesn't work as I wanted.
The 4th and 5th groups need login. But when I clicked the 4th or 5th group, the login isn't needed.
And the 4th and 5th password files are not generated automatically. |
When changing groups and to groups, one can sometimes get fooled by old cookies. Delete all your cookies and try again. You can also install the "Tamper Data" extension for Firefox (https://addons.mozilla.org/firefox/966/) which shows you which cookies are sent to your ELOG server. This should reveal the problem. |
|
2153
|
Fri Mar 2 16:39:22 2007 |
| Justin Ellison | justin@techadvise.com | Question | | 2.6.4-179 | Hiding attributes in Detail view? | First off, thanks so much for this product. It works excellent for us as a server activity log. I have a question, which depending on the answer, might be a feature request 
As I mentioned, we use elog as a serverlog. Sometimes, but not always, we will have a Bugzilla bug # that is associated with the log entry. We then take that bug #, and build a link to our bugzilla server displaying the bug. Here's the relevant config entries:
Attributes = Author, Classification, Subject, Bug Number, Environment, Server, Bugzilla
...
#Make the list table narrow enough to fit in the browser
List display = ID, Date, Author, Subject, Server, Bugzilla
...
#We take in a Bug Number from the user, then calculate a Bugzilla link from that
Change Bugzilla = <a href="http://bugz:4545/bugzilla/show_bug.cgi?id=$Bug Number">$Bug Number</a>
List Change Bugzilla = <a href="http://bugz:4545/bugzilla/show_bug.cgi?id=$Bug Number">$Bug Number</a>
Hidden Attributes = Bugzilla
So, on new entry, the user has the option to enter a Bug Number. Bugzilla is not displayed because it is derived. In list view, Bug Number is not displayed, but Bugzilla is, providing a handy link to the bug on a different server.
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.
Is there a way to hide Bug Number on the view page? |
|
2160
|
Fri Mar 9 22:14:57 2007 |
| Justin Ellison | justin@techadvise.com | Question | | 2.6.4-179 | Re: Hiding attributes in Detail view? | | Any takers? |
|
2161
|
Mon Mar 12 20:35:17 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | 2.6.4-179 | Re: Hiding attributes in Detail view? |
| Justin Ellison wrote: | 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.
Is there a way to hide Bug Number on the view page? |
In revision 1809 I implemented the options
Show attributes = ...
Show attributed edit = ...
The first one is for the log entry page, the second for the entry form. This way you can distinguish between the bug number and the link. The old option Hidden attributes has been dropped, since it has the same effect now as Show attributes edit. |
|