| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2207
|
Thu Apr 19 07:40:01 2007 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.4-1795 | Re: HOW TO change http://localhost:8080/ to an address where users can access? |
| marion wrote: | | it is hosted by franceso - i have full access to everything - i have cpanel - |
Then you have to install elog there from the RPM. See http://midas.psi.ch/elog/adminguide.html |
|
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. |
|
2143
|
Tue Feb 20 18:41:31 2007 |
 | Martin Killenberg | martin.killenberg@web.de | Comment | Linux | 2.6.4 | Hardcoded Path in Makefile | I tried to compile ELOG on Scientific Linux Cern 4.4 and found that make quits because uname is not located in /usr/bin (like it is hardcoded in the makefile) but in /bin.
Later I found that this is only the case in the svn version, in the "latest.tar.gz" from 2007/02/20 the path is /bin.
Why do you have the absolute path in the Makefile? uname should be in the default path on any system. (The same applies to "rm")
I also was confused that you only provide one rpm Package (except for debian) without mentioning for which distribution. You try to avoid dependencies, but the elogd is linked against the basic libraries libc and ld-linux, which might vary. |
|
2144
|
Tue Feb 20 21:10:28 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Comment | Linux | 2.6.4 | Re: Hardcoded Path in Makefile |
| Martin Killenberg wrote: | I tried to compile ELOG on Scientific Linux Cern 4.4 and found that make quits because uname is not located in /usr/bin (like it is hardcoded in the makefile) but in /bin.
Later I found that this is only the case in the svn version, in the "latest.tar.gz" from 2007/02/20 the path is /bin.
Why do you have the absolute path in the Makefile? uname should be in the default path on any system. (The same applies to "rm")
I also was confused that you only provide one rpm Package (except for debian) without mentioning for which distribution. You try to avoid dependencies, but the elogd is linked against the basic libraries libc and ld-linux, which might vary. |
Ups. The hard-coded /usr/uname somehow sneaked in from some temporary test. I removed it in the current SVN.
Indeed the RPM package I provide is built under Scientific Linux. The Debian port is done by someone else. Unfortunately I don't have ten boxes with all possible distributions laying around, so my possibilities are quite limited and I depend on third party help. If you want to contribute additional RPMs you are welcome. |
|
2157
|
Tue Mar 6 16:59:13 2007 |
 | T. Ribbrock | emgaron@gmx.net | Bug report | Linux | 2.6.4 | Upgrade to 2.6.4 broke quick search | Hi!
I just went from 2.6.1 to 2.6.4 and since the upgrade, the quick search drop-down menus no longer work. I can select an attribute, but when I do so, I only get an empty page with the following message:
Attachment #0 of entry #0 not found
Please use your browser's back button to go back
When I do go back, the attribute I selected is still selected, but all entries are listed. With 2.6.1, this worked like a charm.
Any idea?
Thanks in advance,
Thomas |
|
2158
|
Tue Mar 6 17:03:43 2007 |
 | T. Ribbrock | emgaron@gmx.net | Bug report | Linux | 2.6.4 | Re: Upgrade to 2.6.4 broke quick search |
| T. Ribbrock wrote: |
[...]
I just went from 2.6.1 to 2.6.4 and since the upgrade, the quick search drop-down menus no longer work. I can select an attribute, but when I do so, I only get an empty page with the following message:
Attachment #0 of entry #0 not found
Please use your browser's back button to go back [...]
|
Apparently, this must have been some session-oddity - I just logged out and got an error message about a bad URL. I then went to the base URL of the logbook (i.e. http://server:8080), chose the correct logbook and logged in again. Things work fine since. No idea what went wrong the first time round... 
Regards,
Thomas |
|