Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 213 of 806  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  1650   Mon Feb 6 08:27:40 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionOther2.6.1Re: compiling elog 2.6.1 on solaris platform

Angus Au wrote:
ld: fatal: library -lutil: not found


The util library was added recently because of the new shell substitution functionaly, which requires the forkpty() function call. If you know in which library the forkpty is available on solaris, the makefile could be adjusted accordingly. If the forkpty is not available at all, we have to disable the shell substitution under solaris via conditional compilation.
  1651   Mon Feb 6 12:52:09 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportOther2.6.1Re: [261] problem with month selection
> I have several date-fields defined in my logboek. But when I click the icon and select another month the pop-up 
> window get's filled  with the contants of the logboek instead of the date-selection.

Ups, that problem must have been there for quite some time now. I fixed it in the current SVN version.
  1652   Mon Feb 6 12:54:25 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: elog allows me to create user "blahblah "

Dimitrios Tsirigkas wrote:
By the way, it is also possible to create a user that doesn't have a password! Shouldn't that be forbidden?


Well, some people want that!
  1653   Mon Feb 6 12:58:26 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: elog allows me to create user "blahblah "

Dimitrios Tsirigkas wrote:
I noticed that when I register a username that contains whitespaces (eg "boing "), elog allows me to create the user of that name and updates the password file accordingly. It doesn't log me in, but it gives me no error message either. I also found that if I repeat the process it adds yet another entry in the password file, by the same name "boing ". Is that a bug or is there something wrong with my configuration?


Well, I tell you what is wrong: The form says explicitly (name may not contain blanks) and you did not listen Tongue

I can add a simple check if the name contains blanks, but then some people will come up with other strange characters (@#$%), and I'm not sure which of those gives problems. If you test this carefully and tell me which characters to make forbidden, I will happyly add a simple check.
  1656   Mon Feb 6 16:48:17 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionOther2.6.1Re: compiling elog 2.6.1 on solaris platform

Steve Jones wrote:
I have checked and can find no reference within Sun documents regarding the support of the forkpty() function. I have not been following elog development lately -- what is shell substitution supposed to buy us?


See the config manual and look for $shell
  1657   Mon Feb 6 16:53:41 2006 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.1Re: elog allows me to create user "blahblah "

Dimitrios Tsirigkas wrote:
I wouldn't want some imposter to start entering stuff under the username of another user, so it would be nice if I could have some way of forcing them to have a password, even if it's a one-letter password.


Ok, I added an empty password check. If too many people will complain, I will make it a flag.
  1658   Mon Feb 6 17:15:11 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionOther2.6.1Re: sort after find

Willem Koster wrote:
Obviously I would like to be able to sort the result of a find-query.


That worked some time ago, but did not work currently. So I fixed that in the current SVN version.
  1659   Tue Feb 7 12:58:10 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.1-1637Re: Numbered lists get closed by </ul>

T. Ribbrock wrote:
I just ran into the following problem (and was able to reproduce it in the "demo" logbook on this site):

  • Create a new entry
  • Create a numbered list:
    [LIST=1]
    [*] 1st entry
    [*] 2nd entry
    [/LIST]
    
  • In the resulting HTML code, the closing statement of that list translates to </ul> instead of </ol>, causing the list to remain open and all following text to be intented by the list indentation. This gets worse when several such lists are used in one document. I'll include an example below.

Numbered list follows:

  1. one
  2. two
  3. three

This text is indented, as the list was not closed properly.

  1. four
  2. five
  3. six

And now we have double indention...


I can't see any double indention there...

But seriously Wink I fixed that problem and updated this elog server already. It's in SVN revison 1653. The code now correctly chooses the proper </ul> or </ol>. What will not work however are nested lists, like an ordered list inside an unordere list, but that's anyhow very uncommon.
ELOG V3.1.5-3fb85fa6