Your syntax is correct. If you try a big font for example

     Cell Style Status Fixed  = background-color:green;font-size:40px

it will work. The problem here is that the text decoration is defined differently since it's a link. The CSS defines these style via

/* standard link colors and decorations */
a:link { color:#0000FF; text-decoration:none }
a:visited { color:#800080; text-decoration:none }
a:hover { color:#0000FF; text-decoration:underline }
a:active { color:#0000FF; text-decoration:underline }
a:focus { color:#0000FF; text-decoration:underline }

Just for the record: It's actually forbidden. If you do -u "username password" then elog considers "username password" as the full user name, and the password is missing, so it takes the next argument as a password. In one of our trials it then used -a "Category=info" as the password, so the category was then missing. 

Dear ELOG users,

starting with SVN revision 2328, custom input forms are implemented. This allows application specific formats for check lists etc. In our specific case we had to implement a shift check list, which was quite long. Furthermore the check list should be optimized for an iPad, which we take in the field and record various checks and readings (in our case some gas pressure gauges at the PSI particle accelerator). Since the standard ELOG interface was too inflexible, a completely hand-written form was needed. The form can be activated by the new configuration options Custom New Form, Custom Edit Form and Custom Display Form, one for a new entry, an entry to edit and and entry to display. In our case we used the same form for all three cases. This is how the shift check list looks under the Safari Browser on a PC:

And here is how it looks on the iPad:

Each section can be collapsed and expanded (blue arrows at the left), and various internal checks are made before the check list can be submitted.

Implementing such forms is however more something for the advanced user, since you have to hand-write HTML with CSS and JavaScript code. It can then however be a powerful method for check lists. Please find in the attachments the elogd.cfg configuration for that logbook and the shiftcheck.html source code file. It is a bit complicated since the page is a static page, elogd just serves it from the file. This requires all the dynamic functions to be implemented inside the HTML file with JavaScript. To display an entry for example, the JavaScript loads the raw data with the "?cmd=Download" command and the populates the form fields. The collapsing and expanding is done by using CSS properties. The integrated style sheet was optimized for the rendering on an iPad. Rather large fonts were chosen so that the items can be checked easily with your finger tips. Various parameters are sent between the browser and the elogd program via hidden fields and cookies. So only something for experts! But if you go through the effort and hand-write the form, it can be very handy. Note that you have to upgrade to SVN revision 2328 for the three new options.

Hi Stefan,

I'm starting to get a similar problem to Lance's ("SQL Database").  Searching is beginning to take time.

In searching, I either can search one logbook (still relatively quick), or all of them.

I have my logbooks in groups, and often I know which group I want to search, and it would make the searching
much quicker were the search confined to just that group.  I don't think I've missed anything in the
documentation on this matter.  

If not a change to the elog program, is there another way of (say) arranging the logbooks that will achieve this?

> Hi Stefan,
> 
> I'm starting to get a similar problem to Lance's ("SQL Database").  Searching is beginning to take time.
> 
> In searching, I either can search one logbook (still relatively quick), or all of them.
> 
> I have my logbooks in groups, and often I know which group I want to search, and it would make the searching
> much quicker were the search confined to just that group.  I don't think I've missed anything in the
> documentation on this matter.  
> 
> If not a change to the elog program, is there another way of (say) arranging the logbooks that will achieve this?

You can't do that right now. I would have to extend the functionality to allow searching in groups. Also have a look 
at https://midas.psi.ch/elogs/Forum/66901. Maybe that helps a bit in meantime.

Hi Stefan,

I was rather hoping that was *not* going to be your answer.

I much prefer the plain ascii file format, for it allows me to edit it for "mistakes" post submission, 
shall we say. 

> > Hi Stefan,
> > 
> > I'm starting to get a similar problem to Lance's ("SQL Database").  Searching is beginning to take time.
> > 
> > In searching, I either can search one logbook (still relatively quick), or all of them.
> > 
> > I have my logbooks in groups, and often I know which group I want to search, and it would make the searching
> > much quicker were the search confined to just that group.  I don't think I've missed anything in the
> > documentation on this matter.  
> > 
> > If not a change to the elog program, is there another way of (say) arranging the logbooks that will achieve this?
> 
> You can't do that right now. I would have to extend the functionality to allow searching in groups. Also have a look 
> at https://midas.psi.ch/elogs/Forum/66901. Maybe that helps a bit in meantime.

Hi,

I'm trying to configure Elog such that users can self-register. But no luck so far.
I cannot get the login screen. I'm connecting to a logbook (and I can do this without logging in).
Shouldn't I get a screen to login/register?

Here is my elogd.cfg:
[global]
Port=8880
Password file = /usr/local/elog/logbooks/passwd
SMTP host = smtp.mydomain.de
SMTP user = kuku
Logfile = /usr/local/elog/logs/elog.log
Admin user = kuku other
Login user = abc def ghi
SSL=1
URL=https://www.mydomain.de:8880/
Self register = 1
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help
Guest menu commands = List, Find, Login, Help

Admin user = me@mydomain.de
[Demo]
Admin Password = 9lVlUsigs4neBt9xnX44YYQay15Yu9PyLC9hK6sifI9
Attributes = Author, Status
[Linux]
Admin Password = 9lVlUsigs4next9PnXShhQQa515Yu9PyLC9hK6sifI9
Attributes = Author, Status
[Windows]
Admin Password = 9lVlUsigs4neBt9PnXShhQQay15YuxPyLC9hK6sifI9
Attributes = Author, Status

> Hi,
> 
> I'm trying to configure Elog such that users can self-register. But no luck so far.
> I cannot get the login screen. I'm connecting to a logbook (and I can do this without logging in).
> Shouldn't I get a screen to login/register?
> 
> Here is my elogd.cfg:
> [global]
> Port=8880
> Password file = /usr/local/elog/logbooks/passwd
> SMTP host = smtp.mydomain.de
> SMTP user = kuku
> Logfile = /usr/local/elog/logs/elog.log
> Admin user = kuku other
> Login user = abc def ghi
> SSL=1
> URL=https://www.mydomain.de:8880/
> Self register = 1
> Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help
> Guest menu commands = List, Find, Login, Help
> 
> Admin user = me@mydomain.de
> [Demo]
> Admin Password = 9lVlUsigs4neBt9xnX44YYQay15Yu9PyLC9hK6sifI9
> Attributes = Author, Status
> [Linux]
> Admin Password = 9lVlUsigs4next9PnXShhQQa515Yu9PyLC9hK6sifI9
> Attributes = Author, Status
> [Windows]
> Admin Password = 9lVlUsigs4neBt9PnXShhQQay15YuxPyLC9hK6sifI9
> Attributes = Author, Status

You should not mix "Password file" with "Admin Password". Either use one or the other system, but not both. So 
remove "Admin Password", and delete all cookies in your browser, then you should see the login screen.