Re: Adding attachment to an existing entry, posted by Stefan Ritt on Tue Dec 7 09:40:19 2010
|
| Stefan Ritt wrote: |
|
there is however now the problem that one has to click Submit twice to make it work
|
I fixed this problem in the current SVN revision, so now a single click to the Submit button is enough again. |
New entries are not visible from other logbooks based on the same logbook dir through Subdir, posted by JacekK on Fri Jan 14 00:07:01 2011
|
Hi,
I have two logbooks based on the same data directory through "Subdir" option and when I add new
entry in one logbook, then that entry is not visible in other logbook.
I suppose it is a bug in el_submit function, where I think the new message should be added to
message index of every logbook based on the same data directory as the one, where the message was physically
created.
There is a piece of code, which I think should do this automatically
/* if other logbook has same index, update pointers */
but it seems the other logbooks does not have the same index.
I'm new to elog and the sources are also new to me, so my guess to the ground of the problem may be wrong.
Let me know is this bug possible to fix in near future.
Best regards,
Jacek |
|
Re: New entries are not visible from other logbooks based on the same logbook dir through Subdir, posted by Stefan Ritt on Thu Jan 20 08:52:43 2011
|
| JacekK wrote: |
|
Hi,
I have two logbooks based on the same data directory through "Subdir" option and when I add new entry in one logbook, then that entry is not visible in other logbook.
I suppose it is a bug in el_submit function, where I think the new message should be added to message index of every logbook based on the same data directory as the one, where the message was physically created.
There is a piece of code, which I think should do this automatically
/* if other logbook has same index, update pointers */
but it seems the other logbooks does not have the same index.
I'm new to elog and the sources are also new to me, so my guess to the ground of the problem may be wrong.
Let me know is this bug possible to fix in near future.
Best regards,
Jacek
|
Well, having two logbooks in the same subdirectory was initially a planned feature but really never worked. I re-visited this issue and made it working in the current SVN version. So the next release will contain the fix. |
|
Format in "Thread display", posted by Eoin Butler on Sat Jun 18 20:29:25 2011
|
Is is possible to add formatting (such as <b> tags, etc..) to the "thread display" option? |
multiple homes?, posted by Christoph Kukulies on Wed Nov 2 10:49:02 2011
|
Is it possible to have many roots with one elogd (or run several elogds), such that you can seaparate different groups or themes from each other:
electronics
trigger
power
mechanics
detector
support
Thanks.
Christoph
|
|
Re: multiple homes?, posted by Stefan Ritt on Wed Nov 2 10:54:38 2011
|
| Christoph Kukulies wrote: |
|
Is it possible to have many roots with one elogd (or run several elogds), such that you can seaparate different groups or themes from each other:
electronics
trigger
power
mechanics
detector
support
Thanks.
Christoph
|
Have a look at "top groups" in the documentation |
|
Re: multiple homes?, posted by Christoph Kukulies on Mon Nov 7 10:12:04 2011
|
| Stefan Ritt wrote: |
|
| Christoph Kukulies wrote: |
|
Is it possible to have many roots with one elogd (or run several elogds), such that you can seaparate different groups or themes from each other:
electronics
trigger
power
mechanics
detector
support
Thanks.
Christoph
|
Have a look at "top groups" in the documentation
|
Thanks. I got it working so far. One minor glitch:
I have one topgroup (with 2 subgroups),
electronics
trigger
power
and onother topgroup (only 1 subgroup)
mechanics
detector
When I get the login screen for the second (with the only one subgroup) it says in the header:
"Several logbooks are defined on this host. Please select the one to connect to:"
and below only the one group (detector) is shown, so actually nothing to select.
This may be possibly achieved by not defining a subgroup for the second one and leaving it as a topgroup,
but I don't know how it behaves, when the group admin decides to create a subgroup. Can he do
without requiring superuser or elog permissions?
--
Christoph
|
|
Re: automated email notification did not work for me, posted by Oliver Kirsebom on Thu Oct 17 14:23:06 2013
|
| Stefan Ritt wrote: |
|
| Jianglai Liu wrote: |
|
Hi,
I am setting up an elog to organize my lab activities. I installed elog 2.8.0 on the latest CentOS 5.5, 32 bit. I got into trouble setting up the automated email notification.
According to the elog manual, I setup the smtp setting in the elogd.cfg as follows:
SMTP host = smtp.gmail.com
SMTP username = jianglai.liu
I then used "elogd -t" to encode the password into the configuration file.
But when I submit an entry, I always received: "Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. y17sm867489wfd.15"
If I switched to use my university email servers, similar things happened.
SMTP host = smtp.sjtu.edu.cn
SMTP username = jianglai.liu
I got "Error sending Email via "smtp.sjtu.edu.cn": 5.7.8 Error: authentication failed: another step is needed in authentication"
I also switched to use one of my old work server
SMTP host = smtp-server.its.caltech.edu
SMTP username = jliu
and ended up with the same error message.
I did a google search on this without much progress. I would appreciate it very much if someone could shed light on how do I fix this.
Thanks much!
|
elog only supports basic authentication, not TLS or SSL. These days more and more SMTP servers require this however. I will put this on my to-do list. In meantime you can maybe configure your CentOS machine acting as an SMTP server, and then not using TLS or SSL there. That's what most people do.
|
Hi, has this problem been fixed? (i.e does ELOG now support TLS or SSL?) Thanks, Oliver |