| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1400
|
Wed Aug 31 22:02:46 2005 |
 | Martin Lindjärv | martin.lindjarv@emta.ee | Bug report | Windows | V2.5.9-4 | password forgot kills elogd |
Hi!
At first, thanx for this software!
But i found a bug or something like that. I installed elog on win2003 and winxp with default settings. And everywhere i had same problem - when forgot password is used it kills elogd. Error what is reported in EventLog is "Faulting application elogd.exe, version 0.0.0.0, faulting module elogd.exe, version 0.0.0.0, fault address 0x0002f1ee." and thats all. For testing tried newest beta too but it seems to have same problem.
i can insert my email address and when i click submit it wait's for some time and then gives 404.
Any kind of info would be good... |
|
1399
|
Fri Aug 26 13:08:10 2005 |
 | Heiko Scheit | h.scheit@mpi-hd.mpg.de | Request | | | something for the wishlist: 'Recent Changes' |
Something for the wishlist:
A 'Recent Changes'-link (option) that lists entries that were changed
recently, where 'recent' can be changed from 1,2,3...(some maximum)
days. |
|
1398
|
Mon Aug 15 12:54:56 2005 |
| Michael Husbyn | michaelh@online.no | Question | Linux | 2.5.9-2 | Re: Omitting some fields in e-mail |
>
> > I added the option "Email attributes = <list>" for that. So you can specify
> >
> > Email attributes = UA, Pri, Status, Oppdragsgiver, EpostTil, Tittel
> >
> > which also sets the order of the attributes. The cange is in CVS.
Hello Stefan,
Tested the 2.6.0-beta4, and it sort of works. config parameter:
Email attributes = Tittel,Status
gives the mail:
Logbook : work
Tittel : Test
Status : Åpen
Logbook URL : http://xxxxxxxxxxxxxxxx/work/904
---
Is there a way to remove Logbook field (and perhaps Logbook URL if I want?)
Best regards
Michael |
|
1397
|
Wed Aug 10 18:32:14 2005 |
 | Oleg Solovyanov | Oleg.Solovyanov@ihep.ru | Bug report | Linux | 2.6.0-b4 | Comment tooltip shows comment from other logbook |
I have several logbooks with Comment lines,
but the tooltip shows sometimes the correct comment,
sometimes the comment from other logbook...
I see the same behaviour also on this very page...
I use Mozilla 1.7.10.
Tried with Konqueror -> same problem. |
|
1396
|
Wed Aug 10 11:28:30 2005 |
 | ralphb | elog@spampot.com | | | | Changes in Comment and Elog Index page? |
Just updated to ELOG V2.6.0-beta4 from V2.5.6-2 and I note a couple of changes:
- HTML code inculed in elog.cfg "Comment" lines were previously rendered, now they are not. e.g. "Comment = Some comment
<A href="http://somedomain.com/some.html" target="_top"> Some link text</A>" Is this change deliberate, or is the functionality likely to return? Any workaround?
- The "Several logbooks are defined on this host" elog index page was previously collapsable, now it is not. Same questions as previous.
Thanks & best regards,
Ralph. |
|
1395
|
Wed Aug 10 10:50:55 2005 |
| Bertram Metz | bmetz@sbs.com | Question | Linux | 2.6.0-beta | Long lines in printout |
Hi,
long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer. Does anybody know a solution for this?
Thanks,
Bertram |
|
1394
|
Wed Aug 10 03:18:05 2005 |
| Dinesh Bapat | dinesh.bapat@gmail.com | Question | Windows | 2.6beta3 | Email notification does not work |
I have SMTP server that requires authentication
Whenever a new user 'self registers' to E-log, I get an automated email saying so. Hence, the SMTP setting are correct and working.
However, for any entry made to log, no email notification is generated. error '5.5.4 Invalid Address'
suppress notification checkbox is 'unchecked'
Kindly help. |
|
1393
|
Sun Aug 7 17:16:42 2005 |
 | cunnilinux | cunnilinux@bigmir.net | Info | Linux | 2.5.7 | charset specified in elog.conf has no effect [updated] |
well, here's the problem that i had: my charset (koi8-u) was specified in elog.conf for every logbook, but this had no effect, and all elog pages continued tu appeared as iso-8859-1 (which is the default)
when i specified charset in the global section, the problem's gone away.
2do: i think it's worth testing how does it work whet charset specified for a separate logbook overrides globally specidied charset
elog version that is in use: 2.5.7 from debian sarge 3.1 r0a powerpc |