Hold on I'm having a senior moment

struct FILETYPE {
   char ext[32];
   char type[80];
} filetype[] = {
        {".AI",   "application/postscript"},
        {".ASC",  "text/plain"},
        {".BZ2",  "application/x-bzip2"},
        {".CFG",  "text/plain"},
        {".CHRT", "application/x-kchart"},
        {".CONF", "text/plain"},
        {".CSH",  "application/x-csh"},
        {".CSS",  "text/css"},
        {".DOC",  "application/msword"},
        {".DVI",  "application/x-dvi"},
        {".EPS",  "application/postscript"},
        {".GIF",  "image/gif"},
        {".GZ",   "application/x-gzip"},
        {".HTM",  "text/html"},
        {".HTML", "text/html"},
        {".ICO",  "image/x-icon"},
        {".JPEG", "image/jpeg"},
        {".JPG",  "image/jpeg"},
        {".JS",   "application/x-javascript"},
        {".KPR",  "application/x-kpresenter"},
        {".KSP",  "application/x-kspread"},
        {".KWD",  "application/x-kword"},
        {".MP3",  "audio/mpeg"},
        {".OGG",  "application/x-ogg"},
        {".PDF",  "application/pdf"},
        {".PNG",  "image/png"},
        {".PS",   "application/postscript"},
        {".RAM",  "audio/x-pn-realaudio"},
        {".RM",   "audio/x-pn-realaudio"},
        {".RM",   "audio/x-pn-realaudio"},
        {".RM",   "audio/x-pn-realaudio"},
        {".RPM",  "application/x-rpm"},
        {".RTF",  "application/rtf"},
        {".SH",   "application/x-sh"},
        {".SVG",  "image/svg+xml"},
        {".TAR",  "application/x-tar"},
        {".TCL",  "application/x-tcl"},
        {".TEX",  "application/x-tex"},
        {".TGZ",  "application/x-gzip"},
        {".TIF",  "image/tiff"},
        {".TIFF", "image/tiff"},
        {".TXT",  "text/plain"},
        {".WAV",  "audio/x-wav"},
        {".XLS",  "application/x-msexcel"},
        {".XML",  "text/xml"},
        {".XSL",  "text/xml"},
        {".ZIP",  "application/x-zip-compressed"},
        /* Open XML file types */
        {".DOCM", "application/vnd.ms-word.document.macroEnabled.12"},
        {".DOCX", "application/vnd.openxmlformats-officedocument.wordprocessingml.document"},
        {".DOTM", "application/vnd.ms-word.template.macroEnabled.12"},
        {".DOTX", "application/vnd.openxmlformats-officedocument.wordprocessingml.template"},
        {".PPSM", "application/vnd.ms-powerpoint.slideshow.macroEnabled.12"},
        {".PPSX", "application/vnd.openxmlformats-officedocument.presentationml.slideshow"},
        {".PPTM", "application/vnd.ms-powerpoint.presentation.macroEnabled.12"},
        {".PPTX", "application/vnd.openxmlformats-officedocument.presentationml.presentation"},
        {".XLSB", "application/vnd.ms-excel.sheet.binary.macroEnabled.12"},
        {".XLSM", "application/vnd.ms-excel.sheet.macroEnabled.12"},
        {".XLSX", "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet"},
        {".XPS",  "application/vnd.ms-xpsdocument"},
        {"",      ""},
};

Our elog instance (elogd 3.1.4 built Jan 13 2021, 20:44:20 revision ce2a48e9) has been running for years without any problems.

We have a new user who consistently crashes the elog:

GET /Omicron-STM-XPS/?rsort=Record%20date HTTP/1.1
Host: elog.fhi-berlin.mpg.de:4821
Cache-Control: max-age=0
DNT: 1
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
sec-gpc: 1
Sec-Fetch-Site: same-origin
Sec-Fetch-Mode: navigate
Sec-Fetch-User: ?1
Sec-Fetch-Dest: document
sec-ch-ua: "Google Chrome";v="117", "Not;A=Brand";v="8", "Chromium";v="117"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Linux"
Referer: https://elog.fhi-berlin.mpg.de/elog/isc/Omicron-STM-XPS/
Accept-Encoding: gzip, deflate, br
Accept-Language: el-GR,el;q=0.9,en;q=0.8
Cookie: ufnm=Sotirios Tsatsos; urem=1; elmode=full; elattach=1; sid=CD2B04E2C3F02EA4; googtrans=/en/en; amp_6e403e=aWS6RQd5UjGctj5Ym_cDzA.c2Fsdm9fc290b2thaXRlbkB5YWhvby5jb20=..1hajnscc0.1hajnscc0.0.ac.ac
X-Forwarded-For: 141.14.151.26
X-Forwarded-Host: elog.fhi-berlin.mpg.de
X-Forwarded-Server: elog.fhi-berlin.mpg.de
Connection: Keep-Alive

Received unknown cookie "googtrans"
Received unknown cookie "amp_6e403e"
*** buffer overflow detected ***: terminated
Abort (core dumped)

Hello,

I've noticed that many times, I start an elog and continue editing adding to a few hours later, then I submit and it deletes everything I entered after the last time a draft was saved. I paid more attention and saw that it saves a draft after about a few minutes, and if I wait too long before submitting, it doesn't let me re-save the draft. My workaround is to copy all text before I submit, so if it ignores whatever I entered after the last saved version, I can edit it and paste it back in. Is there a setting someplace that I can change to fix this problem?

Thanks!

Hello,

I started using the record date feature in one logbook, since we plan to copy over old entries Joplin/Onenote. When starting a new entry, I see that the record date is automatically set to the current date, but when I reply to an elog, the record date is automatically set to the record date of the elog I'm replying to. Is there a way to fix this?

Jul 17 20:36:21 elog kernel: elogd[179095]: segfault at 7ffda4d82000 ip 00007f97033a1406 sp 00007ffda4d58c38 error 6 in libc-2.28.so[7f9703374000+1cd000]

Elog version ELOG V3.1.5-30ada1df 

Running on a Rehdat 8 enterprise server

compiled with a Makefile change :: change -Wno-unused-result to -Wno-unused-value

Wondering if anyone has been seeing this?

Follows a very simple logbook definition:

(Assume that all attributes are used farther down.  This is for illustration only.)   

To see what I see when I run this tiny elogd.cfg, see attachment.

"Show attributes" does not seem to be working because all of the attributes are shown, not just those specified in the directive.  Or do I misunderstand/forget something?

Well, it DOES work.... but only if you use the "Show Attributes Edit" directive.  "Show Attributes" is only for the single entry pages, whereas "Show Attributes Edit" is for the "entry pages."

I should have read the docs more carefully, sorry.  But isn't this a bit inconsistent with the way other directives work?  Usually one uses "<Directive>" for new entries, "<Directive Edit>" for editing existing entries, and "<Directive Reply>" for replies.  So I am guessing that "Show Attributes Edit" will be used for new and edit?

> > We are interested in using your ELOG (which we consider to be a wonderful 
> > application) even more. We would like to make a few adaptations in your 
> > source code, above all to add some functionality that we are missing.
> > 
> > I was wondering if there is a way we could coordinate the development 
> > together. For instance, would it be of your interest to receive the code 
> > adaptations we do and implement it in your future releases? 
> 
> Sure, I'm very interested in those and ready to merge it into the main 
> development tree.
> 
> - Stefan

Thanx for your quick answer.
I'll keep you updated as we move ahead with the development.
Tomas