Hi Stefan,

There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time".  I archive many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results.  And it gets annoying that the default default is "Day", the number of times I've forgotten...

I got around this by allowing a "Show last default = 0", modifying the relevent line in the block of code you modified when this was introduced to make this select "i==0", and that did the trick. 

Law of unintended consequences came into play.  If you use 0, then on the results page it says "Restricted search to last 0 Days".  So that also needs tweeking, and that's really put my c coding (or lack of it) to the test.  But I've changed that phrase to "Unrestricted search" followed by blank for when the parameter "last" is 0.

Oh, and a typo, "seach" instead of "search".

No doubt other features will show up...

Hi Andreas,

Yes, the empty string does exactly that, in the drop down menu, but before my changes, I could not set it to be the default setting in the configuration file.  In an archived logbook, it's perfectly possible for "all time" to be the only sensible value.  I tried "Show last default =  " and various other variants, with no success in getting what I actually required.  Also, in the documentation, there was no mention of a way to set the default as "all time", just a list of number of days (week (7), month (31), year (364) etc), which also led me to believe that it was not possible with the existing code.

I've sent an email to Stefan giving my coding changes for information.

Having installed v3.1.0 on a test logbook, I find that I can browse and select a file, but when I click on the "Upload" button, I get a pop-up message from the browser asking me:

"This page is asking you to confirm that you want to leave - data you have entered may not be saved."

The stay on page does nothing, the leave page option does what one expects from elog - that is the attachment thumbnail is generated etc. 

I guess this is something to do with the drag and drop feature, but wondered if others have this issue or whether it may just be some mystery setting of the browser (firefox).

Thanks Stefan, that did the trick.

Had a bit of an effort with the git repository, though, kept getting 403 errors when tried the

git clone https://bitbucket.org/ritt/elog as per the "download" page.

error: The requested URL returned error: 403 while accessing https://bitbucket.org/ritt/elog/info/refs

Hi Francois and Andreas,

On Francois' first question, I wonder if Francois is using attrib1, attrib2... as the actual attribute names in the config file.  If this is the case, Francois, you can name attributes with suitable names in the configuration file and dictate which ones appear in the List and Threaded display modes. In the List Display, those names appear along the top row at the top of each column, which I think is what you want. 

This example of three lines in a config file (made up).

Attributes = Worker, System, Organisation, Customer, Status, Ticket

List display = ID, Date, Organisation, Customer, Worker, System, Status, Ticket

Thread display = $Ticket: $Worker. $Organisation / $Customer, ($message id).

In list display, those words ("Organisation", "Customer" etc) are those that appear at the top of each column.  In Thread Display, note how you can use punctuation.  Also (not shown here) you can colour the line in Thread Display depending on the attribute System (which is akin to your question on cell style colouring) a feature not much used in this forum, and the Icon at the beginning of the line depending on the attribute Status. 

This is in the documentation, but perhaps it's not clear to all that - apart from the system defined attributes - any word can be used as an attribute name, and that "attrib1" "attrib2" is just shorthand for "any words you wish to use as attribute names".

Otherwise, if you want a different word along the top if the column in the List Display (and also in the form for making a new entry) for the attribute that appears in that column, why not just use that different word as the name for the attribute?

On the third point, about Cell Style, it would be good for having attrubute 2 able to dictate the colour of the cell of attribute 1, and no need to show attribute 2 in the List Display.  But take your point that it can be done in a shell script.

I only saw Andreas' edited version of the original enquiry, so I didn't see the orignal config file under discussion - so most of my previous entry is totally pointless.  Sorry about that.

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