ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67983
|
Tue Jun 9 17:09:22 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.0-2 | ELOG Forum: drafts cannot be deleted |
> Another strange thing: the draft got submitted when I hit the "Back" button after reopening it.
Well, this is a problem indeed. When edit entries now, drafts gets saved regularly, overwriting your original entry. This is a limitation of the elog database, which cannot do full versioning. So "Back" is actually the same as "Commit without email notification". Or better "Commit some ten seconds ago". Now I
don't know what the best solution is. I'm tempted to just remove the "Back" button and replace it with a "Delete" button. So people can either submit an entry or delete it completely. Any thoughts? |
67982
|
Tue Jun 9 16:58:28 2015 |
| Christof Hanke | hanke@rzg.mpg.de | Request | All | 3.1.0 | Re: logout to external page |
Yes, I saw it on bitbucket, also all the commits. Thanks!
Stefan Ritt wrote: |
I implemented it, but actually called it Logout to URL = <URL>
Christof Hanke wrote: |
Hi Stefan,
I am happy to see that you include the webserver authentication.
So I can now login at some other page and then access elog.
However, I would also need some means of logging out some where else.
For this I propose a new Configuration option "Logout to page" which redirects to another page if set and "Logout to main" is 0.
See the attached patch (against git HEAD)
Does this make sense to you ?
Christof
PS: Many thanks for the autosave mode, I already used it ;-)
|
|
|
67981
|
Tue Jun 9 16:57:06 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Comment | All | 3.1.0 | Re: Documentation of the webserver authentication |
Also this made it now to the docs. Thanks.
Christof Hanke wrote: |
Hi Stefan,
here is a draft of how you could describe the webserver authentication in your docs.
T/Christof
|
|
67980
|
Tue Jun 9 16:51:55 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | V3.1.1-2c4f838 | Re: subject line bug on resumit elog entries as new? |
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..."
|
|
|
67979
|
Tue Jun 9 16:46:48 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | V3.1.1-2c4f838 | Re: subject line bug on resumit elog entries as new? |
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..."
|
|
67978
|
Tue Jun 9 16:17:06 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | V3.1.1-2c4f838 | Re: subject line bug on resumit elog entries as new? |
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..."
David.
Stefan Ritt wrote: |
I fixed both issues, now resubmitting an entry or submitting a new entry both yields "New LEOG entry".
Jacky Li wrote: |
Hi,
I updated an old elog entry and resubmit it as new by checking the box resubmit as new. Does the subject line should said it is a "New ELOG entry" instead of "Updated ELOG entry"? Thank you.
Also when some people submit a new elog, the subject line is "Updated ELOG entry". This is a bit odd. I can't reproduce that bug when I did my test.
Jacky
|
|
|
67977
|
Tue Jun 9 16:09:39 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 3.1.0 | Re: logout to external page |
I implemented it, but actually called it Logout to URL = <URL>
Christof Hanke wrote: |
Hi Stefan,
I am happy to see that you include the webserver authentication.
So I can now login at some other page and then access elog.
However, I would also need some means of logging out some where else.
For this I propose a new Configuration option "Logout to page" which redirects to another page if set and "Logout to main" is 0.
See the attached patch (against git HEAD)
Does this make sense to you ?
Christof
PS: Many thanks for the autosave mode, I already used it ;-)
|
|
67976
|
Tue Jun 9 15:44:49 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | All | 3.1.0 | Re: parse a correctly the username in save_user_config when using Webserver authentication |
Hi Christof,
thanks for the patch, I merged it into the current HEAD.
/Stefan
Christof Hanke wrote: |
Hi Stefan,
When we use Webserver authentication, we have the correct username already in the variable http_user.
The old way of copying this http_user to "user" is wrong since we don't use the size of http_user.
Instead, just encode the http_user variable directly.
See attached patch against git HEAD.
Christof
|
|