Re: Logbook aliases, posted by Yoshio Imai on Wed Dec 14 15:45:29 2005
|
| Stefan Ritt wrote: | | If you click "List" on the single entry page, it takes you by default to the listing page. |
I also think this is the best way to do it.
BTW, now that everyone here got used to the current elog look&feel, I think we no longer need the conditional hiding of attributes (don't hit me...  ). I hope you didn't invest too much time in that already.
Thanks, and happy beamtime!
Yoshio |
|
Re: "Logkook dir" in top group [global] section ineffective, posted by Yoshio Imai on Wed Jan 4 15:27:31 2006
|
| Stefan Ritt wrote: | | I implemented that request. When you click on "list", it takes you to the listing page containing the current entry, which is even highlighted. Have a look at this forum if this is what you like. |
Thank you!
I just installed the latest revision; it is exactly what we need.
I found one problem, however: while linking the binaries for elogd, the linker complained about an undefined reference to forkpty implemented in libutil. I had to add the linker option -lutil to the Makefile target elogd:, then it compiled correctly.
One strange thing (maybe it isn't strange at all) is the following behaviour: when the list view is set to "summary", then the line containing the entry where we clicked "list" is highlighted, however when the list view is set to "full", it isn't. Is this "a bug, or a feature"?
Thanks for the work from all, and happy new year.
Yoshio |
Page browsing links in Find mode broken, posted by Yoshio Imai on Wed Jan 11 15:54:28 2006
|
Hi!
We are having problems with the "Find" mode in the latest revision. When we used "Find" to search for specific texts, and the results span more than one page (say, 2 for example), the page links in the command bar on top point to the ELOG pages rather than the find result pages. This means that, when I click onto "Previous" from find result page 2 (which is the first page getting displayed), I get to logbook page 1 (entries 1 to 20) and not to the previous page of find results. I think this didn't happen in earlier versions. Could you check that? It also happens here in the Forum.
Thanks
Yoshio |
|
Side effects from debugging, posted by Yoshio Imai on Thu Jan 12 11:32:19 2006
|
| Stefan Ritt wrote: | | Thanks for reporting this bug, I fixed it in revision 1597. |
Thanks for your quick reaction! Unfortunately, there is one side effect. As far as I understand, you fixed the bug by preserving the command attributeshttp://www.logbook.domain/logbook/pageN?command when browsing with the Goto page links, so that when a filter is applied, it is still active upon page change. However, the same is true for all other commands, including the ?id=NNN command which is active when clicking List from single entry view. If you click onto, e.g. Previous in this mode, the elogd has a conflict in that it is required to display one page and having to highlight an entry that resides on another. http://www.logbook.domain/logbook/pageN?id=NNN The highlighting supersedes, and the page browse links are effectively disabled. Is there a way to keep the bug fix but disable the side effects, e.g. selectively not preserving the ?id=NNN upon page browsing? Maybe you could implement a "blacklist" of not-to-be-preserved commands, in case there are other problems like this one.
Thanks for the work (I saw the timestamp!)
Yoshio |
|
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 |
|