I have downloaded a latest version.  It has displayed the new version as ELOG V2.9.2-bac715d where seems defined in GIT_REVISION as I guess.  Then I set Bottom Text Login to a html file, it still shows those unwanted characters.

 I have a possible explanation for this problem, but it is just guess work. If I'm right, then just download the latest ELOG version and it will work properly again.

• You've downloaded an elog version from git, which still contained the line 12 in elogd.c: char svn_revision[] = "$Id$";
• Since you did checkout from git, the $Id$ was not substituted.  
• ELOG trys to extract the version by this:      rsprintf
            ("<center><a class=\"bottomlink\" title=\"%s\" href=\"https://midas.psi.ch/elog/\">ELOG V%s-%d</a></center>",
             loc("Goto ELOG home page"), VERSION, atoi(svn_revision + 13));
• svn_revision + 13 is pointing into the void. Still I would have expected that you get a number as a result.

My advice: download again and retry.
 

> [13 Nov]
> As my threads have lots of replies, I end up with a forest of ">" characters which makes it difficult to read
> earlier quoted entries (what with word-wrapping of the browser).
> I thought to replace the ">"s by a simple date entry prepended to the start of each reply. - much as I have 
> given at the top of this initial entry.
> 
> So this is what I put in the config file:
> 
> ....
> Time format = %a %d %b %y
> Date format = %d %b
> Prepend on reply = [$date] \n
> ...
> 
> The time is used in the string for the Thread display.
> 
> Only I don't get the date, with the date format, prepended to replies but the time, in the time format, as
> 
> [Wed 13 Nov 13]
> 
> Now this is hardly a disaster, but any ideas why the date formatting is being ignored?

Hi David,
yes, a $date is substituted with the "Time format" in the function build_subst_list().
I guess that is a bug, but it could break many existing logbooks to change it.
I leave this to Stefan.

There is a simple solution for your problem: you can execute a shell command.

Prepend on reply = $shell(date '+[%d %b]') \n
Reply string =

That snipped will do exactly what you want :-) (of course you need to have the "-x" option to start elogd.)

Kind Regards
Andreas

Please read the documentation in https://midas.psi.ch/elog/config.html und the option "Use Lock". If you don't need locking, just turn it off.

 I'm having same issue. Kerberos is working on Apache on same ubuntu 12.04 server. I used the USE_KRB5 option for compiling elog.

Does anyone  have an idea to solve that problem? 

 I don't know what happened here - I mean, I understand the ">" characters being added to the start of every line of a quoted previous entry, but now what then happened to the formatting.

By default in plain mode elog adds ">" to the start of every quoted line, just as quoting an email will do (some mailer programs).

If you're beyond your nteenth reply, word-wrapping of the browser etc makes past comments difficult to read.  Of course it would be equally difficult in in html mode as the boxes would get more and more nested.

Not sure if your link here about html is relivent to the use of the ">" to indicate a quoted reply or not, although that wasn't really my question - which was about date format in the config file.