Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 209 of 793  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSup ELOG Version Subject
  1365   Tue Aug 2 10:25:32 2005 Reply Kees Bolkees.bol@wur.nlInfoLinux2.6.0Re: "full" only changes color

Stefan Ritt wrote:

Kees Bol wrote:
I have the strange problem that when changing to "full"-diplaymode the output looks the same as with "summary", only the color is different. The texts don't appear.
Any idea what can cause this behaviour?


Can you send me your elogd.cfg ?

Have you made sure that the entries do contain some text? The behaviour you describe usually happens if you have entries without any text.


Well, I guess that causes it. In the summary-view there is no visible text.
I thougt when choosing the full-view the text would appear along with the other attributes.

My config-file is:
================================================================
Theme = default

Attributes = Author, Type, Subject
Required Attributes = Type, Subject
Preset Author = $long_name
Locked Attributes = Author

Options Type = Question, Configuration, Problem, Info, Other

List Display = ID, Date, Author, Type, Subject
Thread display = $Subject, posted by $Author on $Date

Menu commands = Back, New, Edit, Delete, Reply, Find, Last 10, Change password, Logout, Help

Quick filter = Date, Type
Summary lines = 0

Start page = ?rsort=Date

; alleen eigen messages editen
Restrict edit = 1
======================================================================================
  1370   Thu Aug 4 20:32:56 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux 2.5.9+r16Re: problem with list display attribute

John Habermann wrote:
I not sure if this has been found and fixed as I did find something to do with the list display attribute in the forums but wasn't sure if it was the same thing.

There seems to be a bug with the List Display attribute in that it drops the last attribute of the list. So in my example if I want to display the Subject in my list I have to add a dummy attribute after it otherwise the Subject will not be displayed. The comma after Subject is not enough, but all you have to do is to add 1 letter and then you will see the subject in List view. If you don't all I see is the Date and Author fields and then the Text field in my Summary view in the log book.

List Display = Date,Author,Subject,t

I am running elog 2.5.9+r1674-1 on Debian sarge.


I tried with the current 2.6.0-beta3 and it worked fine. Can you send me your full elogd.cfg in order to reproduce the problem?
  1373   Thu Aug 4 21:44:53 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6Re: Login twice

Carl Shirey wrote:
Yes Here is a copy of the elog.cfg.


I tried with your config file and it worked fine. So can you tell me:

  • At what URL do you access your logbook? Do you just type http://localhost:8080 or anything else
  • Do you use any proxy or stunnel?
  • What is the URL in your browser showing on the first and second login?

You might want to consider to put a
URL = http://<your host>:8080/
into your config file.
  1374   Thu Aug 4 22:35:57 2005 Reply Stefan Rittstefan.ritt@psi.chInfoLinux2.6.0Re: "full" only changes color

Kees Bol wrote:
I thougt when choosing the full-view the text would appear along with the other attributes.


That's how it is supposed to be. I tried your config file, added three entries, and got the behaviour documented in the attached images. To me everything looks fine.
Attachment 1: summary.jpg
summary.jpg
Attachment 2: full.jpg
full.jpg
  1375   Thu Aug 4 22:59:12 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0b3Re: Email subject garbaged when set?

Chris Green wrote:
The email I get has:

Subject:
=?ISO-8859-1?B?W0Jvb05FLUVMT0ddIE5ldyBzdWJtaXNzaW9uIHRvIENoYXJnZWQgQ3Vyc
mVudCBQaSBQbHVzIGZyb20gQ2hyaXMgR3JlZW4=?=

... which isn't particularly illuminating.


This is the BASE64 encoding of the subject. It was discussed here and I implemented it according to RFC2047. All subjects I receive look fine in Outlook and Thunderbird, but not under Pine, which apparently does not implement the RFC correctly. One could of course put a switch into elog to encode it or not. But as soon as you want to send some non-ASCII characters (like the Norwegian as described in the thread mentioned above) you have a problem. Maybe you can configure your email client correctly to interprete the encoded subject?
  1376   Fri Aug 5 01:13:13 2005 Reply Chris Greengreenc@fnal.govQuestionLinux2.6.0b3Re: Email subject garbaged when set?

