*** empty log message ***

SVN revision: 940

doc/config.html

@@ -1622,18 +1622,23 @@ the <i>Edit</i> command). A locked message gets displayed with a little red sign
 that the message is currently edited by someone and should not be touched. This can be
 helpful in installations where several people can edit messages. Without locking, the second
 submission of an edited message overwrites the first submission without notice. Although
-the sign gets displayed, the message can still be edited, but it's the user's response to
-avoid any conflict.<br><br>
+the sign gets displayed, the message can still be edited (the lock can be "stolen"),
+but it's the user's response to avoid any conflict.<br><br>
 
 Since elog cannot determine if someone keeps a message very long for editing or if only the
 browser got closed, the locking can show up even if the message is not kept for editing any more.
-In that case, the message has to be edited again and submitted, to remove the origial lock.
-Alternatively, the admin user can issue the <i>Unlock</i> command.<br><br>
+In that case, the message has to be edited again and submitted, to remove the origial lock.<br><br>
 
 Note that logbooks accessible from the internet usually get scanned by search engines. This
 can lead to situations where the <i>Edit</i> link of each message is "followed" by a bot,
 resulting in all messages being locked. In those cases locking has to be turned off.<br><br>
 
+Since release 2.5.4, some Javascript code has been added to avoid unwanted locks. If someone
+edits an entry, but then goes away from that page or closes the browser without submitting
+the changes, a pop-up window appears asking the user to submit the changed entry. Although
+this works for most browsers in most cases, it could be that Javascript has been turned off
+in a browser, in which case the stale locks still might appear.<br><br>
+
 Default for "Use Lock" is <b>0</b>.<p>
 
 <li><b><code>Prepend on reply = &lt;string&gt;</code></b>

doc/contrib.html

@@ -23,53 +23,10 @@
 &nbsp;[<a class=nav href="download.html">Download</a>]&nbsp;
 </div>
 <p>
-<div class=Sub><i>ELOG Contributions</i></div>
-<hr>
 
-Here are some "<I>contributions</I>" from various ELOG users. In case of questions, please contact
-them directly<p>
-
-<UL>
-
-<LI><h2>Perl script to submit an email to ELOG</h2>
-
-<h3>by <a href="mailto:sak&#64;essc.psu.edu">Sridhar Anandakrishnan</a></h3>
-
-Perl program to split apart an email message and submit each of the mime
-attachments as an attachment to ELOG. The <i>-a</i> command line is fixed for
-now as "subject=subject of the email", so the logbook has to include that.<p>
-
-<a href="../contrib/mailelog.txt">mailelog.txt</a>
-<a href="../contrib/mailelog.pl">mailelog.pl</a>
-<p>
-
-<LI><h2>Perl scripts to convert an ELOG logbook to a MySQL database</h2>
-
-<h3>by <a href="mailto:fhooper&#64;sushisoft.com">Fred Hooper</a></h3>
-
-Perl scripts to help translate logbooks created by ELOG from the native elog
-flat file format to a MySQL database. The elog2sql toolkit consists of two
-scripts. The first script, parsecfg.pl, reads an elogd.cfg, and creates a
-sqlfile that will create a set of db tables corresponding to ELOG logbooks.
-The second script, parselog.pl, takes a set of ELOG logfiles, and creates a
-sql file that will enter the logbook data into the database.<p>
-
-<a href="../contrib/elog2sql.txt">elog2sql.txt</a>
-<a href="../contrib/elog2sql">elog2sql</a>
-<p>
-
-<LI><h2>Javascript for Bookmark link for one-click submission to ELOG</h2>
-
-<h3>by <a href="mailto:fhooper&#64;sushisoft.com">Fred Hooper</a></h3>
-
-Javascript to be used as a browser link that allows a one step copy and paste
-from a web browser into an ELOG logbook.<p>
-
-<a href="../contrib/elogsubmit.txt">elogsubmit.txt</a>
-<a href="../contrib/elogsubmit.js">elogsubmit.js</a>
-<p>
-
-</UL>
+<center>
+<h2>ELOG contributions can now be found in a <a href="http://midas.psi.ch/elogs/Contributions">separate logbook</a></h2>
+</center>
 
 <HR>
 <div class=footer>&nbsp;