| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67992
|
Wed Jun 10 09:12:06 2015 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.10.2 | Re: Path disclosure on unfound file |
What URL did you use? If I try here on this forum I get:
which looks fine to me.
| Bruce Bush wrote: |
|
Greetings,
Running elog 3.1.0 on CentOS 6.6. When I try to access a nonexistent file, elog reveals a path in the 404 page. For example:
Not Found
The requested file /usr/local/elog/themes/default/blortblortblort7854.htm was not found on this server
ELOG version 3.1.0
Is there any way to use a custom 404 page with elog, or to make it stop displaying the file information?
Thank you,
bb
|
|
|
67991
|
Wed Jun 10 08:13:50 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | V3.1.1-2c4f838 | Re: subject line bug on resumit elog entries as new? |
Making a new release takes me about an hour (compile under Windows, Linux, Mac OSX), so I don't do it for each little change. If you want to follow the development closely, I recommend that you learn to compile elog from the GIT repository. It's pretty easy: a git pull, followed by a make and make install.
If you want to see which changes are already in the version you are running, look at the 7 digit GIT hash at the bottom of each elog page and compare it with the bitbucket repository:
| Jacky Li wrote: |
|
Hi,
I compiled the 3.1.0-2 source rpm from the download area. Unless there is a minor release, I think the problem is still there. Thank you.
Jack
|
|
|
67990
|
Tue Jun 9 22:31:59 2015 |
| Jacky Li | zli@hawaii.edu | Question | Linux | V3.1.1-2c4f838 | Re: subject line bug on resumit elog entries as new? |
Hi,
I compiled the 3.1.0-2 source rpm from the download area. Unless there is a minor release, I think the problem is still there. Thank you.
Jacky
| David Pilgram wrote: |
|
Hi Stefan,
The email sent from here had he expected (correct) message "A new ELOG entry..."
Thanks, David.
| Stefan Ritt wrote: |
|
Any better now?
| David Pilgram wrote: |
|
Hi Stefan,
I see that you've updated the elog running this forum today, 5 versions after you reported fixing the "A new elog entry has been entered" and "An old elog entry has been updated" issue. But the emails coming out are still all of the "An old elog entry...", rather than "A new..."
|
|
|
|
|
67989
|
Tue Jun 9 20:26:00 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | V3.1.1-22022e6 | Re: Problem with a draft message |
I missed or don't remember that post. My vote is replace "Back" with "Delete" - or "Abort"
| Stefan Ritt wrote: |
|
Just read what I wrote at elog:67983
| David Pilgram wrote: |
|
Just to comment that the expected emails that one would have expected with the last two entries have either
been held up or simply have not been generated and sent - both the preceeding entries were submitted by using the "Back" button, this time I'll use the "Submit" button, which should generate a email.
| David Pilgram wrote: |
|
Just to comment that I submitted the entry below by pressing the "Back" button!
| David Pilgram wrote: |
|
Hi Stefan,
I had started to write a completely different bug report, but then realised I had not checked a detail. I had written about one sentence. So I decided to abort the message, and hit the "back" button. Only I found that this had created a new entry in the elog listings. I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!
It doesn't seem to have created an email, though. And for the sake of all your users, I'd not want to experiment here on the matter too much!
|
|
|
|
|
|
67988
|
Tue Jun 9 19:35:28 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | V3.1.1-22022e6 | Re: Problem with a draft message |
Just read what I wrote at elog:67983
| David Pilgram wrote: |
|
Just to comment that the expected emails that one would have expected with the last two entries have either
been held up or simply have not been generated and sent - both the preceeding entries were submitted by using the "Back" button, this time I'll use the "Submit" button, which should generate a email.
| David Pilgram wrote: |
|
Just to comment that I submitted the entry below by pressing the "Back" button!
| David Pilgram wrote: |
|
Hi Stefan,
I had started to write a completely different bug report, but then realised I had not checked a detail. I had written about one sentence. So I decided to abort the message, and hit the "back" button. Only I found that this had created a new entry in the elog listings. I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!
It doesn't seem to have created an email, though. And for the sake of all your users, I'd not want to experiment here on the matter too much!
|
|
|
|
|
67986
|
Tue Jun 9 17:23:27 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | V3.1.1-22022e6 | Re: Problem with a draft message |
Just to comment that the expected emails that one would have expected with the last two entries have either
been held up or simply have not been generated and sent - both the preceeding entries were submitted by using the "Back" button, this time I'll use the "Submit" button, which should generate a email.
| David Pilgram wrote: |
|
Just to comment that I submitted the entry below by pressing the "Back" button!
| David Pilgram wrote: |
|
Hi Stefan,
I had started to write a completely different bug report, but then realised I had not checked a detail. I had written about one sentence. So I decided to abort the message, and hit the "back" button. Only I found that this had created a new entry in the elog listings. I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!
It doesn't seem to have created an email, though. And for the sake of all your users, I'd not want to experiment here on the matter too much!
|
|
|
|
67985
|
Tue Jun 9 17:21:25 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | V3.1.1-22022e6 | Re: Problem with a draft message |
Just to comment that I submitted the entry below by pressing the "Back" button!
| David Pilgram wrote: |
|
Hi Stefan,
I had started to write a completely different bug report, but then realised I had not checked a detail. I had written about one sentence. So I decided to abort the message, and hit the "back" button. Only I found that this had created a new entry in the elog listings. I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!
It doesn't seem to have created an email, though. And for the sake of all your users, I'd not want to experiment here on the matter too much!
|
|
|
67984
|
Tue Jun 9 17:17:11 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | V3.1.1-22022e6 | Problem with a draft message |
Hi Stefan,
I had started to write a completely different bug report, but then realised I had not checked a detail. I had written about one sentence. So I decided to abort the message, and hit the "back" button. Only I found that this had created a new entry in the elog listings. I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!
It doesn't seem to have created an email, though. And for the sake of all your users, I'd not want to experiment here on the matter too much! |