Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 58 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6444 Entries 
Goto page Previous  1, 2, 3 ... 57, 58, 59 ... 804, 805, 806   Next  
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  1771   Mon Mar 13 13:19:09 2006 Reply Yoshio ImaiBug reportLinux2.6.1-1671Broken thread structure in Forum?

Stefan Ritt wrote:
I have no clue how this could have happened, but I fixed it by manually editing the log file.


I also have never come across anything like this in our logbooks (approx. 10000 entries), so it doesn't look like a bug.
  1799   Thu Apr 6 20:24:06 2006 Question Yoshio ImaiQuestionLinux2.6.1-1671elog client authentication and attachment comment
Hi again!

I have two questions, one concerning authentication methods for the elog client. Until revision 1642, it was possible to submit entries to a password-protected logbook using the elog client without supplying authentication information. With revision 1671 this is no longer possible. In principle this is good. However, many of our run control programs use the elog client (via rsh to the elog server computer) to submit automatic entries, which fails now. In order for this mechanism to work again, we would have to change the command-line call in the sources, including now the password in clear text. Since this can be considered a security issue, we would like to avoid it if at all possible. I guess my request would go in the direction of PAM support, but would it be possible to revert to the old behaviour as an option? (If you tell me where in the code to look, we could probably also comment out the respective lines ourselves so that you don't have extra work...)

The second remark is about attachment comments. When editing a logbook entry, the attachment upload buttons appear again, but without the comment. Shouldn't it be there, too?

Thanks,

Yoshio
  1803   Mon Apr 10 20:08:02 2006 Reply Yoshio ImaiQuestionLinux2.6.1-1671Re: elog client authentication and attachment comment

Stefan Ritt wrote:
We could save the username/password in a file on the server, which is maybe readable only by the owner.

I have discussed it with the others, and it sounds like a good idea. There is only the debate whether it should be readable by the owner or by the root user of the elog server. I can't tell at the moment which is more favourable ...
  1981   Wed Oct 11 16:03:52 2006 Reply Yoshio ImaiQuestionLinux2.6.2-1714Re: Turn off smileys?

Stefan Ritt wrote:
Put a \ in front of anything which is turned into a smiley, so ;) gets converted into Wink, but \;) does not get converted

Other suggestion: What about going the other way round and making this 
\?)
the smiley and this 
?)
the usual question in brackets? If there was a special sequence to announce the unusual case (i.e. the smiley), I think less people would complain about having unwanted conversions ...
  2183   Tue Apr 3 13:17:27 2007 Idea Yoshio ImaiRequestLinux2.6.4-1795Multiple ideas for multiple logbooks
Hi!

After a long pause, here we are again with a bunch of new ideas (and problems ...;) )

1. Multiple login
Since we are using the elog system now for most aspects of our work, we are more and more often confronted with the need to work with different logbooks open in parallel (e.g. the shift logbook as well as the personal analysis logbook, via tabbed browsing). These logbooks do not always have the same users allowed to access them, so when having logged on to one logbook and then opening another one in a different browser tab, I have to log on as a different user, thereby losing the login on the first logbook. Is there any way to change the cookie structure so as to allow one (physical) user to be logged on as more than one elog user at a time?

2. <Ctrl-T>
While using this logbook (and tabbed browsing), I noticed that the keyboard shortcut <Ctrl-T> now leads to the creation of a table (great thing, btw). However, many of our users are accustomed to this shortcut opening a new browser Tab. Is there any way to disable these elog shortcuts or otherwise disentangle these functions (by using <Alt> instead of <Ctrl> or something similar, since the functionality itself is very good)?

Thanks for any idea on these issues, and thanks for the great software!
  2187   Tue Apr 3 17:55:21 2007 Smile Yoshio ImaiBug reportLinux2.6.4-1826Re: Multiple ideas for multiple logbooks

Stefan Ritt wrote:
Well, you didn't realize, but you were my beta-tester for the keyboard shortcuts Big grin . I didn't yet publish it, so you must have gotten this brand new feature from SVN.

You should really have told me Wink . Actually, I found out about the <Ctrl-C> issue while using this logbook.

Stefan Ritt wrote:
So get the SVN update, and let me know what you think

Did so, we are running now -1826. I think it is very usable, with maybe one exception (this might be a browser issue, however): When using the shortcuts and/or the ELCode buttons, sometimes the code is generated and the cursor in between the [XX] and [/XX] directive, but sometimes, the whole code directive is selected as if for editing

which prevents from immediately continuing to type (which, I guess, was the idea behind the shortcuts). The behaviour is not completely reproducible, and I have even seen it change during one and the same browser (=firefox) session while working on the same entry (*). I also had it once that the browser out of a sudden completely ignored the ELCode meaning, and instead used <Ctrl-I> for page info and <Ctrl-B> for the history.

(*) It just happened again!


BTW, there are (of course Big grin) two other issues. They are still present in -1826
- one bug was reported by a logbook user: when using the "find" function in a logbook, and selecting one value from the "Author" drop-down list and another from the "Category" drop-down list, the elogd reports no entries found, but when specifying only the "Author" and leaving "Category" blank, many entries are found, including those with the "Category" being looked for. When specifying only the "Category" and leaving the "Author" blank, the elogd also reports no entries found. Has anyone reported a similar behaviour?

- We have one logbook top group for the beamtimes. Under certain conditions, a preset text is to be displayed. 
{2&a} Preset Text = resource/text_1.txt
{2&b} Preset Text = resource/text_2.txt
However, the definitions of these conditions have to be repeated for every logbook in the group (putting it only under [global beamtimes] doesn't do it), otherwise they are ignored.

Any idea on these?
  2191   Wed Apr 4 11:37:56 2007 Agree Yoshio ImaiRequestLinux2.6.4-1795Re: Multiple ideas for multiple logbooks

Stefan Ritt wrote:
Actually there is a way

... and it works! Thank you!


Stefan Ritt wrote:
I fixed that now in the updated elcode.js.

That works now, too!


Stefan Ritt wrote:
Your other problem of ignoring the control keys at all I could not reproduce. Try to reproduce it in a well-defined way and let me know.

I will try to do that (new beamtime, new occasions ... Wink).


Stefan Ritt wrote:
Maybe you used a userlist attribute for the author?

No, I didn't. I will try to investigate this further and let you know if I find anything.

So for the moment ... thanks for the help!
  2193   Wed Apr 4 14:20:41 2007 Reply Yoshio ImaiBug reportLinux2.6.4-1826Re: Multiple ideas for multiple logbooks

Stefan Ritt wrote:
Maybe some other problem?

Possible, but I think it worked also on our server until the number of logbooks in the top group got larger than one. Can you try to see if your code still works when there is more than one logbook defined?
Goto page Previous  1, 2, 3 ... 57, 58, 59 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6