Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 224 of 801  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  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.
  1228   Tue Jul 5 23:06:12 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.5.9+r167Re: changing the default to plain text rather than elcode

John Habermann wrote:
I just shifted our elogs to a new server and in the process upgraded to the latest debian version which is 2.5.9+r1674-1. I am just wondering how to change the default for the text body area from "elcode" to plain text? I can't see anything in the admin configuration syntax guide and the HTML default = 2 option no longer seems to work.


The HTML default option has been replaced by the Default encoding option, with which one can set the default encoding style to plain text (Default encoding = 1).


John Habermann wrote:
Also is there anything in particular that you have to do to get the elcode editor to work. Although the elcode buttons appear highlighting text and clicking on them doesn't actually do anything although it works fine in my browser when using these elog forums. I don't get any errors in mozilla but trying it in IE under cxoffice gives an "error on page" message in the bottom of the browser.


The ELCode editor requires the JavaScript file elcode.js to be present in the scripts directory under your elog root directory. Future installations will handle this correctly.
  1230   Thu Jul 7 02:41:40 2005 Reply Tim Fowlertimfowler1@gmail.comQuestionLinux2.5.9+r167Re: changing the default to plain text rather than elcode

Stefan Ritt wrote:

John Habermann wrote:
I just shifted our elogs to a new server and in the process upgraded to the latest debian version which is 2.5.9+r1674-1. I am just wondering how to change the default for the text body area from "elcode" to plain text? I can't see anything in the admin configuration syntax guide and the HTML default = 2 option no longer seems to work.


The HTML default option has been replaced by the Default encoding option, with which one can set the default encoding style to plain text (Default encoding = 1).


John Habermann wrote:
Also is there anything in particular that you have to do to get the elcode editor to work. Although the elcode buttons appear highlighting text and clicking on them doesn't actually do anything although it works fine in my browser when using these elog forums. I don't get any errors in mozilla but trying it in IE under cxoffice gives an "error on page" message in the bottom of the browser.


The ELCode editor requires the JavaScript file elcode.js to be present in the scripts directory under your elog root directory. Future installations will handle this correctly.


The installation did not include scripts directory. Where can I download the elcode.js file?
  1236   Thu Jul 7 08:38:11 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.5.9+r167Re: changing the default to plain text rather than elcode

Tim Fowler wrote:
The installation did not include scripts directory. Where can I download the elcode.js file?


I said future installations will handle this. This feature is still in beta becaus it's not finished completely. You can get the elcode.js from CVS.

- Stefan
  1241   Thu Jul 7 22:31:40 2005 Reply Tim Fowlertimfowler1@gmail.comQuestionLinux2.5.9+r167Re: changing the default to plain text rather than elcode
I said future installations will handle this. This feature is still in beta becaus it's not finished completely. You can get the elcode.js from CVS.

- Stefan


Thanks Stefan! This is an excellent application.
  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!
  67090   Wed Jul 20 13:50:34 2011 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.8.1-1Re: changing raw style when empty attribute value

Zbigniew Reszela wrote:

Dear all,

I wonder if anyone of you already tried to  change raw style in case of empty attribute value.

In my configuration file I have defined attribute "End date" (without quotation marks) and it's type is datetime.

How should I configure extra style for entries where this attribute doesn't have value.

My tries were:

Style End date = background-color:red

Style End date "" = background-color:red

Style End date " " = background-color:red

Style End date - = background-color:red

But they didn't work.

Any ideas?

This functionality was not implemented. I added it in SVN revision #2420, so it will be contained in the next release.

  67092   Wed Jul 20 17:38:16 2011 Reply Zbigniew Reszelazreszela@cells.esQuestionAll2.8.1-1Re: changing raw style when empty attribute value

Stefan Ritt wrote:

Zbigniew Reszela wrote:

Dear all,

I wonder if anyone of you already tried to  change raw style in case of empty attribute value.

In my configuration file I have defined attribute "End date" (without quotation marks) and it's type is datetime.

How should I configure extra style for entries where this attribute doesn't have value.

My tries were:

Style End date = background-color:red

Style End date "" = background-color:red

Style End date " " = background-color:red

Style End date - = background-color:red

But they didn't work.

Any ideas?

This functionality was not implemented. I added it in SVN revision #2420, so it will be contained in the next release.

Thanks a lot Stefan

Goto page Previous  1, 2, 3 ... 223, 224, 225 ... 799, 800, 801   Next  
ELOG V3.1.5-3fb85fa6