Hi,

when I choose the Spanish language, the command Copy To isn't allowed. I have had to change the language file and  change the line:

Copy To = Copiar a

to

Copy To = Copy To

Bye!

That's strange. I just tried (even with Spanish) and it worked for me. Which version of elog do you have installed? Can you send me your elogd.cfg file?

I intend to create a script that updates one of our elog logbooks based on mails it receives. I was hoping to be able to do this using the "elog" command line tool. Adding a new entry works fine, as does "replying" to an existing entry. The only thing I cannot get to work is editing an existing entry. All entries ahve several attributes and I intend not to use the "message" itself. I tried the following (on the machine this elogd is running on):

1. Create a new entry with Attribute1 set to "value":
   

   elog -a 'Attribute1=value' -x -h localhost -l 'LOGBOOK' -p 8080 -u USER PASSWD

   This works - the entry gets created and is displayed properly.
NOTE: I found that this does not work if LOGBOOK has any spaces in it - I would get error messages where the logbook was not found.
 

2. Edit this entry to set a second attribute:

   elog -e 1 -a 'Attribute2=something' -x -h localhost -l 'LOGBOOK' -p 8080 -u USER PASSWD

   The result was: Error transmitting message. Running the same command with -v gives me a whole bunch of text with at the end this message (I've stripped the HTML): "This entry has in meantime been modified by someone else. Submitting it now would overwrite the other modification and is therefore prohibited." However, I know for certain that this entry is not being editied by anyone at that moment, so I'm wondering what I'm doing wrong here...

elog -a 'Attribute1=value' -x -h localhost -l 'LOG\ BOOK' -p 8080 -u USER PASSWD

Message successfully transmitted, ID=12345

 I fixed two things:

• The logbook can now contain a space. Enclose it in double quotes such as elog -l "LOG BOOK" ...
• The error you report comes from the fact that you are the first person using elog submissions together with "use lock=1" in the configuration file. This has never been tested and therefore does not work . So I fixed this by adding a new hidden parameter. If you update to SVN revision 2122, things should work

Concerning your request of editing existing entries by their idea, I agree with Yoshi that you could grab the ID upon the first submission. An alternative is to make a direct search on a logbook. Since this is not implemented in the elog command line tool, you have to use wget for it:

wget "http://localhost:8080/LOGBOOK/?mode=raw&Attribute1=something" -O elog.txt

A problem here is that the username and password are normally transmitted in an encrypted form as cookies by your browser after you logged in. Now you have to convince wget first to log in like

wget "http://localhost:8080/LOGBOOK/?unamee=USER&upassword=PASSWD"--save-cookies cookies.txt

followed by a second call to wget with --load-cookies cookies.txt. I tried that but was not successful since the login procedure above redirects to the elog listing page, and only the cookies set after the redirection were saved in cookies.txt. Maybe you can figure out how to do that. The only way I could get it to work is to supply the encoded password, which I manually obtained from the password file. The URL was then

wget "http://localhost:8080/LOGBOOK/?mode=raw&Attribute1=something&unm=USER&upwd=ENC_PWD" -O elog.txt

Tehe, leave it to us "stupid users" to break your nice little program in new and exiting ways... ;-) But: THANK YOU! Both things are indeed working now - that brings me one step closes to my automated logbook, which is great!

wget "http://localhost:8080/LOGBOOK/?mode=raw&Attribute1=something" -O elog.txt

wget "http://localhost:8080/LOGBOOK/?unamee=USER&upassword=PASSWD"--save-cookies cookies.txt

wget "http://localhost:8080/LOGBOOK/?mode=raw&Attribute1=something&unm=USER&upwd=ENC_PWD" -O elog.txt

I thought about grabbing the ID on first creation. The problem with that is that I really would have to run parallel "databases" - one in elog to keep the information I want plus a second one which maps the elog-IDs to the "real" IDs - and the second one would also have to deal with things like "ID exists", "ID doesn't exist", "ID gets deleted" and so on - just the kind of hassle I want to avoid. But what you suggest with wget will most likely be sufficient. The logbook in question is readable for everyone (only editing/writing requires authentication), so I can search without password hassle. In fact, this will work:

wget -q "http://localhost:8080/LOGBOOK/?mode=raw&Attribute1=something" -O -| grep '\$@MID'|awk '{print $2}'

