> > When creating/updating entries in elog, excluding the main text field are 
> > there any limits on the size of the other fields?
> 
> Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
> currently set to 1500 characters. You can try to increase this and recompile,
> but at some point you will produce a stack overflow and elogd will crash. So
> the current length is a compromise.
> 
> - Stefan

Thanks. Thats useful to know.

Paul

Hello,

I try to have two Extendable options : Client and Equipment
so here is the line in my elogd.cfg
Extendable options = Client, Equipment

When I create a new entrie, I have the 2 scroll menus(Client and 
Equipment) and the 2 buttons(Client and Equipment) but i can't create 2 
news entries, i must create one for client, after I submit, I edit one 
more time and add a new equipement. Is there a solution for this?

Thanks a lot and sorry for mistakes or problem of comprehension i'am 
french :)

The reason for the earlier question is that we are trying to use Elog to store 
data in a form we'd need to store more 1500 characters in more than one field.

Is it possible to get around this problem by having more then one main text field 
per record?

thanks

Paul

> > > When creating/updating entries in elog, excluding the main text field are 
> > > there any limits on the size of the other fields?
> > 
> > Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
> > currently set to 1500 characters. You can try to increase this and recompile,
> > but at some point you will produce a stack overflow and elogd will crash. So
> > the current length is a compromise.
> > 
> > - Stefan
> 
> Thanks. Thats useful to know.
> 
> Paul

> 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.

I am currently trying to get some attributes into one line in my logbook, with some others on a line of their own (this is on the single message page) - pretty much like in this forum.
I searched through the forum and the config examples and found elog:571 as well as elog:Config+Examples/4, but I cannot get it to work.

In the forum, the "Subject:" line is on its own line and fills the whole line, which is what I want. In my logbook, the equivalent attribute does stand on its own line, but the 'value' only fills the space of the second column (i.e., if it was in this forum, the 'value' of "Subject" would be the same width as the icon above it and the rest of the line just blank).
As far as I can see, I'm using the "Format <attribute>=1" statements in the same way as in the example - and when I compare the resulting HTML, it also looks the same. I did notice, however, that you use different CSS classes for "Subject" and its value. Hence my question: To get "Subject" and its value to stretch over the full line, is there some fancy CSS footwork involved? I was not able to find the CSS file for this forum among the configuration examples - maybe you could add it?

Thanks in advance!

I fixed this problem in revision 1.586. It will be contained in the next release.

Hi to all,

I've prepared a new Debian package.  This version will probably be the one
which you'll find in Sarge/stable.

There are some invasive changes in this version which call for a serious
test.  In accordance with a suggestion, I've changed the configuration
mechanism.  For details, please read the NEWS.Debian file attached.

Could the Debian users who follow this forum test it and give some feedback?
You can download the package from the following link:

  http://l10n-turkish.alioth.debian.org/debian/elog_2.5.8+r1592-1_i386.deb

Thanks in advance for your participation,

> Hi to all,
> 
> I've prepared a new Debian package.  This version will probably be the one
> which you'll find in Sarge/stable.
> 
> There are some invasive changes in this version which call for a serious
> test.  In accordance with a suggestion, I've changed the configuration
> mechanism.  For details, please read the NEWS.Debian file attached.
> 
> Could the Debian users who follow this forum test it and give some feedback?
> You can download the package from the following link:
> 
>   http://l10n-turkish.alioth.debian.org/debian/elog_2.5.8+r1592-1_i386.deb
> 
> Thanks in advance for your participation,

It seems to work nice to me.
Just another suggestion: I think it would be better to insert a commented out
example for all allowed parameters in the distributed  /etc/default/elog

nice work :-)