So subscribe to ELOG RSS feeds, do the following:

- In Thunderbird, click "Tools/Account setting", then click "Add account",
"RSS News & Blogs", "Next", "Finish", "Ok".

- Select "News & Blogs" in the "Folders" pane, right-click and select
"Properties"

- Click on "Manage Subscriptions..."

- Click on "Add"

- Enter the Feed URL of elog. Use your logbook URL and add "elog.rdf". For
this forum for example, enter

http://midas.psi.ch/elogs/Forum/elog.rdf

- Click OK. That's all.

See how the RSS feed shows up in the attached image. Please note that you
need public read access to your logbook for this to work (via "Guest menu
commands"), since the RSS mechanism does not support authentication.

> I was upgrading to the latest version and I wrote over my cfg file. I 
> still have my database files. Is there a way to put the cfg file back 
> together using the database files as a guide.  It did not seem to want to 
> upgrade until I did this and I forgot to copy and then paste the cfg files 
> back.  The latest version is now running. Before I did this I was still 
> getting the old version number at the bottom of the main screen.  Also I 
> have an RSS reader that can do user name and password, is this possible 
> with Elog if the RSS reader has the ability?

I put an extra dialog box into the installer to prevent overwriting the
original config file, but unfortunately I cannot prevent people from shooting
themselves into the foot (;-)

The database files contain at least the attributes. Just open any file with a
text editor. But the other settings, like "preset <attribute>" etc. are lost.

Concerning teh RSS authentication, I willing to implement this if you tell me
which reader you are using, so that I can test it. You could also try yourself,
maybe it works without modification. What you would need is public read access
via "Guest menu commands" option plus a "Read password". The read password
prevents again the public read access, but the RSS reader can maybe submit it.
What the RSS reader certainly cannot do is to fill out the "Login" screen of
elog, so you need the "Guest menu commands" for sure.

- Stefan

> I have a question about sending emails. I have a customer service ELog 
> currently running but I would like to have an option to be able to pick 
> from a list of people, one or more than one to send emails to with the 
> logbook entry as the body.  I am currently using the email option to send 
> emails to a list if an emergency is used in a category but I would like to 
> be able to send the entry to different people at different times.  I would 
> have everyone pre-entered with their names and emails and you could check 
> a box by the person or people you want the log entry sent.  I wasn't sure 
> if this is possible with the current system. 

It is. Put an MOptions in you config file, and then put individual email
statements there. Like

Attributes = ..., Notify
MOptions Notify = Joe, Jack, Jim
Email Notify Joe = joe@fujicolor.com
Email Notify Jack = jack@fujicolor.com
Email Notify Jim = jim@fujicolor.com

What this does it give you a checkbox for each name. If the check box is
checked, then the corresponding email statement is executed. Note that the
email address does not have to correspond to the "Notify" value. You could also
use completely different names, like "MOptions Notify = Security, Police,
Admin", and then put some email address from specific people there.

> Hello,
> I have been running Elog for a long time on a variety of RedHat releases,
> (this is a terrific project by the way). Currently running Elog v2.5.7 on 
> RedHat (Fedora Core-II) and most is working great excepting being able to 
> modify the default fonts being used by Elog when trying to write and save 
> in text mode while in Elog's main editing screen. 
> 
> On my setup the font size is way too small and to work around this problem 
> I write and save everything in HTML mode. I've browsed the Elog css file 
> but don't yet see where or how to properly set the default font style or 
> size for the main screen in the editor. Can you shed some light on this for 
> me?

The text style of the main message text is defined in the following lines in the
CSS field:

.messagepre {
  font-family:'lucida console',courier,monospace;
  font-size:10pt;
}

Locate these lines and change 10pt to 12pt or even 14pt.

> Thank you so much for working with me on this.  The RSS reader I have been trying 
> is at http://www.rssreader.com   and is version 1.0.88.0  It is a free RSS reader 
> and seems to work very well.  It has a username and password system, but I am not 
> sure what and how it will support with ELog. I have been successful in reading an 
> open logbook with no passwords.  

rssreader supports HTTP authentication. So what you have to do is to define a "read
password". Open a dos box, navigate to your elog directory, and enter

elogd -l <logbook> -r <password>

replace <logbook> with your real logbook name and <password> with any password. This
command modifies elogd.cfg and puts your password there in encrypted form.

Next, tell rssreader to use authentication and enter there your password
(authetication name does not matter). See the attachment. Rssreader will then be able
to connect properly to your logbook.

I applied a similar fix like you proposed, just omit highlighting at all if I get a
zero length match. Changes committed to CVS.

> I downloaded the latest file and installed but the version number stayed at 
> 2.5.8-2 and did not change to -3.

Sorry I forgot to increase the version number in the source code. So don't worry.

> Also is there a way to change the display of the default date. It uses 
> allot of space in the date column.

Date format = %A, %B %d

see manual!

> I have been running ELOG on FreeBSD no problem for a year now,
> but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine 
> with a few warnings (see attached logs).
> But has issues with password files, now it shows message "Can't open 
> passwords.pwd" for all my logbooks. It did convert the password files to 
> xml format. I had a good hard look at file permissions and config file with 
> no luck. So I went back a version and compiled 2.5.7-1 which works just 
> fine with old password files. So something with XML & FreeBSD?...

Hard to say. The simplest would be if I could debug this.

> Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
> When I run a ./elogd -C http://elog.blah.here:88 it clones the config file 
> just fine, also seems to copy over all logbook entries.
> But once I look through them there's a fault with one of the fields it 
> copies over, so entries never show up.
> 
> It should be:
> ========================================
> Date: Tue Mar 01 19:41:29 2005
> In reply to: 24
> Work done by: someuser
> Work done at (dd/mm/yy hh:mm):  1/03/05 3:30pm
> Downtime duration: 0 min
> Planned: Yes
> Reason: Normal work
> Attachment:
> Encoding: plain
> 
> But once cloned it looks like this:
> ========================================
> Date: Tue Mar 01 19:41:29 2005
> In reply to: 24
> Work done by: someuser
> Work done at (dd/mm/yy hh: m):  1/03/05 3:30pm
> Downtime duration: 0 min
> Planned: Yes
> Reason: Normal work
> Attachment:
> Encoding: plain
> 
> 
> For some reason it looses the "m" so line 4 instead of having
> "hh:mm" has "hh: m"

Your problem is that the attribute "Work done at (dd/mm/yy hh:mm)" which
contains a ":". This character is not allowed in attributes. Unfortunately I did
not document this (and even didn't know this until now... (;-) ). So you should
use the new option

Type Work done at = datetime

this gives you at the entry mask fields for day/month/year/hour/minute to fill
out, so you don't have to write it directly into the attribute. Another option
would be to use 

Comment Work done at = Please enter as (dd/mm/yy hh:mm)

which just displays a comment below the attribute in the entry mask.

- Stefan