Re: Bottom text = <file> not displayed in every screen?, posted by Stefan Ritt on Thu Jul 24 15:10:14 2003
|
> I tried to add a file with the "Bottom text = <file>" option.
>
> Although one would suggest that the bottom text file is included in every
> page, I only saw the file appear in the page that appears when you issue
> the "cmd=Edit" command.
That's really weired. The file is displayed at the bottom of single messages,
and the message list, but NOT at the form, which you reach with the "Edit"
command. So all I can suggest ist the following:
- Hit the reload button on your browser each time you change that file, to
make sure the browser does not display a page from its cache
- The HTML file is *included* in the normal page, so it should not contain
<HTML> or <BODY> tags. Start with a simple file containing something like
<center>Test</center>
and see what you get.
- Make sure the file is in the elog "resource" directory, which gets
displayed if you start elogd with the "-v" flag.
Let me know if any of this helped. |
not proper HTML, posted by Heiko Scheit on Thu Jul 31 16:02:41 2003
|
I just upgraded from 2.3.5 to 2.3.9.
There are some errors in the generated HTML. Most of the time
the browser renders everything correctly but sometimes not. Please
check especially (http://validator.w3.org/):
- http://midas.psi.ch/elogdemo/Database/7
There are too many <table> tags before the attribute list:
'Type', 'Operating system',... This should be just one table and
not each row a separate table. Also the first <table> tag lies
outside a <td> tag of the enclosing table.
- http://midas.psi.ch/elogdemo/forum/ |
|
Re: not proper HTML, posted by Stefan Ritt on Mon Sep 8 11:32:42 2003
|
> There are some errors in the generated HTML. Most of the time
> the browser renders everything correctly but sometimes not. Please
> check especially (http://validator.w3.org/):
I did so and fixed several errors. Now the W3 validator doesn't complain any
more. New version under CVS. |
|
Elogd.exe Crashes When There are too Many Replies to Replies..., posted by Christopher Jones on Sun Oct 12 08:37:00 2003
|
Hi,
We have been using Elog successfully as a shiftlog book for over a month
now, but I recently ran into an annoying bug, I think.
We had a thread that was created and was being replied to over several
days. We first replied to the original thread and then each subsequent
reply was a reply of the previous reply. When the thread reached above 13
of these, the elogd.exe would crash everytime a user attempted to select
the logbook that contained the enormous thread.
I found the only workaround was to manually delete the offending entry
from the log file and to instruct my users to not reply to replies unless
absolutely necessary. I have been able to replicate this error across the
rest of my logbooks as well. If there is any more information you may
need, please feel free to contact me.
Thanks,
Chris Jones |
|
Re: Elogd.exe Crashes When There are too Many Replies to Replies..., posted by Stefan Ritt on Sun Oct 26 17:04:59 2003
|
> We have been using Elog successfully as a shiftlog book for over a month
> now, but I recently ran into an annoying bug, I think.
> We had a thread that was created and was being replied to over several
> days. We first replied to the original thread and then each subsequent
> reply was a reply of the previous reply. When the thread reached above 13
> of these, the elogd.exe would crash everytime a user attempted to select
> the logbook that contained the enormous thread.
> I found the only workaround was to manually delete the offending entry
> from the log file and to instruct my users to not reply to replies unless
> absolutely necessary. I have been able to replicate this error across the
> rest of my logbooks as well. If there is any more information you may
> need, please feel free to contact me.
Sorry my late reply, I was pretty busy these days...
I tried to reporduce your problem, but without success. Have a look at
http://midas.psi.ch/elogdemo/Linux/32
where I replied 20 times producing a very long thread without any problem. So
can you reproduce your problem? I suspect that there was some other problem,
since the number of replies is internally not limited in any way. If you
again get into a situation where elodg.exe crashes on the *DISPLAY* of some
message, you can send me the offending file xxxxxxa.log directly by email and
I can analyze it. Only if I can reproduce a problem, I can fix it.
- Stefan |
|
Re: Elogd.exe Crashes When There are too Many Replies to Replies..., posted by Stefan Ritt on Tue Nov 11 13:49:50 2003
|
I found a stack overflow if there are too many replies. This has been fixed in
the current CVS verson of elogd.c and will be incorporated into the next release. |
elog.exe , posted by Etienne Van Caillie on Wed Nov 12 07:52:45 2003
|
impossible to create the moptions with
-a Type#0="%D1%"
-a Itel#0="%zItel%"
the variable are set to
set D1=Tel
set zItel=Tel.gif
other standard option work fine
does anybody has good experience with elog.exe command ?
elog -h 'my site elo' -p 83 -l 'my logbook' -a Phone="%2" -a Contact="%3 %
4" -a Type#0="%D1%" -a Cat="%5" -a Itel#0="%zItel%" "%6 %7 %8 %9"
----------------------------- here are the config in elog
[titiPHONE]
Comment = PhoneList
Find menu text = menu/titiphone_top.html
Data dir = prive_Etienne/PhoneList
Guest Menu commands = Help
Find Guest Menu Commands = Help
Attributes = Phone, Itel, Dossier, Ext_direct, Societe, Contact, Cat,Type,
Prive, Email, Adress, City, Relation, By
Quick filter = Itel,Type,Dossier,Date,Prive
Roptions Prive = no,CD,EC,MD,NB,TR,TV,AH,NW,JW,Manon
IOptions Itel = Tel.gif, TelDirect.gif, Fax.gif, Gsm.gif, Tel2.gif,
TelHome.gif,TelFax.gif,TelHelp.gif
ROptions Type = Tel,TelDirect,Fax,Gsm,Tel2,Home,Combine,TelHelp
Preset Itel = Tel.gif
Preset Type = Tel
Preset Prive = no
Preset Email =
Display mode = Summary
Thread Icon = Itel
Thread display = $Phone,$Contact,$Dossier,$Societe($Type/$prive) |
|
Re: elog.exe , posted by Stefan Ritt on Wed Nov 19 09:06:11 2003
|
> impossible to create the moptions with
>
> -a Type#0="%D1%"
> -a Itel#0="%zItel%"
>
> the variable are set to
> set D1=Tel
> set zItel=Tel.gif
>
> other standard option work fine
Sure it works. But in your elogd.cfg, you have ROptions, not MOptions! I
changed this to
...
IOptions Itel = Tel.gif, TelDirect.gif, Fax.gif, Gsm.gif, Tel2.gif,
TelHome.gif,TelFax.gif,TelHelp.gif
MOptions Type = Tel,TelDirect,Fax,Gsm,Tel2,Home,Combine,TelHelp
...
Then I added a batch file elog_submit.bat with following contents:
elog -h 'my site elo' -p 83 -l 'my logbook' -a Phone=%1 -a Contact="%2 %3" -a
Type#0="%TYPE% -a Cat="%4" -a Itel#0="%ITEL%" %5 %6 %7
Then I made a
set TYPE=Tel
set ITEL=Tel.gif
and a
elog_submit 123 a b CAT Test Message
ans all worked fine. Please change your ROptions to MOptions and try again. |
|