For one user in our ELog installation the "Show only new entries" button seems to be stuck on one particular date and time " ...

this occurs with different browsers and PC's

For other users it works as described in this forum post ...

"When you are active browsing entries, your activity is recorded (only the time) in the password file. Now when you are inactive for more than one hour, you are considered "logged out", and your last activity is taken as a filter for new entries. That means you see new entries since your last activity in the logbook. " https://midas.psi.ch/elogs/Forum/1612

Regards

Mark.

When compiling elog on OSX 10.9 (Mavericks), I get the error below.

Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.

$ make

cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall  -I../mxml  -DHAVE_SSL -w -c -o crypt.o src/crypt.c

cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall  -I../mxml  -DHAVE_SSL -o elog src/elog.c crypt.o -lssl

src/elog.c:125:8: error: expected parameter declarator

size_t strlcpy(char *dst, const char *src, size_t size)

       ^

/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'

  __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))

                                           ^

/usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'

#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)

                                                             ^

/usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'

#    define _USE_FORTIFY_LEVEL 2

                               ^

src/elog.c:125:8: error: expected ')'

/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'

  __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))

                                           ^

/usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'

#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)

                                                             ^

/usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'

#    define _USE_FORTIFY_LEVEL 2

                               ^

src/elog.c:125:8: note: to match this '('

/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'

  __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))

                                           ^

/usr/include/secure/_common.h:39:53: note: expanded from macro '__darwin_obsz'

#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)

                                                    ^

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

We recently installed ELOG and it works pretty well, but the load times are rather inconsistent. Most of the time 
it is very fast, but it also often hangs for around 5-10 seconds while loading. It seems to affect all parts of 
the page that are returned at random, so sometimes the main html file will hang, sometimes the css file and 
sometimes the images.

The hardware it is running on is nothing special, an older 3 GHz Celeron, but it should be fast enough. It is 
running on Debian 7. 

Any ideas what the problem could be, or how I could investigate it further to find the bottleneck?

My elog is named "Whatever Elog" so the URL generated is /Whatever+Elog . This works fine but when in the interface certain buttons generate this URL : /Whatever%20Elog  ...this URL fails.  It seems that elog does not recognize these ( + and %20 ) as the same which I believe they should be as part of HTTP request.