The size is defined by the variable MAX_CONTENT_LENGTH in elogd.c which is set to 10 MB. But email attachments are encoded in ASCII form, so they take useually 3-4 times the space of the binary format. If you have problems with large emails, you can use the option "Email Format = 111" which causes only the names of attachments to be included in email notifications. Users can then still click on the elog link inside the email notification and download the attachment from the elog page.

> > this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
> > methinks I should only be offered to edit draft messages that I own or I can edit. K.O.
> I find it odd that I can see someone elses draft, but never one that I am in the middle of composing (using a
> different tab of the browser) in the elog listing.  There's one such draft Konstantin refers to in the logbook
> listings now - last one was dark blue, this one a pink background, is there a reason for these different colours?

I just tried that on the "Demo" logbook and could see my own draft entry (which appears pink) in a second tab.

Dark blue means you have not updated the default.css file properly from the current distribution.

Stefan

> elogd is spewing these messages about unknown cookies:
> 
> Received unknown cookie "is_returning"
> Received unknown cookie "__utma"
> Received unknown cookie "__utmz"
> Received unknown cookie "SSESSee3cc9c70bedf9a840203765bf409d7b"
> Received unknown cookie "SESSee3cc9c70bedf9a840203765bf409d7b"
> Received unknown cookie "MidasWikiUserID"
> Received unknown cookie "MidasWikiUserName"
> Received unknown cookie "MidasWiki_session"
> 
> K.O.

Delete your cookies ;-)

Elog just logs all unknown cookies for trouble shooting. This should go under verbose output. I changed that just now.

Stefan

> Hi Stefan,
> could we change the format of the "ELOG Version" field in this logbook, that one can enter the full git revision
> number?
> That would be 13 characters.
> 
> Cheers
> Andreas

Ok, done.

/Stefan

No.

I acknowledge these two bugs and will fix them soon.

There are browser extensions for that like "Autofill Forms" for Firefox. You can even link text templates to a single key.

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