I'll try increasing the list size(s), and will also prepare a simplified config file for you to look at.  Maybe there is a another way to implement what I am trying to achieve?  

In general terms I am trying to give an e-log a "memory" of what has been recorded previously in order to constrain what is permissible to record next.  I do this by starting a log with an initial entry, then alter the config so that users can add records only by duplicating the last record.  The log records the current state of some variables, and allows users to record changes to the state of any of these variables. Conditions are used to constrain the permitted state changes, depending on the current state; conditions are also used, with subst options, to update the current state variables when changes are made.

Specifically, we have "Mate-Demate" logs for connectors to record when connectors are mated and demated.  Previously we just had an attribute for each connector in an assembly with options "Mate", "Demate" and "-" to indicate that either a mate or demate was carried out or that the connector was not touched on this occasion (although others were).  My cunning plan was to ensure that a "Demate" (or no-op) was possible only if the connector is currently mated, and conversely that a "Mate" (or no-op) was possible only if the connector is currently demated.  For each connector (e.g. ConnectorA), there are now two attributes

• "ConnectorA state", to record the current state, and
• "ConnectorA" to record any change.

A new record can be created only by duplicating the last record, thus copying the current state of the connectors, and for each connector the relevant config file entries are like this:

Show Attributes = ConnectorA
Show Attributes Edit = ConnectorA state, ConnectorA
Locked Attributes = ConnectorA state
Preset on duplicate ConnectorA = -
Options ConnectorA state = Mate{1}, Demate{2}
{2} Options ConnectorA = -, Mate{3}
{1} Options ConnectorA = -, Demate{3}
{3} Subst ConnectorA state = $ConnectorA

Maybe some more information will help with the question.  Here's the results of my playing around with URL = /host.domain/subdir in elog.cfg.  Commented out, I can access locally with http://localhost:8080 and tunnelled (1234:host.domain:8080) with http://localhost:1234, with and without Apache (i.e., Apache is bypassed?).  URL = /host.domain/elog in elog.cfg works locally with browser locator localhost:8080 (of course), localhost/elog, and host.domain/elog, but the tunnel directly to 8080 no longer works, nor does http://localhost:4321/elog (even though this ends up showing the same URL on the remote browser as on the local browser) (4321:host.domain:80).  http://localhost:4321 brings up the Apache window.  Every other URL assignment I tried failed both locally and remotely, so, I assume the ssh tunnel directive is wrong, or the browser locator, or maybe still URL = .  Anyway, my question is, what am I doing wrong?

I've just checked that 'wget --no-check-certificate --save-cookies cookie.txt --keep-session-cookies -d "https://elog-gfa.psi.ch/SLS?uname=uuu&upassword=ppp" -O elog.txt'

created a file cookie.txt. The file contains three lines of data if uname and upassword are a valid login, and it is empty (beside of three comment lines) if they are not a valid login (wrong user or wrong password).

Could it be related to the set-up of your particular logbook?

You get a drop-down list if you define several options for an attribut, like

Options Category = Start Up, Start Down, Other

The you can select one of the categories from the drop-down list.

I forgot to mention - this is for searching the logbook.   So would the config file look more like this:

[global]

port = 8080

usr = vulcanstaff

Max content length = 1073741824

Menu commands = New, Edit, Delete, Reply, Find, Last day, Move to, Copy to, Import, Help

RSS Title = $subject, posted by $author on $entry time

RSS Entries = 10

Options Category = Date, Subject, Subtext

Quick filter = Date, Subject, Subtext

Use Lock = 1

Reverse sort = 1

Required Attributes = Author, Subject

I know that this is for searching. But you don't get the point. You have attributes, like Date, Category, Subject. Each attribute can either contain arbitrary text (like the subject), or one of a set of predefined values. So category can be, let's day, "one", "two", "three". You define the possible options of the category with

Options Category = one, two, three

If you then define the quick filter

Quick filter = Category

then you get for the category a drop-down box where you can select "one", "two" or "three". If you do so, elog shows all logbook entries where the category attribute has the selected value.

I hope that this is clearer now. 

Thanks Stefan, I think I understand, and now I see the options definition on the syntax page.  I apologize for taking up your time and thank you for the great software.  I think this is right now:

Options Search = Date, Subject, Subtext

Quick filter = Search

No this is not right. Better read the manual carefully, then come back here again.