Stefan Ritt wrote:

Chris Green wrote:
The email I get has:

Subject:
=?ISO-8859-1?B?W0Jvb05FLUVMT0ddIE5ldyBzdWJtaXNzaW9uIHRvIENoYXJnZWQgQ3Vyc
mVudCBQaSBQbHVzIGZyb20gQ2hyaXMgR3JlZW4=?=

... which isn't particularly illuminating.


This is the BASE64 encoding of the subject. It was discussed here and I implemented it according to RFC2047. All subjects I receive look fine in Outlook and Thunderbird, but not under Pine, which apparently does not implement the RFC correctly. One could of course put a switch into elog to encode it or not. But as soon as you want to send some non-ASCII characters (like the Norwegian as described in the thread mentioned above) you have a problem. Maybe you can configure your email client correctly to interprete the encoded subject?


Apparently the pine people think they're implementing it correctly. Indeed the default subject, "[ISO-8859-1] New ELOG entry" appears just fine. The one for membership confirmation, and anything set in Use Email Subject, however, is borked as above. Maybe the pine bug is something that can be worked around with something simple (like spaces after the ISO spec, or something? Some things work just fine, as I said.

Thanks,
Chris.
  1378   Fri Aug 5 02:14:22 2005 Reply Carl Shireycarl.shirey@pw.utc.comQuestionLinux2.6Re: Login twice

Stefan Ritt wrote:

Carl Shirey wrote:
Yes Here is a copy of the elog.cfg.


I tried with your config file and it worked fine. So can you tell me:

  • At what URL do you access your logbook? Do you just type http://localhost:8080 or anything else
  • Do you use any proxy or stunnel?
  • What is the URL in your browser showing on the first and second login?

You might want to consider to put a
URL = http://<your host>:8080/
into your config file.


Thanks
Your questions that you ask me help me out.
What I was doing was typing in the URL was http://pdls:8080 and it took me the pass down log. When I went to login into Elog took me back to the log but the URL read http://pdls.pwfl.com:8080 so when I log in the second time I was to be the edit mode. So I guess I should have typing in the URL http://pdls.pwfl.com:8080.

Thanks again for your help
  1379   Fri Aug 5 02:27:15 2005 Angy Chris Greengreenc@fnal.govBug reportLinux2.6.0-CVSTop Groups, Show Top Groups, password file and Protect Selection page have nasty interaction
Hi,

Just as our ELOG went into production, I tripped over a couple of related (I think) bugs.

First, the easy one: line 21368 of src/elogd.c has a compile warning which looks non-benign. I fixed it in my local copy with:

Index: elogd.c
===================================================================
RCS file: /usr/local/cvsroot/elog/src/elogd.c,v
retrieving revision 1.739
diff -r1.739 elogd.c
21368,21369c21368
< sprintf(str, "?fail=1", user);
< redirect(lbs, str);
---
> redirect(lbs, "?fail=1");

Regardless (ie if I use the original CVS code or the patched version), a hard-to trace problem occurs with my configuration whereby users are denied access after password entry at the logbook selection page (even when details are verifiably correct), and users are dropped through to the next (non-protected) Top Group page. This problem goes away if "Protect Selection Page" is turned off.

A kind of "shadow" of this problem occurs if you create a new logbook from the Change Config File page, whereby after creating the new logbook one is dropped through to the next Top Group's selection page after saving the configuration (and the url has ?fail=1 added to it, althoguh line 21368 above is hardly the only place where this could have occurred).

I think all these things are linked. I'd be grateful if you could review this section of this code for possible causes of these problems. While we can operate for now with non-logged-in users able to see our list of logbooks, that is not something we want for the long term.

Thanks for your help,
Chris.
ELOG V3.1.5-fe60aaf