We have a logbook in which we use two "Status" attributes, both of which are MOptions. What we want to do is have the corresponding line of the list change its colour depending on the combination of those attributes. I have done so successfully using "Style" for a single Options or MOptions or even two Options (using conditionals and a third attribute), but up until now I have no luck with two MOptions. Conditionals do not seem to work with MOptions (the manual only mentions Options and when I tried anyway, it did not work... ) and multiple "Style" statements also do not seem to work. I've tried the following:

MOptions StatusA = Status-A-red, Status-A-orange, Status-A
MOptions StatusB = Status-B-red, Status-B-orange, Status-B

Style StatusA Status-A-red = background-color:red
Style StatusA Status-A-red | Status-A-orange = background-color:red
Style StatusA Status-A-red | Status-A = background-color:red
Style StatusA Status-A-red | Status-A-orange | Status-A = background-color:red
Style StatusA Status-A-orange = background-color:orange
Style StatusA Status-A-orange | Status-A = background-color:orange
Style StatusB Status-B-red = background-color:red
Style StatusB Status-B-red | Status-B-orange = background-color:red
Style StatusB Status-B-red | Status-B = background-color:red
Style StatusB Status-B-red | Status-B-orange | Status-B = background-color:red
Style StatusB Status-B-orange = background-color:orange
Style StatusB Status-B-orange | Status-B = background-color:orange

As far as I can see, the "Style" statement for StatusB only gets evaluated if none of the statements for StatusA matches (i.e. StatusA = Status-A). What I would want to achieve is that any "red" condition in either StatusA or StatusB takes precedence over "orange" and "none" and that "orange" takes precedence over "none".

Is there any solution for this problem short of merging both status attributes into one (which would be very unwieldy, especially, as StatusB is not used at all in some cases)? Any suggestions are most welcome!

Thanks in advance,

Thomas

I have two logbooks running, one for current accounts and one for non-active ones. The idea is to move an entry from one logbook to the other once an account becomes non-active. Both logbooks share some attributes (e.g. the name of the account, its creation date, ...), but both also have some uniqe attributes.

While I was playing with this set-up, I ran into a problem:

1. Move an existing entry from current to non-active.
   • "Type" and "Status" have options. "Created" and "Archived" are in date format.
   • "Created" and "Type" are supposed to be locked in non-active. This works.
   • "Archived" and "Status" are empty, as they do not exist in current. This also works.
   • Depending on the "Type", only certain of the additional attributes are shown on edit. This works as well.
   • I would also like "Status" to have some influence on how certain other attributes are preset and/or shown. This is where the problem starts...
2. Edit the entry in current.
   • As expected, "Created" and "Type" are shown as locked.
   • As soon as I change the selector for "State", the whole edit mask is redrawn - and the date shown in "Created" is deleted.

I've been experimenting with this quite a while and as far as can see the following applies:

• Only date format attributes are affected
• Only locked attributes seem to be deleted completely
• If I have a date attribute that is not locked and I set it partially in the edit mask (e.g. only select the month or enter a year), it is also deleted
• If I have a date attribute that is not locked and I set it completely in the edit mask (i.e. day, month and year), it is not deleted

During the experiments I came up with a stripped down version of the non-active logbook configuration, which does show the bug. It only contains Type, Created, Status, Archived. To make an entry to experiment, you'll have to comment out the "Locked attributes" line, make a new entry (with "Created" date), the uncomment that line.

I hope my description isn't too confusing - please don't hesitate to ask if anything is unclear. I'd be much obliged if you saw a chance to fix this at some point...

Best regards,

Thomas

Hi,

how can i make the author field read only on new postings? It should take the value from $long_name after login and without login there is no way to make new postings.

This is a part of my elogd.cfg

[global]
.......

Logfile = elogd.log
Logging level = 3
Login expiration = 24
Password file = ./passwd
.......

[Informations]
.......

Logout to main = 1
Logbook tabs = 1
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Select, Login, Help


Preset Author = $long_name
Attributes = Author, Subject
Required Attributes = Author, Subject
........

Thanks Brassmann

[global]
.......

Logfile = elogd.log
Logging level = 3
Login expiration = 24
Password file = ./passwd
.......

