Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 223 of 796  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSup ELOG Version Subject
  1577   Mon Jan 9 20:53:28 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0Re: MS Fonts only in ELCode options?

T. Ribbrock wrote:
I'm just after installing 2.6.0 and marvelling at all the changes, especially ELCode (I was using 2.5.8 previously). However, I noticed that the "FONT" menu for ELCodes only offers Microsoft fonts Astonished - something I usually avoid like hell when publishing web content, as I cannot rely on those being installed on the clients. As far as I can see there is no easy way to change this, short of patching the source - or is there?
I'd want to add at least options like "serif" and "sans-serif" and maybe some standard (Unix\?) fonts like "Helvetica".


In revision 1593 I implemented a "Fonts = ..." option where you can specify a list of fonts to be shown on the list. I tried however the MS set of fonts on a Linux system, and found that the MS fonts got mapped to Unix fonts in a reasonable way. Even the Comic Sans MS font was avalilable.
  1580   Tue Jan 10 10:42:18 2006 Reply T. Ribbrockemgaron@gmx.netQuestionLinux2.6.0Re: MS Fonts only in ELCode options?

Stefan Ritt wrote:

In revision 1593 I implemented a "Fonts = ..." option where you can specify a list of fonts to be shown on the list. I tried however the MS set of fonts on a Linux system, and found that the MS fonts got mapped to Unix fonts in a reasonable way. Even the Comic Sans MS font was avalilable.


Very nice, thanks! Yes, vou're right, MS fonts have a chance of working on newer Linux distributions, but not on all and there are still older ones out there - never mind all those folks sitting behind some kind of Solaris/Sparc box or similar... Big grin
  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.
  1584   Wed Jan 11 21:12:13 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0beta5Re: Getting back from "Find" mode

Yoshio Imai wrote:
Is there a more direct way to get back to the unfiltered list view than selecting an entry and go to "List" or using "Find" again and clicking on "Back"?


Yes, just click on the logbook tab on the very top of the page.
Attachment 1: elog.gif
elog.gif
  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.
ELOG V3.1.5-2eba886