> > 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.
> 
> That feature is one of the main reasons why the version jumped from 2.x to 3.x. 
> A free tip: changes in major revisions do indicate some kind of incompatibility.
> 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 have to admit here, that I haven't read any GIT tutorial yet.
> By the way: you are welcome to contribute to the release documentation!
> 
> On your actual problem: to go back to a former version of ELOG you can simply
> - stop elogd 3.X, 
> - move all entries from the sub-directories one level up, and 
> - start the 2.X version of elogd.
> 
> I wouldn't really call this an "incompatibility", would you? 
> At least you can easily go back without much trouble.
> 
> Cheers
> Andreas
Stefan told me that the change was because some users were having thousands of yymmdda.log files
in the logbook directories, and that sorting them into subdirectories by year at least did something to bring some 
order.  Possibly to get around the lazy archivers, I suspect.

When I first tried v3.0, I wanted to go back due to some bug or feature, and had to do exactly what Andreas suggested above.

David.

> Stefan told me that the change was because some users were having thousands of yymmdda.log files
> in the logbook directories

I am one of those users. The elog for the ALPHA experiment at CERN goes back to 2006 or so,
with large volume of messages and huge number of attachments. The MIDAS forum elog goes back to 2003.
The TRIUMF DAQ internal elog goes back to 2001.

I think the new organization is an improvement.

K.O.

> > Stefan told me that the change was because some users were having thousands of yymmdda.log files
> > in the logbook directories
> 
> I am one of those users. The elog for the ALPHA experiment at CERN goes back to 2006 or so,
> with large volume of messages and huge number of attachments. The MIDAS forum elog goes back to 2003.
> The TRIUMF DAQ internal elog goes back to 2001.
> 
> I think the new organization is an improvement.
> 
> K.O.
Hi Konstantin,

I've used elog as my main reference/logbook since 2005.  I had looked at it in its version 1 incarnation, but
didn't get on with that so well.  

My biggest problem in the past was running elog on two physically separated linux boxes, and for complex reasons
all the logbooks were on a memory stick (plus the vital backup)!  Hence my previously mentioned memory issues - in
my case the size of the available memory sticks.
David.

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

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

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

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