diff --git a/doc/faq.html b/doc/faq.html index e66d6286..435e6821 100755 --- a/doc/faq.html +++ b/doc/faq.html @@ -43,12 +43,14 @@ where one can enter messages but not change them afterwards.
One can use the Start page option for that. The entry:
-
No. The idea behind ELOG is that it is a simple to use, simple to install application.
Many people use ELOG under Windows, and they even don't know what MySQL means. Other people like
@@ -73,7 +75,7 @@ into a MySQL database. One is available at
http://midas.psi.ch/elogdemo/Forum/387.
-
No. The ELOG daemon was designed as a standalone server and it will stay like that in the future.
The reason for that is that
- By default, no password is used in ELOG. This can be useful for public directories etc. that
anybody should be able to read. To add password security, read the documentation under Note that passwords are transferred over the network in plain text and therefore not secure. If this
is a problem, a secure network connection should be used.
-
Use the URL:
@@ -106,7 +108,7 @@ This executes the "Last" command using a filter with <attribute>=&l
Note the "l" before the second attribute, as in "lAuthor=1".
-
In an old version of the FAQ it has been stated here that one has to use two logbooks pointing to
the same data directory. From Version 2.0.6 on, this can be accomplished much easier by the usage
@@ -131,14 +133,14 @@ Self register = 1
in the configuration file. New users can then create their own accounts.
-
You can have several logbooks point to the same password file. So if you change a user or
password in that file, it becomes automatically available in all logbooks which use that file.
-
There is a simple trick. You use the "Start page" option in the
-
New commands can be added for example with the
@@ -59,7 +61,7 @@ all logbooks, the above statements can be placed in the option.
To display all messages from last week and month of with "category = info", one can put
@@ -171,7 +173,7 @@ Note that the parameters [global]
elogd should not rely on any other software. This is for
@@ -83,7 +85,7 @@ therefore becomes much simpler. To run elogd in parallel to
port 80, use Apache as a proxy, following the instruction on the installation page
("Running elogd under Apache").elogd file
to redirect the start page to something else. Here are some examples:
@@ -154,7 +156,7 @@ to redirect the start page to something else. Here are some examples:
The various URLs can be copied from the browser's address bar when doint various things there.
"Bottom text = bottom.html""last=7&Category=Info" applies a fi
how to make these filters by looking at the URL in your browser when you submit a find
command with certain options.
-
This works with the option Menu commands. By default, the menu commands
@@ -184,7 +186,7 @@ statement into :
This prohibits the execution of the commands "Edit" and "Delete".
elogd.cfg
-
There are two ways:
@@ -215,7 +217,7 @@ each line. One can then edit the message and submit it. In the threaded message one sees then the different revisions as a message thread.
-
Usually, the current date/time is recorded when you add a new entry. It might be, however, that one wants to enter "old" entries, or some entries with a date in the future (like a @@ -238,13 +240,35 @@ and day. This is necessary since sorting is done only lexically. Please note tha List Display was renamed recently. Prior to version 2.3.10, it was called Display Search. -
This can happen if you change the login policy, for example move the Password file = entry
in the configuration file from a logbook section to the [global] section or back. In that case some old cookies
could be stored in your browser, which confuse the system. Please delete your cookies in the browser to resolve
this problem. Read your browser documentation on how to do that.
+
+This is a typical request of a bug-tracking set-up. Someone enters a request, opening a new +thread. The expert(s) reply to the the request, and after a while, the request gets satisfied +or the problem gets fixed. If an attribute like "status", having the options "open" and "fixed" +could get changed for the whole thread, on could very easily search for all "open" problems.
+ +Since this functionality is not implemented, an alternative strategy is recommended: Implement +two (or more) logbooks. The first logbook has open issues, the second one has fixed ones. When +an entry changes state, it simply has to be copied to the second logbook. This can be done +by defining the menu command "move" in the config file, like:
+
+
+Menu commands = Back, New, Edit, Delete, Reply, Find, Move to, Config, Help
+
+ +Note the additional Move to. This solution is even more elegant than having +attributes changed in whole threads, since one has two separate logbooks, and can treat +the second one more like an archive, make separate back-ups, or deleting some entries +after some time, while keeping the open issues untouched. +