I am using eLog ELOG V2.6.1-1681 which has 7 log books under 8 categories. Out of 7 log books, 2 are daily used. It happened that two weeks back. I modified information on two log books which were not used for quite longtime. Hence using CONFIG, I updated these log books, changing text etc. After that eLog in general started giving error. Any time when we click SUBMIT button in any log book, eLog shows page not found. That submit crashes eLog and as a result elogd service stops. Restarting elogd service, eLog operation comes back and the log which I submitted was actualy saved. Difficulty is that this problem is happening with every single submit action. 

I searched forum and learnt that upgrading eLog to newest version 2.7.8 will solve this problem. Upgrade created more problems, I was not able to open any log, authentication was not accepted. I restored that backup and went back to previous version. eLog started working but with submit error.

If any one can help me in fixing this problem

I propose that you get 2.7.8 working. If the authentication fails, try do do password recovery, or recreated the accounts. 

 Thanks for the reply. I found problem with existing version. I opened log book group  without  opening log book details in configuration, that is why at submitting or opening elog was not able to find log book for that group and was getting lost.

Regarding moving to 2.7.8, I want to know that in this new version file location for pwd and log books will remain same or are changed. If changed then I have to change location manually. Also how I can perform password recovery.

Is it possible to create a drop down menu for the last 3 days of log entries. Currently we have the last day, month, 3 month, etc.

Reason being, after a weekend most people would like to view the log entries for the last three days. Can anyone help me out here?

It is a good point, and surprised that this particular number of days was overlooked.

It only needs four lines added into elogd.c to achieve this.  Even with my notorious 
c coding, I did it first time, but as I'm on linux, not a great help for you.  Indeed, 
any other arbitary number of days could be added in, if you have the sources and means 
to recompile.

I think windows versions are only updated on version number, not svn number, so it will 
require a request to the great man himself(*) to produce a new version for windows.

(*)Hint; Stefan likes the occasional beer.


<p>
<table width="98%" align="center" cellspacing="1" style="border:1px solid #486090;">
<tbody>
<tr>
<td cellpadding="3px" style="background-color:#486090; font-weidht:bold; color:white;">Paul O'Shaughnessy
wrote:</td></tr>
<tr>
<td cellpadding="10px" style="background-color:#FFFFB0;"><p>Is it possible to create a drop down menu for the
last 3 days of log entries. Currently we have the last day, month, 3 month, etc.</p>
<p>Reason being, after a weekend most people would like to view the log entries&nbsp;for the last three days.
Can anyone help me out here?</p></td>
</tr>
</tbody>
</table>
</p><p> </p>

> It is a good point, and surprised that this particular number of days was overlooked.
> 
> It only needs four lines added into elogd.c to achieve this.  Even with my notorious 
> c coding, I did it first time, but as I'm on linux, not a great help for you.  Indeed, 
> any other arbitary number of days could be added in, if you have the sources and means 
> to recompile.

David send me his modification and I put it into the main source code, so it will be contained in the next Windows 
version.

> I think windows versions are only updated on version number, not svn number, so it will 
> require a request to the great man himself(*) to produce a new version for windows.
>
> (*)Hint; Stefan likes the occasional beer.

Yepp ;-)

> David send me his modification and I put it into the main source code, so it will be contained in the next Windows 
> version.

I made an interim 2.7.8-3 version which contains the fix and can be downloaded from the web site.

Hi Stefan,

I have noticed a problem when closing multiple log entries i.e entries which have more than 10 threads. I use Select -> Click the box that appears next to the thread I wish to close -> Edit.

As soon as I click on Edit the elogd service crashes and Windows displays an error message window. The only work around has been opening up all the threads and individually changing the "Status" to Closed. 

Forgive me if this issue has been raised before but I have looked throughout the Forum and could not see anyone experiencing the same problem.

Thanks

Cliff

Unfortunately I cannot reproduce your error. In my test set-up it works fine, so it might be related to your configuration. Can you send me your config file, a zip with the needed logbook entries (xxxxxxa.log files), and a recipe what to click exactly in what order.

 This programing have stoped working, I guess after last update.

Elog is running on Solaris.

Ulf Helmersson

Options Type = Journal Article{1}, Proceeding Article{2}, Book chapter{3}, Book{4}, Patent{5}

{1} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Abbrivated journal name, Volume, First page, Year, Elsevier format, AIP/APS format, IOP format

{2} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Conference name, Place, Country, First page, Year, Month.Days, Volume, Elsevier format Proceeding

