Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 128 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  1357   Thu Jul 28 09:46:40 2005 Reply Kees Bolkees.bol@wur.nlQuestionLinux2.57-1Re: attribute of type "datetime" sorted incorrectly

Stefan Ritt wrote:

Kees Bol wrote:
What goes wrong here?


The wrong sorting is a mystery to me. I redid what you have, and entered exactly the same entries, and got following:



As you can see, the sorting is quite different. What happens if you reload the page, what if you restart elogd?

As for the missing validity check for the date field, all what was missing was the year check. I added that.


Stefan, I think it has something to do with version 2.57-1. Yesterday evening I installed V2.60 and there was a big difference. All entries of Logdate were changed in 1-jan-70 and when entering/editing an entry I now get the calendar and clock. So everything, including sorting, looks good now.

Thanks
  1359   Thu Jul 28 17:11:32 2005 Question Carl Shireycarl.shirey@pw.utc.comQuestionLinux2.6Login twice
Where I work we started to use Elog for our shift carry over log, everyone seems to likes it.
I do have one problem for some reason we have to login twice in order to submit a new entree in
the log. I do have a guest account setup so when we click logon the logon page pops up and you
type in username and password and enter. Then main page pops up and you are still in the guest mode.
Click on logon again and enter everything again and this you get in the edit mode.
I hope you can me with this.
  1360   Sat Jul 30 14:36:08 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6Re: Login twice

Carl Shirey wrote:
Where I work we started to use Elog for our shift carry over log, everyone seems to likes it.
I do have one problem for some reason we have to login twice in order to submit a new entree in
the log. I do have a guest account setup so when we click logon the logon page pops up and you
type in username and password and enter. Then main page pops up and you are still in the guest mode.
Click on logon again and enter everything again and this you get in the edit mode.
I hope you can me with this.


Can you send me your elogd.cfg?
  1361   Mon Aug 1 06:14:41 2005 Agree Dinesh Bapatdinesh.bapat@gmail.comQuestion  Re: Summary page

Thank you very much.


Stefan Ritt wrote:

Dinesh Bapat wrote:
But "Summary" page of my e-log continues to display additional column "Text". Kindly advise how to hide this last column.


Summary lines = 0


Dinesh Bapat wrote:
Also, is it possible to assign % width for each of these columns (ID, Author, Type, When, Subject)


Yes, via the Cascading Style Sheets, but only for the single display page. First put a

Format Author = 0, author_name, author_value

then put into your default.css following sections:
.author_name {
  width:10%;
  text-align:right;
  font-size:14pt;
  background-color:#AAAAFF;
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1px solid white;
  padding:3px;
}

.author_value {
  width:10%;
  font-size:14pt;
  border:1px solid #308000;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#BBCCBB;
  padding:3px;
}

Here you can then play with the width, font-size etc. I use this for example for the large subject dispaly in this forum.

On the list display however, the column width is determined by the browser, which tries to optimally arrange the colums for best readability.
  1363   Mon Aug 1 23:41:06 2005 Reply Carl Shireycarl.shirey@pw.utc.comQuestionLinux2.6Re: Login twice

Stefan Ritt wrote:

Carl Shirey wrote:
Where I work we started to use Elog for our shift carry over log, everyone seems to likes it.
I do have one problem for some reason we have to login twice in order to submit a new entree in
the log. I do have a guest account setup so when we click logon the logon page pops up and you
type in username and password and enter. Then main page pops up and you are still in the guest mode.
Click on logon again and enter everything again and this you get in the edit mode.
I hope you can me with this.


Can you send me your elogd.cfg?


Yes Here is a copy of the elog.cfg.

Thanks for your help
  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.
  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.
ELOG V3.1.5-3fb85fa6