Restricting entries view by user, posted by Leonardo Tacconi on Thu Nov 2 11:38:36 2023
|
Good morning,
I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.
Thank you in advance.
Leonardo |
Re: Restricting entries view by user, posted by Stefan Ritt on Thu Nov 2 11:46:42 2023
|
No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.
Stefan
| Leonardo Tacconi wrote: |
|
Good morning,
I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.
Thank you in advance.
Leonardo
|
|
|
Re: Restricting entries view by user, posted by Matteo Mannini on Tue Nov 7 22:07:24 2023
|
Dear Stefan,
thanks to the answer you gave to my colleague.
Now, attempting to follow your suggestion... If we will create several logbooks, one for each user,
1) there is a way to automatically duplicate all the entries in anoter "global" elog without loosing them and keeping them updated between the global and the individual logbooks?
2) alternatively how I could activate a search in all these user logbooks (and only in this set of logbooks without searching in the others logbook present in the same file conf)? shall I gnereate a separated elog instance only for this set of logbooks? how to let this search to all option available only to a reduced number of "superusers" that are not "administrators?
thanks
Matteo
| Stefan Ritt wrote: |
|
No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.
Stefan
| Leonardo Tacconi wrote: |
|
Good morning,
I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.
Thank you in advance.
Leonardo
|
|
|
|
Re: Restricting entries view by user, posted by Stefan Ritt on Thu Nov 30 14:28:12 2023
|
Keeping the global and individual logbooks in sync is not possible. So indded my proposal is a cumbersome solution in your case. We do have "restrict edit" which lets users only edit their own entries, but we do not have "restrict view". Maye some thought for a future version of elog.
Stefan
| Matteo Mannini wrote: |
|
Dear Stefan,
thanks to the answer you gave to my colleague.
Now, attempting to follow your suggestion... If we will create several logbooks, one for each user,
1) there is a way to automatically duplicate all the entries in anoter "global" elog without loosing them and keeping them updated between the global and the individual logbooks?
2) alternatively how I could activate a search in all these user logbooks (and only in this set of logbooks without searching in the others logbook present in the same file conf)? shall I gnereate a separated elog instance only for this set of logbooks? how to let this search to all option available only to a reduced number of "superusers" that are not "administrators?
thanks
Matteo
| Stefan Ritt wrote: |
|
No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.
Stefan
| Leonardo Tacconi wrote: |
|
Good morning,
I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.
Thank you in advance.
Leonardo
|
|
|
|
|
Cannot send Emails, posted by John on Mon Oct 23 20:35:54 2023
|
Hello, my sending of emails was working a while back but I have not checked on it in a few months and found out I am getting authentication errors sending to my MTA (mailer). I was using a base64 to encode the pw but now my mailer (gandi.net) rejects it. Has anything changed over the last couple of years with Elogs code that would be affecting this? I just upgraded (Linux) and changed my testing grounds to non-production and the same problem exists. Thing is I CAN send using other programs, but not with Elog. It is impertive I figure this out or have a work around.. but a 'work around' does not seem like a possible task since all the work (forums and such) will be via my Elog server.
Thanx, John |
|
Re: Cannot send Emails, posted by Stefan Ritt on Tue Oct 24 08:12:38 2023
|
ELOG has not change in the last years in that respect, but I know that mailer get more and more picky about encryption etc. So you probably have to convince your mailer to accept the pw as it comes from ELOG, or do not require a pw for that specific client.
Stefan
| John wrote: |
|
Hello, my sending of emails was working a while back but I have not checked on it in a few months and found out I am getting authentication errors sending to my MTA (mailer). I was using a base64 to encode the pw but now my mailer (gandi.net) rejects it. Has anything changed over the last couple of years with Elogs code that would be affecting this? I just upgraded (Linux) and changed my testing grounds to non-production and the same problem exists. Thing is I CAN send using other programs, but not with Elog. It is impertive I figure this out or have a work around.. but a 'work around' does not seem like a possible task since all the work (forums and such) will be via my Elog server.
Thanx, John
|
|
|
Fail to upload enclosure in ELOG , posted by Laurent Jean-Rigaud on Mon Jan 16 20:18:12 2023
|
Hi,
I currently testing last ELOG version from git in a docker with LDAP activated (https://hub.docker.com/r/usinagaz/elog-ldap). The goal is to use it on Synology NAS server, associated with local LDAP server.
The reverse proxy is done by embedded DSM nginx, according to FDQN associated to ELOG service (elog.corp.com). In Docker, URL is set to elog.corp.com.
All is good, but when I post any enclosure in any elog post, the elogd exits and docker is automatically restarted. The browser shows an error 405 generated by nginx server.
Do you have any idea of the cause of this problem ?
Thanks for help.
Laurent |
|
Re: Fail to upload enclosure in ELOG , posted by Laurent Jean-Rigaud on Wed Oct 11 23:09:36 2023
|
Ok, i reply to myself as i could resolve the problem by changing the alpine Linux image to Debian light.
After debugging, the problem seems to be the compilation option used for alpine packets, which is not fully compatible when running on NAS Intel cpu.
The problem disappeared with Debian light, which should be less "aggressive" for optimization. I think the core is generated during imagemagick lib call (png, jpeg,pdf, ...).
Cheers
| Laurent Jean-Rigaud wrote: |
|
Hi,
I currently testing last ELOG version from git in a docker with LDAP activated (https://hub.docker.com/r/usinagaz/elog-ldap). The goal is to use it on Synology NAS server, associated with local LDAP server.
The reverse proxy is done by embedded DSM nginx, according to FDQN associated to ELOG service (elog.corp.com). In Docker, URL is set to elog.corp.com.
All is good, but when I post any enclosure in any elog post, the elogd exits and docker is automatically restarted. The browser shows an error 405 generated by nginx server.
Do you have any idea of the cause of this problem ?
Thanks for help.
Laurent
|
|
link to attachment within html editor, posted by Celeste Torkzaban on Mon Oct 9 10:43:46 2023 
|
Hello,
I like the ELcode feature that lets you easily make an internal link to an attachment in the same post. However, I wasn't able to get this to work in the html editor, even though it's possible to use the ELcode format to link to another post in the logbook. When I type in elog :/1 in the html editor (without the space) and submit (even with an attachment present), it weirdly gets changed and shows up as 61/1 in the submitted elog, without any hyperlink. As far as I know we're using the standard elog code and only modified css parameters. Is there another syntax to link to attachments in html?
Testing it out here: 69699/1 (elog :/1 without the space turned into 69699/1) |
|
Re: link to attachment within html editor, posted by Stefan Ritt on Mon Oct 9 12:30:44 2023
|
You can always insert the full link to the attachment like this one: https://elog.psi.ch/elogs/Forum/231009_104933/SCR14.PNG
But you can also use elog:69699/1 as shown here. Unfortunately you can do that only after the entry has been submitted, so you know the ID number of that entry. Once you have it, edit the entry and put it in.
Stefan
| Celeste Torkzaban wrote: |
|
Hello,
I like the ELcode feature that lets you easily make an internal link to an attachment in the same post. However, I wasn't able to get this to work in the html editor, even though it's possible to use the ELcode format to link to another post in the logbook. When I type in elog :/1 in the html editor (without the space) and submit (even with an attachment present), it weirdly gets changed and shows up as 61/1 in the submitted elog, without any hyperlink. As far as I know we're using the standard elog code and only modified css parameters. Is there another syntax to link to attachments in html?
Testing it out here: 69699/1 (elog :/1 without the space turned into 69699/1)
|
|
Re: link to attachment within html editor, posted by Celeste Torkzaban on Mon Oct 9 16:43:06 2023
|
thank you!
| Stefan Ritt wrote: |
|
You can always insert the full link to the attachment like this one: https://elog.psi.ch/elogs/Forum/231009_104933/SCR14.PNG
But you can also use elog:69699/1 as shown here. Unfortunately you can do that only after the entry has been submitted, so you know the ID number of that entry. Once you have it, edit the entry and put it in.
Stefan
| Celeste Torkzaban wrote: |
|
Hello,
I like the ELcode feature that lets you easily make an internal link to an attachment in the same post. However, I wasn't able to get this to work in the html editor, even though it's possible to use the ELcode format to link to another post in the logbook. When I type in elog :/1 in the html editor (without the space) and submit (even with an attachment present), it weirdly gets changed and shows up as 61/1 in the submitted elog, without any hyperlink. As far as I know we're using the standard elog code and only modified css parameters. Is there another syntax to link to attachments in html?
Testing it out here: 69699/1 (elog :/1 without the space turned into 69699/1)
|
|
|
|
Filtered browsing, posted by Michael on Fri Oct 6 11:19:34 2023
|
Hi,
is there a trick to get "Filtered browsing" working?
If i am on the first entry and i checked the checkbox of one Attribute, the next entry is still the second one and not the next with the same Attribute. |
elog server crashed due to cookies send by client, posted by Heinz Junkes on Mon Sep 18 13:49:05 2023
|
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)
|
|
Re: elog server crashed due to cookies send by client, posted by Heinz Junkes on Tue Sep 19 10:58:14 2023
|
The server is crached because the author field was accidentally filled with a long string due to an automated (remote) script:
“
Author: The ion getter pump has successfully recovered and appears to be operating steadily once more. Consequently, I proceeded with sputtering to obtain an XPS survey scan of the Au sample. Initially, the stability of the X-ray function was compromised, leading to multiple interruptions. Subsequently, an unexplained issue arose regarding the collection of counts on the channeltron detector. Additionally, the emission current exhibited fluctuations. Fortunately, it seems that we have addressed and resolved the previous issues. In the image below, two XPS survey spectra are presented. The spectrum highlighted with a red line corresponds to the AlKa source, which was selected using the AlKa button. Conversely, the spectrum with a black line represents the MgKa source. In both cases, the energy configuration was set to 1486.7 eV. It's worth noting that the 1050 eV peak in both spectra corresponds to the Au4f state, with an energy displacement of 961.7 eV due to X-ray ghost lines caused by O contamination (84+961.7). It has come to my attention that the Mg source appears to have oxidized, a phenomenon we've observed before. Moreover, it's important to highlight that the difference between the peaks in the low binding energy region is approximately 100 eV, not the expected 233 eV (considering the energy difference between magnesium and aluminum). This observation holds true for both cases where the same energy setting was used. Additionally, the energy of the Au4f peakSotirios Tsatso
“
Instead of just "Sotirios Tsatso".
So it had nothing to do with the cookies etc.. But when the item created in this way was called up, the system crashed:
[248459.853246] elogd_misc[8407]: segfault at 561725164a4e ip 00007f8210c02854 sp 00007ffdcb92b338 error 4 in libc-2.31.so[7f8210a99000+178000]
[248459.853251] Code: 7f 07 c5 fe 7f 4f 20 c5 fe 7f 54 17 e0 c5 fe 7f 5c 17 c0 c5 f8 77 c3 48 39 f7 0f 87 ab 00 00 00 0f 84 e5 fe ff ff c5 fe 6f 26 <c5> fe 6f 6c 16 e0 c5 fe 6f 74 16 c0 c5 fe 6f 7c 16 a0 c5 7e 6f 44
| Heinz Junkes wrote: |
|
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)
|
|
update elog downloads page, posted by Konstantin Olchanski on Fri Sep 15 21:42:38 2023
|
The elog downloads page is slightly out of date, https://elog.psi.ch/elog/download.html
1) the "git clone" instructions work (but there is no git tags corresponding to different releases, I suggest adding test: "elog developers
recommend always using latest version from elog git repository").
2) "elog source code", recommends downloading tar file, but latest tar file is from February 2023, probably out of date. people who can compile elog
from sources can do "git clone", is the "tar" method still relevant?
3) windows binaries, latest available is from 2018, before the famous security fixes, probably no longer safe for running on the open internet. I
suggest we remove this section and say "sorry, windows binaries no longer available".
4) linux binaries, all links are dead, and we have requested removal of elog packages from red hat, debian and ubuntu. (and they have been removed).
K.O. |
|
Re: update elog downloads page, posted by Stefan Ritt on Mon Sep 18 14:38:30 2023
|
Thanks for the reminder, I updated the download instructions. |
|
File/App associations for attachments, posted by Evinrude Motor on Sun Aug 20 20:49:04 2023
|
Is there somewhere I can change the file extension / app associations ? When I open an ".ods" attachment ELOG lets me pick the app . If I open a ".eml" it dumps me into the browser. At the system level ".eml" is associated with "thunderbird"
ELOG on RPI4B , 3.1.5
Client Kubuntu Linux |
|
Re: File/App associations for attachments, posted by Evinrude Motor on Thu Aug 24 15:54:51 2023
|
I was thinking I could accomplish this with some 'attribute' change but havent fogured it out yet .
My preference would be for elog to ask everytime .
| Evinrude Motor wrote: |
|
Is there somewhere I can change the file extension / app associations ? When I open an ".ods" attachment ELOG lets me pick the app . If I open a ".eml" it dumps me into the browser. At the system level ".eml" is associated with "thunderbird"
ELOG on RPI4B , 3.1.5
Client Kubuntu Linux
|
|
|
Re: File/App associations for attachments, posted by Stefan Ritt on Thu Aug 24 16:43:41 2023
|
Below are the MIME types hard-coded into elogd. As you can see there is neither .ods nor .eml. If you give me the MIME type, I can add that easily. I wonder however why both work differently for you. I believe this is a browser setting.
Stefan
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"},
{"", ""},
};
|
Re: File/App associations for attachments, posted by Evinrude Motor on Thu Aug 24 17:21:06 2023
|
so now that you have pointed me in the right direction let me hack on it a bit to see what works .
| Stefan Ritt wrote: |
|
Below are the MIME types hard-coded into elogd. As you can see there is neither .ods nor .eml. If you give me the MIME type, I can add that easily. I wonder however why both work differently for you. I believe this is a browser setting.
Stefan
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"},
{"", ""},
};
|
|
|
Re: File/App associations for attachments, posted by Evinrude Motor on Thu Aug 24 19:22:01 2023
|
I gave it a shot with no luck
On my client (Kubuntu) an ".eml" is associated with mime type "message/rfc822" . Just adding this to the list seemed to have no effect so there must be more to it than that :}
| Stefan Ritt wrote: |
|
Below are the MIME types hard-coded into elogd. As you can see there is neither .ods nor .eml. If you give me the MIME type, I can add that easily. I wonder however why both work differently for you. I believe this is a browser setting.
Stefan
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"},
{"", ""},
};
|
|
|
Re: File/App associations for attachments, posted by Evinrude Motor on Thu Aug 24 19:48:06 2023
|
You were correct . This is 100% a browser issue , Thanks for your assistance.
| Stefan Ritt wrote: |
|
Below are the MIME types hard-coded into elogd. As you can see there is neither .ods nor .eml. If you give me the MIME type, I can add that easily. I wonder however why both work differently for you. I believe this is a browser setting.
Stefan
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"},
{"", ""},
};
|
|
|