Side effects from debugging, posted by Yoshio Imai on Thu Jan 12 11:38:13 2006
|
Addendum: in the Forum, I found a very strange effect: When deliberately highlighting an entry (http://midas.psi.ch/elogs/Forum/?id=1858), the Elog server no longer keeps the page partitioning, but displays ALL entries of the logbook. I don't know if these problems are related, but maybe you could check (we use the "Full" mode for the list view, in case that matters). I have tried to reproduce the problem with our logbook in threaded mode, but we don't seem to have this problem there.
Yoshio |
Broken thread structure in Forum?, posted by Yoshio Imai on Mon Mar 13 12:51:36 2006
|
Hi!
I noticed that this thread seems to be broken in the Forum. When I view the thread start in single view (http://midas.psi.ch/elogs/Forum/1739), I have access to all subsequent posts, but the first reply seems to be interpreted like a new thread, i.e. when clicking onto it (http://midas.psi.ch/elogs/Forum/1741), the thread start is no longer displayed and accessible in the list of posts. Is this intentional, or is it a bug?
Yoshio |
|
Broken thread structure in Forum?, posted by Yoshio Imai on Mon Mar 13 13:19:09 2006
|
| 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. |
|
elog client authentication and attachment comment, posted by Yoshio Imai on Thu Apr 6 20:24:06 2006
|
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 |
|
Re: elog client authentication and attachment comment, posted by Yoshio Imai on Mon Apr 10 20:08:02 2006
|
| 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 ... |
|
Re: Turn off smileys?, posted by Yoshio Imai on Wed Oct 11 16:03:52 2006
|
| Stefan Ritt wrote: | Put a \ in front of anything which is turned into a smiley, so ;) gets converted into  , 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 ... |
XML, CSV and Raw export produces 'last' page only, posted by Brian Marshall on Mon Nov 6 17:41:13 2006
|
The Find command page provides an option, 'Display n entries per page' which is useful when the result of the search is to be viewed on-screen.
However this value is also applied to CSV, XML and Raw export and only the 'last' page of data is exported.
For example, if there are 17 matching entries and n is set to 8, only one entry will appear in the exported file.
In my opinion, this option should be ignored for XML, CSV and Raw export and all matching entries should be exported. |
Multiple ideas for multiple logbooks, posted by Yoshio Imai on Tue Apr 3 13:17:27 2007
|
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! |
|