ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 199 of 806

Not logged in

Find | Login | Help

Full | Summary | Threaded | Show attachments

6445 Entries

Goto page Previous 1, 2, 3 ... 198, 199, 200 ... 804, 805, 806 Next

Thu Aug 4 20:35:48 2005

Resolution (i think) - Re: Problems with beta 3 (Follow-on to CVS/XML msg 1296)

PJ Meyer wrote:

think I figured it out- had to make explict most of the default settings: resource, logbook, url, theme, css and so on.

so this is done.

I'm not satisfied with this solution, I rather would like to fix the problem at the source. So can you remove the explicit directory settings, then stip down the config file to the bare minimum where the problem happens, then send me this file so that I can reproduced it. Do yo use SSL, stunnel or a proxy?

- Stefan

1372

Thu Aug 4 21:36:21 2005

Re: Creating logbook by copying an existing one crashes elog

Chris Howe wrote:

Trying to create a new logbook from an existing one causes elog to crash.

I (hopefully) fixed that bug. The fix will be included in 2.6.0-beta4.

1373

Thu Aug 4 21:44:53 2005

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

Re: "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.

1375

Thu Aug 4 22:59:12 2005

Re: 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?

1383

Fri Aug 5 10:54:49 2005

Re: "full" only changes color

Kees Bol wrote:

Stefan, I installed V2.6.0-beta3 and there is a (unwanted) difference. The Text field now appears in the summary-view despite the config specifies:

List Display = ID, Logdate, Author, Book, Chapter, Type, Subject

so in my opinion the text-field should not show up here.

If you do not want text display in the summary view, add

Summary lines = 0

into your config file.

Kees Bol wrote:

Another point: there was some discussion about v2.6.0-beta3 being slow.
I have v2.6.0-beta and v2.6.0-beta3 running side by side on the same server and notice also a big difference in speed, beta3 being much slower.

This is still a mystery to me, since on all machines I try the speed is fine. I'm still waiting for some debugging analysis from users which have this problem. If I cannot reproduce it, I cannot fix it.

1385

Fri Aug 5 12:06:47 2005

Re: Top Groups, Show Top Groups, password file and Protect Selection page have nasty interaction

Chris Green wrote:

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");

Thanks, applied.

Chris Green wrote:

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.

I hope I have fixed this problem, at least it works ok here when I tried with your config file.

One note I would like to make however: "Top groups" were invented for having completely separate logbook groups. Before the invention of top groups, one had to run several instances of elogd for different departments for example, where one department should not see the other department's logbooks. But having many departments means having to maintain many elogd daemons. This led to the invention of top groups, so one daemon can serve several independent groups, each having their own [global] section, with probably their own administrator.

In your case however, it would be more applicable not to use top groups, but use nested groups. Like

Group MiniBooNE = Analysis, Miscellaneous
Group Analysis = Charged Current Pi Plus, Neutral Current Coherent Pions
Group Miscellaneous = demo

I presume this is more what you want, and you can avoid some problems which arise from top groups.

Chris Green wrote:

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 have not tested this one, but it could well be that the modification I made also fixes this.

1386

Fri Aug 5 12:37:42 2005

Re: Email subject garbaged when set?

Heiko Scheit wrote:

Well not quite. According to the RFC the encoded word must not be longer than 75 characters! Indeed shorter subjects are displayed by pine, but not longer ones as they do not follow RFC2047.
Below is the quote from the RFC.

You are right Big grin

, thanks for this information, I overlooked it.

Now I split a long subject into separate chunks of encoded words, and my pine is happy. Update in CVS.

Goto page Previous 1, 2, 3 ... 198, 199, 200 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6