Re: length of fields, posted by Stefan Ritt on Tue Mar 8 20:28:49 2005
|
> Is it possible to get around this problem by having more then one main text field
> per record?
No, not at the moment. You can increase the 1500 characters by recompiling elogd, but
at some point you will hit the stack limit and elogd will crash. I plan a major
redesign with completely dynamic memory allocation, thus permitting any number of
characters on any attribute. But this will take a couple of months or so. |
|
Re: Non clickable column, posted by Stefan Ritt on Mon Mar 14 21:56:15 2005
|
> I talk about the column contents. In fact on ELOG, we store password so its
> more easyer to click twice on it to select them and after to copy them instead
> of select from right to left the password and to try to copy them. The HMTL
> link gave problem, its more hard to copy data from HTML link than an normal TXT.
> A little hard to explain sorry for my mistakes and explication I'm French :o).
I added a new option "Link display = ...", with which you can restrict the number of
attribues which gets a HTML link. If you put
Link display = ID, Author
then only the ID column and the colum with the Author are shown as HTML links, all
other are shown as simple text.
The new version is under CVS. This option will be included in the next release. |
|
Re: Non clickable column, posted by Alex H on Tue Mar 15 14:11:48 2005
|
> > I talk about the column contents. In fact on ELOG, we store password so its
> > more easyer to click twice on it to select them and after to copy them instead
> > of select from right to left the password and to try to copy them. The HMTL
> > link gave problem, its more hard to copy data from HTML link than an normal TXT.
> > A little hard to explain sorry for my mistakes and explication I'm French :o).
>
> I added a new option "Link display = ...", with which you can restrict the number of
> attribues which gets a HTML link. If you put
>
> Link display = ID, Author
>
> then only the ID column and the colum with the Author are shown as HTML links, all
> other are shown as simple text.
>
> The new version is under CVS. This option will be included in the next release.
Great news :) !
thanks a lot ! |
Can't use the command-line client, posted by Pieter Edelman on Wed Mar 16 20:04:32 2005
|
Hi all,
I'm trying to use the command-line client from linux, but I can't make it
work and that's driving me nuts...
What I want is to reply to a selected message in the logbook, but I
stumble onto two problems:
- There is a read password ("Read Password=..." entry in elogd.cfg)on
the logbook which I cannot bypass from the client. Specifying the switch
-u "" password on the command line has no effect, and neither does
-w password. The error message I get is included at the bottom of this message. If I disable the
read password, I get past the authentication.
- There is a required attribute called "Publiek", and it's defined as
MOptions. Whenever I try to upload, I keep getting the message that it misses this attribute. I
tried the switch -a Publiek=Anders, -a "Publiek=Anders", -a
Publiek_0=Anders, -a "Publiek_0=Anders" -a "Publiek_1=Onbekend,
-a Publiek=1 on the beginning, end, and middle of the command, but
the results are the same. Both "Anders" and "Onbekend" are in the MOptions
list (including capitals).
For completeness, here's (one variety) of my command line:
elog -a "Publiek=1" -h localhost -p 8181 -l Artikelen -v -r 80
The obvious question is if anybody knows what I'm doing wrong. Any help
is greatly appreciated.
Pieter
Authentication error:
Successfully connected to host localhost,
port 8181
Request sent to host:
GET /Artikelen/80?cmd=download HTTP/1.0
Host: pde.dyndns.org
User-Agent: ELOG
Cookie: upwd=bWFOZGFyaWpO;
Response received:
HTTP/1.1 401 Authorization Required
Server: ELOG HTTP 2.5.7-1
WWW-Authenticate: Basic realm="Artikelen"
Connection: close
Content-Type: text/html
<HTML><HEAD>
<TITLE>401 Authorization Required</TITLE>
</HEAD><BODY>
<H1>Authorization Required</H1>
This server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.
</BODY></HTML>
Error transmitting message
Missing attribute error
Successfully connected to host localhost, port 8181
Request sent to host:
POST /Artikelen/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------75ABFDB1E
CB47273B853CE0
Host: pde.dyndns.org
User-Agent: ELOG
Content-Length: 3651
Content sent to host.
Response received:
HTTP/1.1 200 Document follows
Server: ELOG HTTP 2.5.7-1
Content-Type: text/html;charset=ISO-8859-1
Connection: Keep-Alive
Keep-Alive: timeout=60, max=10
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><title>ELOG error</title>
<link rel="stylesheet" type="text/css" href="default.css">
<link rel="shortcut icon" href="favicon.ico">
<link rel="icon" href="favicon.png" type="image/png">
</head>
<body><center>
<table class="dlgframe" width="50%" cellpadding=1 cellspacing=0<tr><td
class="er
rormsg"><i>Error: Attribute <b>Publiek</b> not
supplied.</i><p>
Please go back and enter the <b>Publiek</b> field.
</td></tr>
<tr><td class="errormsg">Please use your browser's back button to go back
</td></tr>
</table>
</center></body></html>
Error: Missing required attribute "Publiek"
|
|
Re: Can't use the command-line client, posted by Stefan Ritt on Wed Mar 16 22:14:19 2005
|
> There is a read password ("Read Password=..." entry in elogd.cfg) on
> the logbook which I cannot bypass from the client.
This is correct. The elog utility works with write passwords and user level access
(specifying a password file), but not with read passwords, that's not implemented. Use a
password file and you should be fine.
> There is a required attribute called "Publiek", and it's defined as
> MOptions. Whenever I try to upload, I keep getting the message that
> it misses this attribute.
Your problem is that you try to combine a MOptions with a "-r <n>" (reply-to) option. I
have never tried that and found there is a problem. I changed the way MOptions are
submitted. Instead of using <name>_0, <name>_1 etc, you can now do a
-a "<attrib>=<value1> | <value2>"
This also solves the problem with the "-r" option. You have to upgrade elogd.c from CVS. |
Re: Can't use the command-line client, posted by Pieter Edelman on Thu Mar 17 09:56:21 2005
|
This solved the problems, thanks for the fast response!
On a side note, one would expect that when "Fixed Attributes Edit" or "Fixed Attributes
Reply" is set, the attributes in this list shouldn't be supplied with the command line client.
Anyway, my problem is solved. Thanks for the great product.
Pieter. |
|
Re: Can't use the command-line client, posted by Stefan Ritt on Thu Mar 17 10:02:45 2005
|
> On a side note, one would expect that when "Fixed Attributes Edit" or "Fixed Attributes
> Reply" is set, the attributes in this list shouldn't be supplied with the command line client.
Well, don't shoot yourself in the foot! The communication between elog and elogd is limited. elog
more or less submits "blindly" whatever you give it on the command line. If "Fixed Attributes
Edit/Reply" is set in the configuration, this only affects the web page with the entry form, so
these attributes are not shown as edit boxes. They are not checked during submission by elogd. Now
to get the same functionality with elog, elog whould have to retrieve the full entry form, analyze
the HTML code, find out which attributes have edit boxes and which ones not. So that's a lot of
work. Since most people use elog in scripts, they set it up once and forever correctly. There are
actually a few people which even want the functionality that elog can change attributes which are
normally fixed.
- Stefan |
|
Re: Can't use the command-line client, posted by Pieter Edelman on Thu Mar 17 23:06:54 2005
|
Okidokie. May I then humbly suggest to mention this in the documentation of the elog command client? |
|