{3} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Book Title, Editors, Publisher, Place, First page, Year, Elsevier format Book chapter

{4} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Publisher, Place, First page, Year, Elsevier format Book, IOP format Book

{5} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Patent number, Year, First page, Elsevier format Patent

The option

Show Attributes =

has been changed to

Show Attributes Edit =

to distinguish between normal entry display an edit mask. So please adjust your configuration file and everything will be fine again.

Hi,

I have been trying to get the display mode into threaded by default, it does not work on any of my logbooks. I saw related threads in this forum but none gave me a solution (unless the 2.7.8-2282 is available for download).

Here is a simple example which i can not get working.

thanks for your help

FX

The display mode is taken from the configuration option "Display mode = ..." only the very first time a users accesses a logbook. When the user switches to any other mode (summary, full) by clicking on the according menu option, the new mode is stored in a cookie in the browser and overrides the "Display mode = ..." setting. Maybe that is what you see.

Hi again,

I was wondering if one could use a conditional statement on an IOption attribute? Indeed i try to do a visual logbook (a green check for OK result, a red cross for NOK result), unfortunately i cannot refer to the attributes value for conditional test, e.g:

IOptions Status= "Delete-icon.png" {1}, "Check-icon.png"{2}
Icon comment Delete-icon.png = Failed
Icon comment Check-icon.png = OK

{1} Show Attribute Edit = Attribute1, Attribute2

Thread Icon = Status

Attribute1 and 2 do not have any sense if the result was successful,

ELOG interprets the {1} and {2} as being part of the icon name!

thanks again for your help

FX

Conditions won't work for IOption attributes. You need an additional attribute like:

I really appreciate your help and I hope that my questions warrant your time.

What I am trying to accomplish is two totally separate groups of logbooks that share a common logbook.

Three logbooks

Logbook A

Logbook B

Logbook C (just informational, write protected)

Two Groups

Top Group 1 = Logbook A, Logbook C

Top Group 2 = Logbook B, Logbook C

What is happening is everything looks good until you try to enter Logbook C from Group 1. You end up in Logbook C (the right logbook) but you are now in Group 2.

Actual Code:

;Groupings
Top Group Central = Centaur, On-LineHelps
Top Group Good Sam = GSH, On-LineHelps

You cannot put the same logbook into two groups. All you can do is to define two logbooks C1 and C2, and force their data directories to be the same (via the "Subdir = ..." directive), so they will actually look at the same data.

 Stefan, sorry to bother you yet again. but I can not seem to get the "Subdir" to do what I want (user error I am sure). Thanks for any help you can give.

[OnlineHelps]
Write Password = SWNlQ3ViZQ==
;DISPLAY
Theme = default
Display mode = threaded
Mode Commands = 0
List Menu commands = New, Find, Config

Thread display = --------------  $Title  --------------

Comment = On-Line Helps
Attributes = Title
Required Attributes = Title
Page Title = ELOG - $subject
Reverse sort = 1

[OLH.gsh]

Subdir = \\ssoelog\ELOG\logbooks\OnlineHelps
Write Password = SWNlQ3ViZQ==
;DISPLAY
Theme = default
Display mode = threaded
Mode Commands = 0
List Menu commands = New, Find, Config

Thread display = --------------  $Title  --------------

Comment = On-Line Helps
Attributes = Title
Required Attributes = Title
Page Title = ELOG - $subject
Reverse sort = 1

First of all, why do you a reply to a very old message? For each new topic you should start a new thread.

I don't know exactly what goes wrong in your case. Just a few ideas:

• Having a '.' in a logbook name can cause trouble, better remove it
• Having a subdir starting with '\\' might work, but I never tried it, does it work if you use a subdirectory on the same drive just with "Subidr = \elog\..." ?
• There is also the option "Logbook dir = ..." which you might try

 If you have a logbook and you create a new entry, is it possible to put a time limit on that new entry so that edits/replies are only valid for certain amount of time.  I am looking for a way that would allow me to have a user start a new message, but after 8 hours, that message becomes locked and no one can edit or add to the message.  This is for some shift work and we do not want users to go back after their shift and edit the messages.  

Did you consider using the "Restrict edit time" option? It should provide the necessary functionality, as long as you don't want to lock the entry at a fixed absolute time, but really only x hours after creation (also, as you talked about closing the "thread" automatically, there is no option to prevent replies after a certain amount of time).

See the administrator's guide.

What you need is

Restrict edit time = ...

as written in the manual.