ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1546
|
Tue Dec 13 10:51:13 2005 |
| Yoshio Imai | | Request | Linux | 2.6.0beta5 | Logbook aliases | Hi!
Is it possible to implement aliases for logbooks? We would like to use a new logbook for every beamtime, but many services need to read/write to the respective current beamtime logbook. It would therefore be nice to have logbook "aliases", so that e.g. a "virtual" logbook beam could be defined to be an alias/redirection to the current beamtime logbook, and all services could refer to that one instead of having to be reconfigured for each beamtime.
This could also help to make sure everyone on shift writes the entries to the correct logbook ... 
Yoshio Imai |
1548
|
Wed Dec 14 11:40:54 2005 |
| Yoshio Imai | | Request | Linux | 2.6.0beta5 | Re: Logbook aliases | Ok, we will try this.
In our case, the "symlink"-type logbook might have been nice because of our daily backup routines. If we move the data of the old logbook to the newly created one, the backup process would first need to upload all logbook data to the backup server under the new directory name and then delete those under the old name.
In our case this is not so much of a problem, because the logbooks are small (100MB), but maybe you can add this to the wishlist if others request the same... (We could try to adjust the backup procedure, but I don't know how well this would work).
Anyway, thanks for the work!
P.S. What do you think about the idea of a "Go to page"-button for the single entry view? |
1550
|
Wed Dec 14 15:45:29 2005 |
| Yoshio Imai | | Request | Linux | 2.6.0beta5 | Re: Logbook aliases |
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 |
1574
|
Wed Jan 4 15:27:31 2006 |
| Yoshio Imai | | Bug report | Linux | 2.6.0 | Re: "Logkook dir" in top group [global] section ineffective |
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 |
1582
|
Wed Jan 11 15:54:28 2006 |
| Yoshio Imai | | Bug report | Linux | 2.6.0r1593 | Page browsing links in Find mode broken | 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 |
1585
|
Thu Jan 12 11:32:19 2006 |
| Yoshio Imai | | Bug report | Linux | 2.6.0r1597 | Side effects from debugging |
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 |
1586
|
Thu Jan 12 11:38:13 2006 |
| Yoshio Imai | | Bug report | Linux | 2.6.0r1597 | Side effects from debugging | 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 |
1769
|
Mon Mar 13 12:51:36 2006 |
| Yoshio Imai | | Bug report | Linux | 2.6.1-1671 | Broken thread structure in Forum? | 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 |
|