The ELOG repository has been moved from Subversion to GIT. While the old repository will be visible for some time, all new development is done on the GIT repository. To download the repository, do a

git clone https://bitbucket.org/ritt/elog.git
git clone https://bitbucket.org/tmidas/mxml.git


or access it online at https://bitbucket.org/ritt/elog/

/Stefan 

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 

 For the login to your email sever, the password is encoded in base64 form (actually not really secure). Somehow your server does not support this. Unfortunately I cannot test this without access to your server. But you can try yourself by doing a telnet to your mail server like:

$ telnet <server.domanin> 25

...

$ AUTH PLAIN

With the "plain" method, you should be able to enter your password in plain text (not base64 encoded), and see if that works. If you are successful, I can add this option to elog.

Best,

Stefan

This is an announcement for the ELOG version 3.1.0 being released just now. Among several bug fixes and an improved Drag & Drop interface for attachments, it contains a long awaited "autosave" feature.

Let's assume that you write an ELOG entry, and keep the window open for a longer time (like to write some shift notes over several hours). If your browser crashes or closes for some reason, you will loose your entered text. To avoid that, ELOG starting from version 3.1.0 has an autosave feature. Whenever you enter some text, it is saved in the background as a draft message to the server. If your browser is closed by accident, you always can go back to the logbook, click "New" and ELOG will tell you that there is a draft message and asks you if you want to edit it. When you edit and regularly submit this message, it becomes a "normal" entry and the draft flas is removed. In addition to the background saving, there is now also a "Save" button so you can manually save your text to the draft entry.

I have tested this to some extent, but I might not have seen all browser/OS combinations, so in case there is a problem, please report it here.

Happy Easter,
Stefan

The changelog is here: http://midas.psi.ch/elog/download/ChangeLog

It is save to install the new version over the old one.

Hi,

I just implemented a different way CSS files are handled in ELOG. Previously, we had the default.css, which could be adjusted for specific needs. Some people did that (like myself). So I changed a few colors etc. When I now implement a new feature in elog, it might need a new CSS class which I put in default.css. But this means that people who have modified this file get it either overwritten, or do not get the new styles.

In order to fix this, the default.css is now called elog.css and is always inluded in any ELOG page. If one specifies a CSS file with "CSS = <file.css>", then this CSS file is loaded in addition to elog.css. So one can put only the modifications into that file and inherits all the rest from elog.css. If new features come in elog.css, the installation with the personalized CSS file will then get the new features from the new elog.css automatically, and just overwrite a few settings in the personalized file. Here is an example:

elog.css:

td {
  color:black;
  font-size:12px;

}

Personalized file special.css, activated with "CSS = special.css" in the elogd.cfg file:

td {
  font-size:18px;
}

This personalized file now overwrites the font size from elog.css to 18 pixel, while maintaining all the rest from elogd.css.

The modification is committed to GIT and will be contained in the next release of elog.

/Stefan

Ok, fixed again.

Cookies are sent from your browser. ELOG has no influence on what the browser sends where. Probably you run your calender at the same machine where ELOG is running, so all the cookies your calender app stores in your browser are sent to ELOG as well. ELOG just complains about something it does not know, but otherwise this message can be simply ignored. Of course you can delete your cookies in your browser, but after the next call to your calendar app they will show up again.