ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 786 of 807

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6451 Entries

Goto page Previous 1, 2, 3 ... 785, 786, 787 ... 805, 806, 807 Next

Author Email down

Wed Jan 11 15:54:28 2006

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

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 attributes

http://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

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

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

1771

Mon Mar 13 13:19:09 2006

Broken 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

elog 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

Re: 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

Re: 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 ...

Goto page Previous 1, 2, 3 ... 785, 786, 787 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6