Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 631 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  1575   Mon Jan 9 20:09:16 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.0Re: "Logkook dir" in top group [global] section ineffective

Yoshio Imai wrote:
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"? Wink


Was a bug. I have fixed that in revision 1591.
  1582   Wed Jan 11 15:54:28 2006 Warning Yoshio ImaiBug reportLinux2.6.0r1593Page 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
  1583   Wed Jan 11 21:06:06 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.0r1593Re: Page browsing links in Find mode broken
Thanks for reporting this bug, I fixed it in revision 1597.
  1585   Thu Jan 12 11:32:19 2006 Warning Yoshio ImaiBug reportLinux2.6.0r1597Side 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 Reply Yoshio ImaiBug reportLinux2.6.0r1597Side 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
  1587   Thu Jan 12 15:50:51 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.0r1597Side effects from debugging
Both problems have been fixed in revision 1598.
  1598   Tue Jan 17 16:04:28 2006 Angy Mark Coudrietmarkcoudriet@yahoo.comBug report  In version 2.6 the themes do not work right on Windows.
In version 2.6 the themes do not work right on Windows. 
The URL is fixed at whichever logbook that is selected (e.g. ELOG 2.5.9-4 is <link rel="stylesheet" type="text/css" href="default.css"> & ELOG 2.6.0-1 is <link rel="stylesheet" type="text/css" href="http://localhost:8080/demo/default.css">).
  1599   Wed Jan 18 02:22:44 2006 Question Adam BlandfordAdam.Blandford@dsto.defence.gov.auBug report 2.6.0Attribute substitution in email configuration
In the logbook config file I am not able to use attribute substitution in the <string> tag for
Use Email Heading = <string>
Attribute substitution does work however for
Use Email Subject = <string>
e.g.
Use Email Subject = ELOG $logbook entry; $Category: $Subject
will result in an email subject of: "ELOG Forum entry; Bug Report; Attribute substitution in email configuration"
Use Email Heading = A new entry has been submitted by $long_name on $remote_host on $date
will result in an email heading of: "A new entry has been submitted by $long_name on $remote_host on $date"

Not sure if this functionality is intended or is a bug. An comment/feedback/suggestion would be appreciated.
ELOG V3.1.5-3fb85fa6