Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 384 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 383, 384, 385 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  1398   Mon Aug 15 12:54:56 2005 Reply Michael Husbynmichaelh@online.noQuestionLinux2.5.9-2Re: Omitting some fields in e-mail
> 
> > I added the option "Email attributes = <list>" for that. So you can specify
> > 
> > Email attributes = UA, Pri, Status, Oppdragsgiver, EpostTil, Tittel
> > 
> > which also sets the order of the attributes. The cange is in CVS.

Hello Stefan,

Tested the 2.6.0-beta4, and it sort of works. config parameter:
Email attributes = Tittel,Status

gives the mail:

Logbook             : work
Tittel              : Test
Status              : Åpen

Logbook URL         : http://xxxxxxxxxxxxxxxx/work/904

---

Is there a way to remove Logbook field (and perhaps Logbook URL if I want?)

Best regards
Michael
  1405   Mon Sep 5 20:16:50 2005 Reply Stefan Rittstefan.ritt@psi.chInfoLinux2.5.7Re: charset specified in elog.conf has no effect [updated]

cunnilinux wrote:
well, here's the problem that i had: my charset (koi8-u) was specified in elog.conf for every logbook, but this had no effect, and all elog pages continued tu appeared as iso-8859-1 (which is the default) when i specified charset in the global section, the problem's gone away.

2do: i think it's worth testing how does it work whet charset specified for a separate logbook overrides globally specidied charset

elog version that is in use: 2.5.7 from debian sarge 3.1 r0a powerpc


The documentation clearly states that the "charset" option is under the [global] section. I put it there since it does not make much sense to have separate charsets for separate logbooks. Or do you have one Russian, one Japanese and one Swedish logbook on the same server? Maybe for an international language school Wink

I can easily put it into the individual logbook's config, but only if more than one person requests this.
  1407   Mon Sep 5 20:39:15 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0-betaRe: Long lines in printout
> long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain
> text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer.
> Does anybody know a solution for this? 

Can you post an example here? If I try a
veeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeery
 long line, it's shown correctly. You just have to scroll right in your browser.
  1409   Tue Sep 6 09:41:04 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.0-b4Re: Comment tooltip shows comment from other logbook

Oleg Solovyanov wrote:
I have several logbooks with Comment lines,
but the tooltip shows sometimes the correct comment,
sometimes the comment from other logbook...

I see the same behaviour also on this very page...

I use Mozilla 1.7.10.
Tried with Konqueror -> same problem.


Should be fixed in the current CVS version (see this page)
  1410   Tue Sep 6 14:41:10 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.5.9-2Re: Omitting some fields in e-mail
> Is there a way to remove Logbook field (and perhaps Logbook URL if I want?)

There is the option "Email format", which lets you specify what to show. Try 

Email format = 27
  1412   Thu Sep 8 03:37:44 2005 Reply Noah PnaQuestionLinux2.5.9+r167Re: changing the default to plain text rather than elcode
I, too, found that this elcode.js file was missing. However, it seems to be present on this demo site!

so, I downloaded it from this very demo site, and saved it to my system (in the root of your resources folder). This (so far) seems to have made the "ELCode" formatting mode work properly.

This is the URL I used. It seems that this file was ommitted from the latest distribution:

http://midas.psi.ch/elogs/elcode.js

Hope that helps!
  1413   Mon Sep 12 10:44:51 2005 Reply Bertram Metzbmetz@sbs.comQuestionLinux2.6.0-betaRe: Long lines in printout
> > long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain
> > text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer.
> > Does anybody know a solution for this? 
> 
> Can you post an example here? If I try a
>
veeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeery
>  long line, it's shown correctly. You just have to scroll right in your browser.

the lines are displayed as expected on the screen, but they are cut off when the browser window is printed via
the browsers print function.
This did not occur in a previous version (V2.5.6).  

Bertram
Attachment 1: elog_lon_lines_screen.jpg
elog_lon_lines_screen.jpg
Attachment 2: elog_lon_lines_print.jpg
elog_lon_lines_print.jpg
  1414   Tue Sep 13 13:33:59 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0-betaRe: Long lines in printout
Your problem is related with the fact that I changed the formatting from fixed font to proportional font ("ELCode"). This gives you three options:

  • Enter your elog entries in "plain" text, which brings you back to the old mode
  • Change the page setup of your browser. Mozilla Firefox has File/Page Setup/Shrink to fit page and left and right margin
  • Reduce the entry window via the config setting "Message width"
Goto page Previous  1, 2, 3 ... 383, 384, 385 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6