Et voila, I have an ID. This will generate a bit more traffic than a parallel "DB", but I think it will be less susceptible to errors, as all information is kept within the elog logbook at all times. Thanks again for your help - time to do some scripting! :-)

hello all,

#1 i love ELOG : excellent app! i would like to ask/present a question here -- I have a couple of TYPE's defined as;

       Options Type = Day Shift, Swing Shift, Night Shift
What I'd love to be able to do, is depending on what TYPE was selected during the creation of a NEW ENTRY in the ELOG "shift log" I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected...

for example, if someone chose "Day Shift" that would be listed with a GREEN background, if someone chooses "Swing Shift" that gets a BLUE background, and so forth... I am wondering how one would go about implementing this?

second question... instead of listing the column named TYPE, can I just change it somewhere in the config to "SHIFT" so that in the list view, and even when in the NEW ENTRY form, I'd like it to show "Shift" instead of TYPE --- really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable?

Thanks for the app, I look forward to any reponses! I been editing the CSS, and once done think I'll add it to yr Config Examples, as I don't see many CSS themes there...

-peace-

Style Shift Day = background-color:green
Style Shift Swing = background-color:blue

Attributes = Shift, Shift leader
Options Shift = Day, Swing, ... <and so on>
Options Shift leader = Mike, Edward, John, ... <and so on>

Hello,

Recently upgraded to 2.7.3 and I'm seeing html code filling up the reply window. Before I would just see [quote] and [/quote] around the original entry. Did I miss something in the upgrade? Thanks!

 Probably you did not install the FCKeditor. Just try a reply to this message, and you will see the many formatting icons on top of the page coming from that HTML editor. Without the editor, you will only see the plain HTML. You can switch back however to the old behavior by selecting the ELCode encoding. You can make this permanent with the "Default encoding =0" option.

One of my shifters just managed to make an anonymous logbook entry even though the Author attribute is required.

It turns out that he had two tabs in his browser opened/logged into the Elog.  He logged out in one tab only.   Then he

did some other work on the desktop.  Then he returned to the browser to make a new logbook entry, finding the tab which

still showed the logged in menu, including the link for "New".  The Shifer is on day two, so he did not give any special

notice to seeing Anonymous in the Author field instead of his name.  He did point it out when I came in, and noted that

no warning was given about making an anonymous entry.

I tested the same scenario myself.  One cannot preview an anonymous entry (when Author field is a required attribute).

A warning is given.  However, one can submit the anonymous entry, and no warning is given.

Alan

 What configuration do you use? I tried to reproduce your problem with a "minimal" configuration like

[demo]
Attributes = Author, Subject
Preset Author = $long_name
Locked Attributes = Author

When I log out from the second browser tab and click on "New" on the first browser tab, I am shown the login page, not the new entry page. I guess your "menu commands" and "guest menu commands" allow non-logged in users to issue a "New" command. Try removing that.

Stefan

My Elog running on windows 2003 sp1 is crashing with this error "  Faulting application elogd.exe, version 0.0.0.0, faulting module elogd.exe, version 0.0.0.0, fault address 0x00061330."  the version of elogd.exe is  has a built date of 2/22/2008.  Will upgrading to the latest windows binary resolve this issue?    Thanks!!

 

 I would give it a try!

Hi,

When the WINDOWS binaries with the latest bug fixes will be available on the download page ?

Have a nice day

 Whenever you ask for it 

I made you an elog274-1.exe containing revision 2118.

I get the following error where thumbnails should go: Cannot create thumbnail, please check ImageMagick installation.

I restarted elog and check the log, it does in fact detect ImageMagick and it does have the most recent version. I'm running ubuntu 2.6.24-19-server.  Is there something else I should be checking?

 Try the following:

• Put logfile = elog.log into your elogd.cfg
• Upload an image to get the error
• Examine your elog.log file

You should get something like:

23-Jul-2008 15:10:38 [] Server listening on port 8080 ..
23-Jul-2008 15:10:52 [stefan@127.0.0.1] {demo} SHELL "convert "logbooks\demo\080723_151052_Capture.png" "logbooks\demo\080723_151052_Capture.png.png""

In your logfile. Now try the "convert" command manually under the same account elogd is running. Possible reasons for problems are:

• The "convert" command is not in your path or links to another program. Unfortunately ImageMagick chose a pretty standard name for this program
• The account under which elogd is running does not have write access to the logbook directory
• converts wants to call ghostscript for PDF conversion, but it is not installed
• ...