Hello,

I have a quick question regarding how to display text using the "Top text" 
feature in the elogd.cfg file.  I've made an entry that looks like the 
following:

Top text = <h1>TEXT TO DISPLAY</h1>

But instead of getting just "TEXT TO DISPLAY" I get something like this:

----begin page ---
/usr/local/elog         "TEXT TO DISPLAY"

...rest of page 

----end page ---

...that is, on the far left at the top of the page in unformatted text 
is "/usr/local/elog/" prepended to the text I want do display. 

I don't know if this is a bug, or (more likely) something misconfigured in 
my setup. But any help that could be provided would be most greatful.

Thanks,

Val   

This was a bug which only occurs under certain conditions, that's why nobody 
has seen it yet. I fixed it, the new version is available under CVS:

http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.275

> This was a bug which only occurs under certain conditions, that's why nobody 
> has seen it yet. I fixed it, the new version is available under CVS:
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.275

Great! 

I'm inclined to wait until you release a new rpm with the changes, as I'm 
likely to mucky things up by trying to upgrade from the cvs archive rather than 
using the rpm mechanics. 

But glad to hear it's fixed.  

By the way, ELOG is a fantastic tool. I'm very thankful for all the effort gone 
into it. I do wish there were standard sql hooks, as I'm a bit fearful of how 
it will scale. But the front-end, which is often most neglected, is well 
thought out.  Thanks so much, Val

I really don't know if anybody already had this problem or i just didn't 
find the solution in the documenttaion: 
 
There is a possibility to sort the log by the value of a attribute as 
well as a flag for reverse sort. anf it's quite easy to build up a 
command line with the sort attribute and value. But this only works from 
a self written command line. 
 
Is there any possibilty to make ELOG soring by default (without a 
command line option) by a other attribute than date? I would use a date 
set by the user manually to sort the log file, even the user clicks on 
the log-name.  
 
or may it be a possibility for a additional feature, like a logbook 
option "Default sort = my own date" and the logbok get sorted by this 
attribute and option by default. 
 
Would be happy about every tip! ThankX! 

This can be easily achieved with the configuration option

Start page = ?sort=<attribute>

or

Start page = ?rsort=<attribute>

where <attribute> is your date.

In your case, you need the URL

http://www.familienhund.ch:8080/Aktuelles+Programm/?sort=Datum+wann

which can be obtained via

Start page = ?sort=Datum+wann

Thank's!!!  :-)) 
 
Great solution. Exactly what I need! 
 
Ueli 
 
> This can be easily achieved with the configuration option 
>  
> Start page = ?sort=<attribute> 
>  
> or 
>  
> Start page = ?rsort=<attribute> 
>  
> where <attribute> is your date. 
>  
> In your case, you need the URL 
>  
> http://www.familienhund.ch:8080/Aktuelles+Programm/?sort=Datum+wann 
>  
> which can be obtained via 
>  
> Start page = ?sort=Datum+wann 
 
 

Maybe consider using the options -W -Wall when compiling elogd.
There are several warning messages.

Thanks, I did so.

So I fixed all compiler generated warnigns except these:

[midas@pc2075 ~/elog]$ gcc -g -O -W -Wall -o elogd src/elogd.c
src/elogd.c: In function `set_cookie':
src/elogd.c:4675: warning: `%y' yields only last 2 digits of year
src/elogd.c: In function `send_file_direct':
src/elogd.c:5483: warning: `%y' yields only last 2 digits of year
src/elogd.c: In function `show_elog_list':
src/elogd.c:11938: warning: `%x' yields only last 2 digits of year in some 
locales
src/elogd.c:11957: warning: `%x' yields only last 2 digits of year in some 
locales
src/elogd.c:11979: warning: `%x' yields only last 2 digits of year in some 
locales
src/elogd.c:11987: warning: `%x' yields only last 2 digits of year in some 
locales
src/elogd.c: In function `ctrlc_handler':
src/elogd.c:15864: warning: empty body in an if-statement
src/elogd.c: In function `hup_handler':
src/elogd.c:15870: warning: empty body in an if-statement

Do you know how to disable these warnings or any other workaround? I would 
like to compile without any remaining warnings.

> So I fixed all compiler generated warnigns except these:
> 
> [midas@pc2075 ~/elog]$ gcc -g -O -W -Wall -o elogd src/elogd.c
> src/elogd.c: In function `set_cookie':
> src/elogd.c:4675: warning: `%y' yields only last 2 digits of year
> src/elogd.c: In function `send_file_direct':
> src/elogd.c:5483: warning: `%y' yields only last 2 digits of year
> src/elogd.c: In function `show_elog_list':
> src/elogd.c:11938: warning: `%x' yields only last 2 digits of year in some 
> locales
> src/elogd.c:11957: warning: `%x' yields only last 2 digits of year in some 
> locales
> src/elogd.c:11979: warning: `%x' yields only last 2 digits of year in some 
> locales
> src/elogd.c:11987: warning: `%x' yields only last 2 digits of year in some 
> locales
> src/elogd.c: In function `ctrlc_handler':
> src/elogd.c:15864: warning: empty body in an if-statement
> src/elogd.c: In function `hup_handler':
> src/elogd.c:15870: warning: empty body in an if-statement
> 
> Do you know how to disable these warnings or any other workaround? I would 
> like to compile without any remaining warnings.


Have a look at the gcc info pages:

$ info gcc "invoking gcc" "warning options"

> Have a look at the gcc info pages:
> 
> $ info gcc "invoking gcc" "warning options"

Sure, I'm not stupid! I looked for ~10 minutes how to turn off the remaining 
warnings, but I could not find it. The code is now correct, like I do want the 
"%y" format specifier in the strftime() function, but the warning is wrong. The 
closest I came to was 

-W -Wall -Wno-format

which removes ther warning in strftime(), but I do want this warning, since it 
helps in many other printf() statements.

> > Have a look at the gcc info pages:
> > 
> > $ info gcc "invoking gcc" "warning options"
> 
> Sure, I'm not stupid! 

  Sorry, didn't mean to offend you.

> I looked for ~10 minutes how to turn off the remaining 
> warnings, but I could not find it. The code is now correct, like I do want the 
> "%y" format specifier in the strftime() function, but the warning is wrong.

  One way to remove the warnings would be to use "%Y" in a separate strftime() call
  and then taking only the last two digits (characters) of that string.

  Something like:
old:
   strftime(str, sizeof(str), "%A, %d-%b-%y %H:%M:%S GMT", gmt);

new:
   strftime(str, sizeof(str), "%A, %d-%b-XX %H:%M:%S GMT", gmt);
   strftime(year, sizeof(year), "%Y", gmt);
   i=strstr(str,"XX"); /* find position of XX */
   if ( i+1 < sizeof(str) ) {
     str[i]  =year[3];
     str[i+1]=year[4];
   } else ...

  Somewhat cumbersome, but should work.  Maybe consider using the four 
  digit year directly, where possible.

  Gruss, Heiko

Somehow elog does not use the -s option (subdir) anymore,
resulting in a 'HTTP/1.1 404 Not Found' error.

For now I am using elog from version 2.3.9 together with elogd v2.5.0,
which seems to work OK.

Oops! I 're-used' the '-s' flag for email suppression, so it was actually 
double used. I changed the email supprssion flag to '-p', so '-s' should 
work again for specifying subdirectories.

Hi,

First off let me say what an excellent program, simple yet powerful...

I've noticed some erratic behaviour when using "quote marks" in header 
fields.  Basically all text to the right of a " disappears.  Try adding an 
entry with quote marks or replying to this post.

Presume this is a bug.

Keep up the good work

Fergus

Like this one ^^^ ???

I'm joking! I fixed the bug and updated the elogd server. Please find the new 
version under CVS.

- Stefan

> Like this one ^^^ ???
> 
> I'm joking! I fixed the bug and updated the elogd server. Please find the new 
> version under CVS.
> 
> - Stefan

Blimey! That was quick!

Many thanks for amending this.  You'll be pleased to hear that my IT Operations  
Team think this is the best thing since sliced bread...its going to replace a 
blizzard of spreadsheets.

Cheers
Fergus

Around line 2240 (in loc()) in elogd.c the following is written, 
which results in an infinite loop, since loc() recursively with
the same argument "Change %s".

   /* special case: "Change %s" */
   if (strstr(orig, "Change ")) {
      sprintf(result, loc("Change %s"), orig + 7);
      return result;
   }

For now I just commented these lines.

This problem has been fixed recently. The new code is

   /* special case: "Change %s" */
   if (strstr(orig, "Change ") && strcmp(orig, "Change %s") != 0) {
      sprintf(result, loc("Change %s"), orig + 7);
      return result;
   }

Alternatively you can get the updated version from CVS.

- Stefan

I have created a javascript to be used as a browser link that allows a one
step cut and paste from a web browser into a elog logbook. 

The intended application is allow a user to do a text selection in a web
browser, then click on a bookmark that automagically pastes the selected
text, the current browser page url, and the current browser page title into
a pre-defined elog logbook.   I do some research where I would like to save
some text from a webpage, but also have a record of where the webpage came
from.  However, you should find that you can extend this script in a varity
of ways for your own application.  

The script is a simple one: it uses javascript in a saved bookmark to get
your selected text, title, and url, and then creates a new browser window
with a elog form, and print the document variables into the form, and then
submits the form to elog.   The key advantage to this approach is that you
can use the "post" command, rather than "get", to submit to the text section
of an elog logbook.  The only way I found now to submit to elog via a
bookmark is using the "get" command, and it doesn't allow entry of the
"text" field, only attribute fields.    

The second major advantage to using POST is that you can submit a much large
quanity of information ; However, some checking on this leads me to believe
that the limit is browser and server depended, so YMMV.  However, a great
discussion on the limits of browsers can be found here: 
http://www.squarefree.com/bookmarklets/browsers.html .

One of the major limits is that IE6.0 browsers have a maxium of 508 bytes
per bookmark - This book runs over 800 bytes, so I suspect tha IE6+ will not
allow it.  I tested the link with Mozilla and Firebird 0.7.

This script will need to edited for you to use with your elog logbook.
The script should be fairly self-explainitory, if you are used to html forms
and have some exposure to javascript.

You will need to modifiy the following fields:

1) in form action = http://<your_domain.com>/elog/<logbook>/?cmd=New
      change the link to point to your specific logbook to be used for entry.

2) the attribute fields need match up with the ones in your logbook.

     The ones listed in the template are Author, Email, Title, and URL.

     If you have fixed fields (like Author and Email), then you can
predefine these fields as shown.  

      I have the page title used as the entry for Title, and the page url is
 use as the URL attribute.

      Finally, I have the text selection used as the entry for the Text field.

      You can add additional fields by creating a new <input ...>  segment
in the script.  For those more clever than me, you can concatinate the
title, url and selection to paste into the Text area as well.  

3) once you have a edited version of the script (make sure you keep it as a
single line), you can then create a new bookmark in your browser, and then
paste the script into the properties->location field (for Mozilla/Firebird)
or the properites->url field (IE).  Give it a good name like "post to elog"

4) once saved, you can then go a web page, select some text, and then go to
your bookmarks and click on the bookmark.  It should then create a new
window in elog with a completed logbook entry.


some notes:

1) again, this may not work on IE6+ browsers due to M$ limitations.

2) You may have to be logged in already to elog for this work - I have not
tested the interaction using a password protected elog

3) You can only post to a single elog logbook - You'll need to have multiple
bookmarks for multiple logbooks.
   

I find this script very nice. Indeed JavaScript can be very powerful to do such 
things. I added some JavaScript support to the elogd server itself. If one opens 
the "New" page like

http://localhost/demo/?cmd=New&js=test.js

then the JavaScript "test.js" (which has to be present in 
themes/default/test.js) gets inserted into the page header and executed. This 
can be used to add custom form validation, which is more powerful than the built 
in checking if required attributes are present.

Then I tried to redo the bookmark script with the new method. A server-side 
script has of course more space than just a bookmark. I started with a bookmark 
like:

javascript:window.open("http://localhost/demo/?cmd=New&js=test.js");

which even works on IE6. The script "test.js" contains:

function a()
{
  var d=opener.document;
  alert("test.js");
  alert(d.location.href);
  alert(d.getSelection());
}

a();

While the first alert() works, the others fail. It seems like the "opener" 
method does not correctly dereference the right window. If anybody has some 
idea, please let me know.

The new version of elogd which supports the "js=" command can be found here:

http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.235

Version 2.5.0 of ELOG has been released yesterday. The main new feature is 
the automatic mirroring of logbooks between different elog servers. 

This is useful if one wants to synchronize logbooks between a desktop PC 
and a laptop, for example. During synchronization, new or modified entries 
on both sides are merged intelligently. Another application is if several 
companies or institutes want to keep a ELOG database locally, but have the 
databases synchronized periodically with each other. Periodic mirroring 
can be set up with a built in cron-like facility. 

Although the synchronization has been tested extensively, I still consider 
this part in beta state. Before using it, one should make a backup of 
existing logbooks. The flag "Mirror simulate" can be used to test the 
mirroring without actually overwriting or deleting anything. If problems 
arise with mirroring, they should be reported to the author.

Localization files have been updated, so if anybody volunteers to update 
or make a new translation, please contact the author.