ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69499
|
Tue Mar 22 17:58:32 2022 |
| Greg Christian | gchristian@tamu.edu | Question | Linux | V3.1.4-395e101 | Re: Unformatted Appearance of Elog | In trying to fix this, I have re-downloaded the source from github rather than the source at http://elog.psi.ch/elog/download/tar/elog-latest.tar.gz, which is apparently very different from what is on github. Now I am running ELOG V3.1.4-d828aa58
The problem still persists, however, although only for some of the logbooks. Curiously, it *seems* to only show up if I run elogd with the -D flag. If I just run it in the terminal, I have not seen the formatting problem (so far).
In case it's helpful, I post my elodg.cfg file.
Greg Christian wrote: |
I recently ported an elog over to a new server running Ubuntu 20.10. Everything is working okay, except sometimes I get a strange unformatted appearance when I go to the elog page (see attachment). The happening of this seems random. For example, yesterday, when I started the elogd daemon everything looked fine, but when I log in today I get the unformatted appearance. Also, yesterday when I was setting things up, sometimes certain logbooks would have the formatting issue, and I could make this go away with a kill...restart cycle of elogd.
I downloaded the source code from here: https://elog.psi.ch/elog/download.html, selecting the elog-latest.tar.gz file.
I have tried viewing the elog on 3 different browsers (firefox, IE, Edge), result is the same every time.
Any thoughts about what the problem is?
|
|
69498
|
Fri Mar 18 00:36:37 2022 |
| Konstantin Olchanski | olchansk@triumf.ca | Bug report | Linux | ELOG V3.1.4-2e1 | http status 200 returned for "file not found" | "file not found" should return http code 404. elogd returns code 200 together
with a page containing text "404 not found". This pollutes the browser cache
with wrong content (in this case, we are trying to load a css file, and the browser
is trying to use text "404 not found" as if it were a css. bad. file not found
should return http code 404. K.O.
in example below, response "HTTP/1.1 200 Document follows" should be "HTTP/1.1 404 ..."
to reproduce, through the https proxy:
daq00:~$ curl -v https://daq00.triumf.ca/elog-midas/Midas/zzz.css
* Trying 142.90.111.168:443...
...
> GET /elog-midas/Midas/zzz.css HTTP/1.1
...
< HTTP/1.1 200 Document follows
< Date: Thu, 17 Mar 2022 23:40:04 GMT
< Server: ELOG HTTP 3.1.4-2e1708b5
< Strict-Transport-Security: max-age=31536000; includeSubDomains
< Content-Type: text/html;charset=ISO-8859-1
< Vary: Accept-Encoding
< Transfer-Encoding: chunked
<
<!DOCTYPE html>
<html><head>
<meta name="ROBOTS" content="NOINDEX, NOFOLLOW">
<title>404 Not Found</title>
<link rel="stylesheet" type="text/css" href="elog.css">
<link rel="shortcut icon" href="favicon.ico" />
<link rel="icon" href="favicon.png" type="image/png" />
</head>
<body><h1>404 Not Found</h1>
The requested file <b>zzz.css</b> was not found on this server<p>
* Connection #0 to host daq00.triumf.ca left intact
daq00:~$
directly:
daq00:~$ curl -v http://localhost:9080/Midas/zzz.css
* Trying 127.0.0.1:9080...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 9080 (#0)
> GET /Midas/zzz.css HTTP/1.1
> Host: localhost:9080
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 Document follows
< Server: ELOG HTTP 3.1.4-2e1708b5
< Content-Type: text/html;charset=ISO-8859-1
< Connection: Close
<
<!DOCTYPE html>
<html><head>
<meta name="ROBOTS" content="NOINDEX, NOFOLLOW">
<title>404 Not Found</title>
<link rel="stylesheet" type="text/css" href="elog.css">
<link rel="shortcut icon" href="favicon.ico" />
<link rel="icon" href="favicon.png" type="image/png" />
</head>
<body><h1>404 Not Found</h1>
The requested file <b>zzz.css</b> was not found on this server<p>
* Closing connection 0
daq00:~$ |
69497
|
Thu Mar 17 18:22:37 2022 |
| Greg Christian | greg.christian@smu.ca | Question | Linux | V3.1.4-395e101 | Unformatted Appearance of Elog | I recently ported an elog over to a new server running Ubuntu 20.10. Everything is working okay, except sometimes I get a strange unformatted appearance when I go to the elog page (see attachment). The happening of this seems random. For example, yesterday, when I started the elogd daemon everything looked fine, but when I log in today I get the unformatted appearance. Also, yesterday when I was setting things up, sometimes certain logbooks would have the formatting issue, and I could make this go away with a kill...restart cycle of elogd.
I downloaded the source code from here: https://elog.psi.ch/elog/download.html, selecting the elog-latest.tar.gz file.
I have tried viewing the elog on 3 different browsers (firefox, IE, Edge), result is the same every time.
Any thoughts about what the problem is? |
69496
|
Mon Mar 14 18:45:14 2022 |
| James Darrow | kb9mmc@ameritech.net | Question | Linux | 3.1.3-7933898 | Re: Removal of ID and Date attributes | That worked! Thanks Stefan
Stefan Ritt wrote: |
Use the configuration option
List display = Day, Station Type, Start time UTC, ...
as written in the documentation.
Best,
Stefan
James Darrow wrote: |
Hello all,
I just found elog which is a great piece of software! I'm implementing it for use to log my shortwave listening contacts. The problem that I have is I'm moving over a current log to elog which already has a date of when the record was created, which is important.I renamed the old date to day to upload the log into elog. My problem is I don't need to see elog's ID# or date/time stamp of when the log was created seeing it's already in my data. My question is, is there any way to not show elog's ID# and date/time stamp or would I need to create a tab and if so could someone provide a config file where I could see how the tab was implemented. I've attached a screenshot of what it looks like so far. I've implemented the dark theme (which I like) that Anthoney had posted in the contibutions section.
Thanks in advance!
Jim
|
|
|
69495
|
Mon Mar 14 08:49:44 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.3-7933898 | Re: Removal of ID and Date attributes | Use the configuration option
List display = Day, Station Type, Start time UTC, ...
as written in the documentation.
Best,
Stefan
James Darrow wrote: |
Hello all,
I just found elog which is a great piece of software! I'm implementing it for use to log my shortwave listening contacts. The problem that I have is I'm moving over a current log to elog which already has a date of when the record was created, which is important.I renamed the old date to day to upload the log into elog. My problem is I don't need to see elog's ID# or date/time stamp of when the log was created seeing it's already in my data. My question is, is there any way to not show elog's ID# and date/time stamp or would I need to create a tab and if so could someone provide a config file where I could see how the tab was implemented. I've attached a screenshot of what it looks like so far. I've implemented the dark theme (which I like) that Anthoney had posted in the contibutions section.
Thanks in advance!
Jim
|
|
69494
|
Sun Mar 13 21:20:56 2022 |
| James Darrow | kb9mmc@ameritech.net | Question | Linux | 3.1.3-7933898 | Removal of ID and Date attributes | Hello all,
I just found elog which is a great piece of software! I'm implementing it for use to log my shortwave listening contacts. The problem that I have is I'm moving over a current log to elog which already has a date of when the record was created, which is important.I renamed the old date to day to upload the log into elog. My problem is I don't need to see elog's ID# or date/time stamp of when the log was created seeing it's already in my data. My question is, is there any way to not show elog's ID# and date/time stamp or would I need to create a tab and if so could someone provide a config file where I could see how the tab was implemented. I've attached a screenshot of what it looks like so far. I've implemented the dark theme (which I like) that Anthoney had posted in the contibutions section.
Thanks in advance!
Jim |
69493
|
Wed Mar 9 17:55:31 2022 |
| Jan Just Keijser | janjust@nikhef.nl | Question | Windows | 3.1.4-a04faf9f | Re: Vulnerability? | I've built the last C version of elog in git, revision 1ebfd06c using mingw-64 ; the resulting binaries work for me on Windows 2019.
Attached is a zip file with the binaries.
I was not able to create a new installer, these are just the executables |
69492
|
Wed Mar 9 16:25:31 2022 |
| Edmund Hertle | edmund.blomley@kit.edu | Request | All | 3.1.4 | Use different HTML class for drafts compared to not existing entries | Right now a Draft shows a red error indication, that the entry is currently a draft. For the CSS styling it uses the HTML class="errormsg". The same class is also used if an entry does not exist.
Would it be possible for the draft version to use a different HTML class (for example class="draftmsg")? It can also use the same visual style (or making it yellow would probably also work)
The reason is that the py_elog Interface uses the class="errormsg" to determine if an entry does not exist ( https://github.com/paulscherrerinstitute/py_elog/blob/master/elog/logbook.py#L394 ) and refuses to return the content for this entry. One could possibly fix that also on the py_elog part, but it would probably at least require parsing of actual text (which might make problems for translated pages). Alternativley one could also look for the edit button, but maybe a small change on the elog server side is the simplest solution to this problem?
|
|