You look here: http://midas.psi.ch/elog/config.html#themes 

 Thanks! but I'm lost in the themes/default/default.css file.... which is the entry I have to edit for the style of the body text (Format "Normal") of the elog pages?

Sara

Just change the body { } entry in the CSS file. Here is a good tutorial: http://www.w3schools.com/css/css_syntax.asp 

 Sorry, my mistake. The cutoff date is anything before September 9th 2001 does not sort.

Andreas Luedeke wrote:

Chris Jennings wrote: Chris Jennings wrote: I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old? Thanks in advance, Chris  Sorry, my mistake. The cutoff date is anything before September 9th 2001 does not sort. I think I remember that this has been discussed earlier: it is a little bug in elogd. You can see where it comes from if you type in the little command 'date -d "9-Sep-2001 3:46:40" +%s' Converted to "seconds of the epoche" (seconds since 1970-01-01 00:00:00 UTC) the date "9-Sep-2001 3:46:40" has one digit more than "9-Sep-2001 3:46:39". Since elog makes a string comparison, suddenly 1'000'000'000 is less than 999'999'999; therefore the wrong sorting. Workaround: you can modify your old entries and add a leading zero to all entries where your specific date field starts with a '9'. Stefan: you should fix it at least well before 20-Nov-2286 18:46:40, when the same bug strikes again!

Ok, well before 2286 approaches I fixed that bug and committed it to the GIT repository (master branch).

/Stefan 

ELOG contains Kerberos authentication at a basic level. If I'm not mistaken, the Windows Domain controller is based on Kerberos. I do not have any 2008 or 2012 domain controller, so I cannot test, but it's worth giving it a try.

/Stefan 

There is nothing within elog itself to insert entry 310 between 300 and 301.  If you allow branching in your logbook. make a second reply to entry 300, and add in the missing details.  That entry will always be there as a reply to 300, but not obviously between 300 and 301.

From this point, any way to improve matters will require editing of the log files (default location /usr/local/elog/logbooks).  I should warn that editing these files can cause problems, including elog to crash, and spotting your error can take a lot of effort.  I speak from experience. I suggest that you have a look at a few entries, the layout of the entries etc first, and if you're still up for it I'll give a quick spin on how to improve the tidyness of how your entires look with 310 inserted between 300 and 301.

I should add what I would write only applies for certain for linux users, as it is my OS of choice.

You are using the entry ID to sort your entries: there is no good way to insert a new entry ID, like 300.5

But you could sort your entries by other means, that allows you to insert entries later between existing entries.

I use for example a "when" attribute of type datetime. Here's an excerpt from the relevant part of my config file: