Cheers, Andreas

I'd like to fix text or table in the subject field that can't be deleted or moved. 

Can that be done in config? Example - 

Time Off:

Reason:

Update By:

Estimated On time:

Detail:

> 
> "News for each version can be seen in the changelog (->http://midas.psi.ch/elog/download/ChangeLog)"
> 
> And for version 3.0.0 it states:
> - Create one logbook subdirectory pear year
> 

The text should read:

the first time you run the new elogd against old elog data,
all existing entries will be moved into by-year subdirectories
and the old elogd will not work anymore.

K.O.

> > 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 ;-)
> 

No, go. The MidasWikiUserName cookie will log me out of the MidasWiki, etc.

But why are MidasWiki cookies sent to the elog? Ah, yes, they all run from the same https://midas.triumf.ca.

This explains why elog complains about unexpected cookies - elogd does not expect to receive
mediawiki cookies - it does not expect to share the https:// connection with somebody else.

This is good to know for the future. (I.e. if mediawiki is confused by elogd cookies).

K.O.

> 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

> > 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

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.

> > elogd 3.1.0 moves all elog entries into year-named subdirectories. this feature makes it incompatible with older elogs and so should be clearly mentioned in the documentation,
> > in the release announcement and in the release and migration notes. K.O.
> 
> But yes, the release documentation by bitbucket is not really that useful: 
> it is difficult for me too, to find out what changed with new releases. 

I did know that I've read it summarized somewhere!
The changes with the different releases are documented here:
http://midas.psi.ch/elog/download/ChangeLog

It is actually not so difficult to find: 
it is linked on the "Download" section http://midas.psi.ch/elog/download.html

"News for each version can be seen in the changelog (->http://midas.psi.ch/elog/download/ChangeLog)"

And for version 3.0.0 it states:
- Create one logbook subdirectory pear year

I admit that version 3.0 has never been announced and the changelog is not mentioned in the announcement of version 3.1.0
Maybe we'll do better in the future ;-)