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.

Howdy and Thank you in advance.

       Can I limit an elog entry mails to only go to my e-mail, my supervisor and the person who is entering the elog entry.  I have the Elog server on Windows XP Pro running version 2.7.8.2282.

Thank you

Paul

That should be possible with the following configuration options:

When replying on a reply, the author is set to the author on the original reply? Othervice it workes great!

part of code:
...
Preset Author = $long_name
Locked Attributes = Author
Subst on reply author = $long_name
...

Just to say that this bug was fixed some time ago - I don't remember when (a senior moment).  
I know because I reported it to Stefan (along with the rest of the universe), as it was appearing 
on this forum when it was running on that particular SVN version. 

If you update to the latest version of elog, all will be fine.

David.
(helping Stefan, since I usually give him such a hard time).

I use: