Hello folks,

Can we have a better support under modern Linux distributions?

I'm trying to install elog in our webserver and it's becoming a boring task. First of all theres only RPM packages. And we really don't like the Red Hat method, so we use Debian Servers. More package mainteners would be nice.

The software appears to be working correctly, but there are some bugs (or perhaps missing dependencies?); the init script put in /etc/rc.d/init.d is broken under Debian:

First of all because it's in /etc/rc.d.

The second problem is in this line:

# Source function library.

#. /etc/rc.d/init.d/functions

The file doesn't even exists.

The third problem is the echo_success; echo_failure commands that doesn't even exist. As I can see it's definitions are sourced in the functions file that doesn't exist.

After removing this missing commands or files from the init.d; I can call elogd script and start the daemon under root. Appears to be working...

And last but not least; there's a way to standardize the init script to run in other Linux distros, so we can put it to start automatically at boot time?

Many thanks in advance,

Vinícius Ferrão 

PS: I'm not asking to support any creepy distros, but to support the .deb package format and system style.

Hello,

when using the summary view, the text field displays umlauts as HTML-charachters, for e. g. diesbezüglich. 
Is there a chance that also this view displays umlauts as ä, ü, ö?

Thank you!

Uwe

It is possible to show the (new) text of a replied entry in the summary text field ?

Actually only for the original entries the text was shown in the text column of the summary report, not for the replies.

Hi,

I've set up my ELOG configuration to display one summary line in the list view. However, a word from the next line creeps in from time to time. You can see this in my logbook - look at the 'Text' column for entries 805, 802 and 800 for instance. The word 'Shift' is from the second line of the entry, but it has been added to the summary text for some reason. Any ideas how I can fix this?

ben

The elog daemon uses cascading style sheets (CSS) to format its output, such
as font family, size and color. Some people started to develop new themes
(skins) and posted them at the contributions logbook (such as
http://midas.psi.ch/elogs/Contributions/7).

From my onw experience, I know that this can be a difficult job, since it
means to change the "default.css" file and reloading a page over and over
again. I recently discovered a way to do this much easier: The Mozilla based
browsers (such as firefox, http://www.mozilla.org/products/firefox/) have an
extension called EditCSS (http://texturizer.net/firefox/extensions/#editcss)
which shows the CSS file on the left side of the browser and the web page on
the right side. Changes in the CSS editor are immediately reflected in the
browser window. This way one can change certain entries in the CSS file and
immediately see its consequences. Development of new skins should therefore
become much more easier.