[Informations]
.......

Logout to main = 1
Logbook tabs = 1
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Select, Login, Help


Preset Author = $long_name
Attributes = Author, Subject
Required Attributes = Author, Subject
........

 All you need is an addition

Locked Attributes = Author

[global]
.......

Logfile = elogd.log
Logging level = 3
Login expiration = 24
Password file = ./passwd
.......

[Informations]
.......

Logout to main = 1
Logbook tabs = 1
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Select, Login, Help


Preset Author = $long_name
Attributes = Author, Subject
Required Attributes = Author, Subject
........

 Thanks, works fine.

Regards Brassmann

[global]
.......

Logfile = elogd.log
Logging level = 3
Login expiration = 24
Password file = ./passwd
.......

[Informations]
.......

Logout to main = 1
Logbook tabs = 1
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Select, Login, Help


Preset Author = $long_name
Attributes = Author, Subject
Required Attributes = Author, Subject
........

 Thanks, works fine.

Regards Brassmann

 Wildcards are not implemented for that purpose. But a "Allow New = admin1, admin2" implicitly denies this command for all other users, I guess that's what you want. There is also the possibility to use "Guest Menu Commands" to allow everybody to read entries, but only logged in users to write and modify them.

I tried it in a global group configuration

[global monitoring]
Allow Edit = admin1, admin2
Allow New = admin1

But I as admin2 am still able to create new entries in the corresponding log books.

Is this configuration only for logbooks?

 I just tried myself with following config:

[global]
port = 8080
password file = passwd
Allow New = joe

[demo1]
Theme = default
Attributes = Author, Subject

and it jus worked fine. When I'm not logged on as "joe", the "New" command even does not appear. If you would have supplied your correct ELOG version, I could have checked if you have an old version. In that case you could upgrade.

Hi,

I've set up my ELOG configuration to display one summary line in the list view. However, a word from the next line creeps in from time to time. You can see this in my logbook - look at the 'Text' column for entries 805, 802 and 800 for instance. The word 'Shift' is from the second line of the entry, but it has been added to the summary text for some reason. Any ideas how I can fix this?

ben

 Your problem comes from the fact that you probably did not enter the HTML text body with the build-in editor, but copy-and-pasted it from somewhere else. ELOG determines the end of a line by looking at the line-feed character (\n), and your HTML text does sometimes not contain this character at the end, but only the HTML paragraph tag (</p>). I added some code in SVN revision 2131 to look also for the HTML tags properly, so if you upgrade to that version, it should be fine for you.

Running on windows server 2003.

Mysteriously from time to time i find ELOG has crashed and i must restart it.

Event log shows:

This has occurred twice so far in the month or less elog has been running.  The platform is stable and i have no other issues or negative events besides incorrect ASP calls here and there.  Thanks.

Faulting application elogd.exe, version 0.0.0.0, faulting module elogd.exe, version 0.0.0.0, fault address 0x0004b9c3.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 Unfortunately this is not enough information for me to conclude anything. You need to be able to reproduce the crash, then tell me exactly how you did it, so that I can reproduce it. Then I have a chance to fix it.

I have a muliple entry field, which is defined by MOptions, which allows you to make multiple selections into one field.

My problem is that when I try to select this option from the Quick filter menu option, it brings back no entries.

When I use the search option this works fine. Any ideas on where I go from here?

Thanks,

Paul

Recently I fixed some issues with MOptions. Please update to version 2.7.5.

 Many thanks, the latest version addresses this problem.

It is possible that the Move to... and Copy to... commands can be configured so that when they operate on a message that is part of a thread, that only that message will be moved, instead of the whole thread?

 This has not been implemented on purpose. Assume you have a thread with

A

    B

       C

So A links to B, B links back to A and so on. If you would move now B into another logbook, A and C would point to an entry which does not exist any more. Furthermore, C may contain some sentences which are a reply to something which has been said in B. So even if the "Move To" mechanism would re-link A to C and C to A, the entry C would maybe make no sense any more if B is missing. That's why you only can move threads as a whole. If you want to move individual messages, don't use replies. You can actually disable the reply command in the configuration file.