ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67964
|
Fri Jun 5 23:08:43 2015 |
| David Wallis | wallis@aps.anl.gov | Bug report | Linux | 3.1.0 | Drag-and-drop not working in elog 3.1.0 | Drag and drop for attachments dosn't work on either Chrome 37.0.2062.94 (64-bit) or FIrefox 31.5.3 (both on Linux). D&D works on the midas.psi.ch demo page.
On my logbooks, the "drop attachements here" area does not have a dashed line border.
I don't see anything in the elogd.conf file that pertains to this feature. |
67965
|
Fri Jun 5 23:10:27 2015 |
| David Wallis | wallis@aps.anl.gov | Bug report | Linux | 3.1.0 | Auto save feature not working on 3.1.0 | Auto-saving does not seem to be working. In the config file, I have the following:
Save drafts = 1
Autosave = 10
but I never see the "auto saving" message or get any other indication that the feature is working.
Am I missing something? |
67966
|
Sat Jun 6 13:38:15 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 3.1.0 | Re: Drag-and-drop not working in elog 3.1.0 | As you've pointed out, for the very same browsers D&D works with the Forum, and that is ELOG 3.1.0.
Hence I can only conclude that it is neither a browser, nor an ELOG issue, but a problem of your local installation. Maybe you try with a fresh and clean installation first? What Linux are you using, by the way?
Or you've picked by bad luck a 3.1.0 version where D&D did really not work. But I cannot tell, since you did not specify the git revision in the ELOG version (it is possible now ;-)
Cheers
Andreas
David Wallis wrote: |
Drag and drop for attachments dosn't work on either Chrome 37.0.2062.94 (64-bit) or FIrefox 31.5.3 (both on Linux). D&D works on the midas.psi.ch demo page.
On my logbooks, the "drop attachements here" area does not have a dashed line border.
I don't see anything in the elogd.conf file that pertains to this feature.
|
|
67972
|
Tue Jun 9 13:01:50 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.0 | Side effects of draft messages (was Fixed text) | I changed it such that drafts are not shown at all in ELOG. The only way you realize them is if you hit "new", and you will be prompted if there is any pending draft.
Andreas Luedeke wrote: |
Hi Stefan,
I got an answer to a forum entry before I actually finished writing my post! It is obviously possible to reply to a draft message.
I think it would be excellent if draft messages would only be shown to their authors (except maybe in case of an anonymous author).
It feels wrong if I watch people while they making an entry ;-)
Anyway, it is just an idea.
Cheers
Andreas
Neal Grafton wrote: |
Thanks Andreas
We are still playing around with ideas, just thought I'd ask, didn't think it was possible.
We are ok with setting attributes but this is new to us as yet so may have more questions later.
Andreas Luedeke wrote: |
Hi Neal,
you can preload words into one attribute field, but one field is either editable or not, you cannot protect single words in a field.
But the ELOG way to solve this would be to have multiple attributes: you would get one entry field for each attribute.
Just look at this logbook: it has the attributes Icon, Author, Author Email, Category, OS, ELOG Version and Subject.
You can change the content of each attribute (except of "Author", that field is made here to be not editable), but as a normal user you cannot change the names in front of the fields.
Did you've set up the demo logbook and played around with it? Because your question suggests to me that you don't figured out yet what ELOG does. Or as a direct answer: no, it does not make sense to me ;-)
But I'm sure you'll figure it out: ELOG is best learned by trial and error.
Kind Regards
Andreas
Neal Grafton wrote: |
Sorry I call this field that you write in the subject field, a little confusing.
So is there anyway to fix the indicated words in place in this typing space so you can enter the text you want next to them but be unable to delete them. (does this make sense?)
Neal
Andreas Luedeke wrote: |
Dear Neal,
I don't understand your example. There is no such thing as a "subject field". You can define an attribute called "subject", like in this logbook.
But I would guess that you want to have five attributes "Time Off", "Reason", etc. that cannot be altered after an entry has been created? That's easy.
Or do you want to protect entries with specific content not to be deleted? That is not easy.
Please explain in more detail what you want to achieve, and I'll be happy to help.
Cheers, Andreas
Neal Grafton wrote: |
I'd like to fix text or table in the subject field that can't be deleted or moved.
Can that be done in config? Example -
Time Off:
Reason:
Update By:
Estimated On time:
Detail:
|
|
|
|
|
|
|
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
|
|
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 ;-)
|
|
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
|
|
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 ;-)
|
|
|
|