Steve Jones wrote: |
Stefan, not a problem. ITMT, any idea how I can manually clear this "lock"? Is it embedded in the logbook itself?
Stefan Ritt wrote: | Sorry about my unusual slow response, but I'm pretty busy these days. I hope I will be able to address this problem in a two weeks from now.
Steve Jones wrote: | Stefan, any ideas on this problem?
Quote: | Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.
SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.
PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset". |
|
|
|
1203
|
Mon Jun 20 04:29:57 2005 |
| Paul Paquette | paquettep@gmail.com | | Windows | | prevent CVS and XML exports |
Hello Again,
I'm being asked to do the impossible to list the Assessing Dept Data but not letting people download the whole database. This way they can lookup the info the Town uses to assess their property. The Town’s Selectmen have stopped paying for the company who hosted the database and the software they used. Now I'm asked to do the same service in house with out funds and without resorces. Hence the question.
Thanks
Paul |
1211
|
Fri Jun 24 20:45:41 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | | Windows | | Re: prevent CVS and XML exports |
Paul Paquette wrote: | I'm being asked to do the impossible to list the Assessing Dept Data but not letting people download the whole database. This way they can lookup the info the Town uses to assess their property. The Town’s Selectmen have stopped paying for the company who hosted the database and the software they used. Now I'm asked to do the same service in house with out funds and without resorces. Hence the question.
Paul |
See elog:1202 |
1592
|
Fri Jan 13 03:21:32 2006 |
| Chris Warner | christopher_warner@dcd.uscourts.gov | Question | Linux | | Problem selecting ports |
I had problems getting elog to run on port 8080 (or many others). I have it installed on Redhat Enterprise Linux rel 4. The only way I was able to get it working was using port 80. I would like to run it on a different port if possible but I'm not sure what is wrong.
Any Ideas |
1613
|
Thu Jan 19 20:50:29 2006 |
| Mark Coudriet | markcoudriet@yahoo.com | Bug report | | 2.6.0 | Re: In version 2.6 the themes do not work right on Windows. |
Stefan Ritt wrote: |
Quote: | The URL is fixed at whichever logbook that is selected (e.g. ELOG 2.5.9-4 is <link rel="stylesheet" type="text/css" href="default.css"> & ELOG 2.6.0-1 is <link rel="stylesheet" type="text/css" href="http://localhost:8080/demo/default.css">). |
So what is your problem? Can't you access http://localhost:8080/demo/default.css ?
If so, you could use an
URL = http://{your host}:8080/
option in your config file, where you replace {your host} with your real host name. |
No, because they would have to be in every logbook instead of coming out of the theme directory.
But I just updated to your new version 2.6.1 & everything is fine now. Thanks for your help!  |
1733
|
Tue Feb 28 12:08:42 2006 |
| Alex H | alex@synergie-inf.com | Info | Windows | 2.6.1-1668 | [SOLVED] Re: MOptions problem ? |
Yop,
I think I found the solution! I was in fact a conditions conflict!
See the attached picture for easiest comprehension.
My list box type's conditions (FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}) conflict with my Equipment's conditions. It seems that the condition ID must be unique across the whole elogd.cfg.
So I have replaced my "Options Type = FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}"
by : "Options Type = FWL1{101}, FWL2{102}, FWL4{103}, VPN1{104}, VPN2{105}, CLIVPN-PROC"
and it works well ! |
Attachment 1: gotcha.gif
|
|
1890
|
Fri Aug 11 21:48:01 2006 |
| Grant Jeffcote | grant@jeffcote.org | Question | Windows | | Conditional E-Mail Attributes |
Stefen, is it possible to change an email option using conditional attributes?
I have a need under certain conditions to send an email in plain text (Encoding type 1) but as type 2 under other conditions, it seems when I do the conditional string is ignored and the global entry is used.
Can all email options be actioned using a conditional string, it only seems to work on some?
Shown here are some of the options that would be nice to set under 'conditions'.
Some appear to already work that way.
{2}Email attributes = xxx, xxy,
{2}Email All = dee@sdf.com, def@sdf.com,
{2}Preset text = This is a test
{2}Email Encoding = 1
{2}Use Email Subject = ELOG-ID $message id - Test Company
{2}Use Email Heading = Test Company Operations Report
{2}Use Email From = admin@sdf.com
{2}Suppress Email to users = 1
{2}Email Format = 27
{2}Suppress Email on edit = 1
{2}Suppress default = 2
{2}Display Email recipients = 1
{2}Omit Email To = 1
Any help would be appreciated. |