> > Correct Way prior to 2.3.8
> > 
> > http://192.168.0.1:99/Provisioning%20Request/35
> > 
> > Broken way with new version
> > 
> > http://192.168.0.1:99/Provisioning Request/35
> 
> Exactly this problem has been fixed between 2.3.7 and 2.3.8, so can it be 
> that you mixed up these two versions? To be precise, the fix happend in 
> Revision 1.113 from 2003/06/04 08:17:35. So are you sure that you use a 
> version of elogd after that modification? I tried to reproduce your 
problem 
> with the official 2.3.8 version, but I got the correct result.

Im using the plain RPM from 2.3.8, i uninstalled the 2.3.7 RPM before this 
upgrade, the only thing I kept was my own stylesheets and the config file.

One thing I just noticed is that if you dont have the URL statement set 
under global properties, some machines quote the hostname of the machine at 
which point this breaks the link. if you define the URL to the IP address 
the problem goes away.

However even without the URL setting undefined, it works for some people 
but not for others, I tried from 2 seperate machines and got 2 lots of 
results, so I suspect it might be DNS related somewhere along the lines.

> Im using the plain RPM from 2.3.8, i uninstalled the 2.3.7 RPM before this 
> upgrade, the only thing I kept was my own stylesheets and the config file.
> 
> One thing I just noticed is that if you dont have the URL statement set 
> under global properties, some machines quote the hostname of the machine at 
> which point this breaks the link. if you define the URL to the IP address 
> the problem goes away.
> 
> However even without the URL setting undefined, it works for some people 
> but not for others, I tried from 2 seperate machines and got 2 lots of 
> results, so I suspect it might be DNS related somewhere along the lines.

The only place I can see this problem could arise from is the "Referer:" 
statement in the HTTP header. This is sent by the browser to elogd, so if the 
included URL contains a blank, this could cause the problem in case no "URL" 
statement is present in elogd.cfg. Can you please run "elogd -v" to see the 
communication betwen elogd and your browser and check this? Maybe it depends 
from the browser, or even from the history of previous accesses. If you 
confirm that the "Referer:" statement contains blanks, I can put in a fix.

> Is there a way to configure elog so users that have their email notification
> on only get notified for updates to logs they have access to? I've looked
> all through the documentation and I can't seem to find a way to do this.

I guess you have a global password file and use "login user" statements for 
your logbooks. I have added some code which does per default not send any 
email to people who are not in the "login user" list, in case this list is 
present. New code under CVS. Please give it a try and let me know if it works 
for you.

- STefan

> I suppose that the advice to increase Mac OS X's default stacksize limit
> might make a fine entry in the FAQ or README file.

I added a note in the installation instructions. 
(http://midas.psi.ch/elog/adminguide.html)

- Stefan

I implemented your request. The syntax is:

Format <attribute> = <flags>,<css_class_name>,<css_class_value>,<width>,<size>

<flags>
  Sum of following values:
    1: Display attribute in same line as previous attribute
    2: Display radio buttons or check boxes in separate lines (if applicable)

<css_class_name>,<css_class_value> 
  Cascading Style Sheet class names used for cells containing attribute name
  or value, respectively. The classes must be defined in the style sheet file 
  (usually themes/default/default.css)

<width>> 
  Width of the text entry field in characters

<size> 
  Maximum number of characters allowed. 

Default is "0, attribname, attribvalue, 80, 500". Trailing parameters can be 
ommitted, so specifying for example only the flags is possible.

In order to have several attributes in one line, each line is now a separate 
table. This requires adjustment of the CSS class "attribname". Best you use 
the current default stylesheet (http://midas.psi.ch/elogdemo/default.css).

You can compare the two different approaches (one attribute per line/multiple 
attributes per line) in this forum and the "archive" logbook. The "subject" 
field in this forum also uses a different style class.

Note that if you upgrade to the current CVS version 
(http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.129), you also 
have to change following options in your elogd.cfg:

- The style sheet must contain the new class "attribhead"
- "Email message body" has been replaces by "Email format"
- "Filtered browsing" is now off by default
- Locking (during editing of messages) is disabled by default, and enabled 
by "Use lock = 1"

Very interesting, indeed!
Thank you very much for the implementation. I believe this is a big step ahead 
in terms of ELOG screen formating (and therefore easier/more ergonomic 
dataentry/reading).

We will test your modifications as soon as you make a new release.

Tomas


> I implemented your request. The syntax is:
> 
> Format <attribute> = <flags>,<css_class_name>,<css_class_value>,<width>,<size>
> 
> <flags>
>   Sum of following values:
>     1: Display attribute in same line as previous attribute
>     2: Display radio buttons or check boxes in separate lines (if applicable)
> 
> <css_class_name>,<css_class_value> 
>   Cascading Style Sheet class names used for cells containing attribute name
>   or value, respectively. The classes must be defined in the style sheet file 
>   (usually themes/default/default.css)
> 
> <width>> 
>   Width of the text entry field in characters
> 
> <size> 
>   Maximum number of characters allowed. 
> 
> Default is "0, attribname, attribvalue, 80, 500". Trailing parameters can be 
> ommitted, so specifying for example only the flags is possible.
> 
> In order to have several attributes in one line, each line is now a separate 
> table. This requires adjustment of the CSS class "attribname". Best you use 
> the current default stylesheet (http://midas.psi.ch/elogdemo/default.css).
> 
> You can compare the two different approaches (one attribute per line/multiple 
> attributes per line) in this forum and the "archive" logbook. The "subject" 
> field in this forum also uses a different style class.
> 
> Note that if you upgrade to the current CVS version 
> (http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.129), you also 
> have to change following options in your elogd.cfg:
> 
> - The style sheet must contain the new class "attribhead"
> - "Email message body" has been replaces by "Email format"
> - "Filtered browsing" is now off by default
> - Locking (during editing of messages) is disabled by default, and enabled 
> by "Use lock = 1"

> In the current source which ive compiled and am using on our elog system, 
> the feature that you put in for me that says "Entry is currently being 
> edited by Joe Bloggs on 192.168.0.10" has vanished.
> 
> It removes existing locks from before updating the binary but doesnt but 
> new ones on.
> 
> Is this something that was removed intentionally or by accident ?

No, but there is now a flag "Use Lock = 0 | 1" which is zero by default, 
since not all people want this feature. So put a "Use Locl = 1" and you 
should be fine gain.

Excellent thanks