Re: email notification for self register 2 3 and 4, posted by Stefan Ritt on Mon Jun 8 08:11:33 2020
|
Why don't you start elogd interactively with the "-v" flag (verbose) and watch the communication between elog and postfix. Maybe you see
a specific error there.
Stefan |
|
Re: email notification for self register 2 3 and 4, posted by Stefan Ritt on Mon Jun 8 09:12:27 2020
|
STARTTLS is not supported natively by elog. You have to disable this in your SMTP server.
Stefan
pierre |
|
Re: Expanding column width when viewing in Summary mode, posted by Stefan Ritt on Fri Jul 17 09:18:18 2020
|
You can't directly change individual columns, but you can reduce the "Text" column. This is done in themes/default/elog.css. Search for
"listtitle2" and change or remove the line "width:100%". This makes the text column narrower, leaving more space for the subject column.
Illam |
|
Re: Expanding column width when viewing in Summary mode, posted by Stefan Ritt on Mon Jul 20 08:37:17 2020
|
I can think of two reasons why you don't see a change:
1) You modified the wrong file. The elog.css file is under elog/themes/default/elog.css. If you "install" elog, it might go into your
installation directory. So check if you have more than one file with this name. |
|
Re: How to change name of record Id from $@MID@$., posted by Stefan Ritt on Wed Jul 22 19:10:08 2020
|
No idea what you are talking about. $@MID@$ is used in the database files to indicate the start of a new message. It is not used on any elog web page.
If you want to put the message ID on your web page, you should use the variable "$message id" as written in the documentation. You say JS, where
is your JS running? You wrote a JS program to work on the raw elog database files? Or you wrote an extension to run in your browse? You have to be a bit |
|
Re: testing the client: unclear it worked, posted by Stefan Ritt on Fri Jul 31 08:34:35 2020
|
The <hostname> you have to actually replace with your real host name. Same for logbook, username and password.
On my local test system I get (actual password hidden here with "...")
~$ elog -h localhost -p 8080 -l demo -u stefan ... -a Authort=SR -a Subject=test |
|
Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Fri Jul 31 15:42:55 2020
|
Start your new server interactively with "elogd -v 3" to see all verbose output. You will then see how it indexes all logbooks. If not, you
might have a wrong path in elogd.cfg
VUIIS |
|
Re: Missing log files when rsync to replacement server., posted by Stefan Ritt on Sat Aug 1 15:13:17 2020
|
You can put your files where ever you want, just tell elogd where to find the elogd.cfg file via the "-c" flag. Then tell elogd where to find files
in the elogd.cfg file via the "Logbook dir" and "Resource dir" directives.
Stefan |