Any reason why when I click "Reply" to a previous submission that the body is full of HTML code?

See below:

<p>
<table width="98%" align="center" cellspacing="1" style="border:1px solid #486090;">
<tbody>
<tr>
<td cellpadding="3px" style="background-color:#486090; font-weidht:bold; color:white;">Hal Proctor wrote:</td></tr>
<tr>
<td cellpadding="10px" style="background-color:#FFFFB0;"><p>
<table width="98%" align="center" cellspacing="1" style="border:1px solid #486090;">
<tbody>
<tr>
<td cellpadding="3px" style="background-color:#486090; font-weidht:bold; color:white;">Quote:</td></tr>
<tr>
<td cellpadding="10px" style="background-color:#FFFFB0;">removed the thing and the other thing....added this and that!</td>
</tr>
</tbody>
</table>
</p><p> </p>
testing reply</td>
</tr>
</tbody>
 

Here is my logbook config:

[Logbook]
Theme = default
Comment = Maintenance Logbook
Attributes = Author, Type, Category, Subject, Shift
Options Type = Repair, Routine, Preventative, Other
Options Category = Emergency, General, Change-Over, Other
Options Shift = 1, 2, 3
Extendable Options = Category
Required Attributes = Author, Type
Page Title = Maint Log - $subject
Reverse sort = 1
Preset Author = $long_name
Preset on reply Author = $long_name
Locked Attributes = Author
Quick filter = Date, Type, Category

I don't see any mistake in the configuration file. Did you switch the "Encoding" from HTML to plain? (Radio buttons at the bottom just below the text window). Is there a problem with your FCKEditor? Do you see the formatting menu bar? 

 I do not get the formatting menu with HTML.  I switched to plain and code still exists.  The only formatting menu I get is when I choose ELCode.   I have no problem with this forum seeing the formatting menu with HTML (although it does take some time to load). 

 Tested it in Chrome and acts the same as IE8 (just much slower)

 It's version issue!!   2.92 does not utilize FCKeditor correctly.  Backed off one version and it works fine!  2.91 is GOOD!

Actually I can confirm a similar issue with 2.9.2:

when I create a new entry with the default "HTML" encoding and then swap to "plain", the text area is cluttered with HTML code (see attachment new_entry.txt)

I did notice it, but I did not pay much attention to it. But I agree is should be fixed. But in my case it could be related to a firefox add-on "It's all text" that uses java script to modify the HTML code.

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

Andreas

Hi all,

I'm absolutely new with ELOG and have only basic programming skills...

I'd like to use ELOG, so I have installed it in my computer to start playing with it (I installed version 2.7.0-1953 because with the latest one I got an error with the elogd.cfg file). I've been able to open the Demo logbook but wasn't able to submit a new entry into it. I get the following error:

"HTML encoding not allowed"

Could you please explain me how I could solve this problem?

I thank you in advance for your help.

Version 2.7.0 is very old and has knows problem. Better go with the current version and fix the problem with the elogd.cfg file. 

Hello,

We use ELOG for many years and enjoy it's functions every day!

Lately, we see errors whenever we add an entry in elog: 554 MailTransferAgentServer ESMTP not accepting messages

We see this from various ELOG servers. Other (non ELOG) servers using the same MailTransferAgentServer do not heve this error.

We are able to send mail messages from the ELOG machines manually via TELNET. So, from a functional point of view, all works well.

We had this error in the past and found out that the cause of this error lies in (network) time-outs.

Questions:
1) Has anyone seen this error before?
2) Is it possible to increase the timeout value used by ELOG?
3) Are the emails that could not be sent stored in a queue/resent later or are they lost?
4) is there a fix?

Any replies are highly appreciated!

T I A !
 

Just my 2 cent: did you try to reproduce the problem with the latest ELOG version 2.9.2?

Kind Regards
Andreas

> Just my 2 cent: did you try to reproduce the problem with the latest ELOG version 2.9.2?

Hi Andreas,

Thank you very much for your reply. Thsi problem occurs also with the latest ELOG version 2.9.2

It would be nice if the timeout value(s) can be edited via the elogd.cfg file. Maybe this can be added in a new 
version.

Best regards,
Ron

Could you run elogd interactively with the "-v" flag to log the communication between elogd and the ESMTP server and send me the traffic log? 

Hello Stefan,

Thanks you for entering this thread !

Fortunately, we were able to solve the problem. A reboot of the DNS server used by the MTA (Mail Transfer Agent Server) to check the from and to address did the trick.

This server now responds within the timeout period in ELOG.

It still would be handy if you could add a parameter to the config file that allows us to fiddle with the timeout value. The DNS server used by the MTA has to deal with heavy load.

Best regards,
Ron

Hi,

Is it possible to have a default filtered view in E-log?

Lets say we have a record with status finished on one attribute.

Is it possible to have a default list view that just shows records with this status?

Sure. Lets assume you have a "Status" attribute, which can be "open" and "finished", then you need

Options Status = open, finished
Quick Filter = Status
Start page = ?Status=open 

The quick filter gives you a drop-down box where you can switch quickly between "open" and "finished", while the "Start page" automatically filters for "open".

 OK, Thanks!
Is it possible to use Start Page with more than one parameter?
For instance if I want to filter on two filter options at the same time, like Status= Open and Status=Ongoing

Start page = ?Status=Open|Ongoing

 Thanks a lot!
I love this program, there is no end of the possibilities.

/UlfO

I'm using Kerberos and SSL and experience problems with individual setting of "Login user =" for different logbooks.
Sometimes (not every time, but most times) the server crashes under the following condition:
When I login at one logbook and then change to a logbook, that has a restricted "Login user" list with my login
name not in it. It created the following GDB output:

Program received signal SIGSEGV, Segmentation fault.
show_elog_list (lbs=0x916b768, past_n=0, last_n=0, page_n=0, default_page=1, info=0x0) at src/elogd.c:19793
19793         message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;

Expected behaviour would be to show me the login page with the error message:
"you don't have access to this logbook".
This message is never shown for the attached configuration file.
If I remove the "Guest" commands for logbook "TestB" then elogd behaves properly.

For the moment I've just disabled "Login user" settings.

Regards
Andreas

Forget the previous post:
I cannot reproduce the problem with the latest version of elogd (2.9.2-2475).

How can I skip the need for an email address when registering and logging in? Our IT dept will not give an email address to each guy I want on the log.

I never thought that someone will not have an email address. One basic feature of ELOG is its automatic notification if there is a new entry, and that only works over email. It's like social networks, you cannot register for Facebook if you don't have an email address.

So if you absolutely want to omit this, just give a fake email address, like nobody@no.where. ELOG just checks if there is a "@" and a "." somewhere. 

 Word of warning about fake email addresses - if your system suddenly does start to send out messages to them, you'll start getting otherwise mysterious email messages back about being unable to deliver and other such comments.  I speak from experience - although in my case the puzzle was finding what was generating the messages in the first place (not elog, another program as it happened).

I suggest you also include

Suppress default = 3

in your configuration file, which also stops them being generated in the first place. 

Although I was unaware (or had totally forgotten) that there was a 'Suppress email button' as mentioned in the documentation.

 Our IT dept is very strict. I'll have to see if I can get email out to a web based email service like yahoo. But they will not give each of my mechanics an email account here.

Thanks

Looking at some of the questions here this seems too newbie to even ask.

I want to set up a log book for my mechanics. I want them to each have a password to log in and enter what they do each day.

When I try to set up a password file it takes all the info, then when I hit save it says "server has been reset" and it will not log in. I have to remove the password = and restart the server.

[global]
port = 8080


[TFB]
Password file = <tfbpass>


Theme = default
Comment = TFB ENGINEERING
Attributes = Mechanic, Type of entry, Status, Subject
Attributes = Author, Status
Options Status = Completed, Incomplete, Notification only
Cell Style Status Completed  = background-color:green
Cell Style Status Incomplete  = background-color:red
Cell Style Status Notification only  = background-color:yellow



Options Mechanic= Jeff K, Arnaldo M, Bob L, Nathan P
Options Type of entry = Break Down, PM Repair, Building, FYI, Other
Options Status = Completed, Incomplete, Notification only, Other
Extendable Options = Category, Status,
Required Attributes = Mechanic, Type of entry, Category, Status,
Page Title = TFB Engineering - $subject
Reverse sort = 1
Quick filter = Date, Mechanic

 

 never mind. I figured it out I left the <  > in the password = line

Yes I do feel stupid.

I'm running elog 2.9.2 on a Red Hat 6.3 server. This installation has been running for some time on a Solaris server, and was recently moved to the RHEL server.

When a user tries to upload a .bmp attachment, the upload never completes, eventually timing out with a proxy error. At that point, the elogd process stops responding to requests and needs to be restarted. Nothing is in the log file other than a "Listening" message when elogd starts up. Png and pdf attachments seem to work fine. I was able to convert an image from .bmp to .png and upload, but that's not practical for my user.

ImageMagick 6.5.4-7 is installed on the server. Everything else seems to be working normally.

Is this a known problem, or have I missed something that needs to be installed on the RHEL server?

When I saw this problem come in, I was reminded of problems I have of elog crashing.  So I tried attaching a .bmp file to an entry.  In my case it did not crash, but it did not run ImageMagick either - it just gave a link as it it were a zip or tar file - that is to say no .png image had been generated and shown.   As I've never attached a .bmp file before, I don't know whether elog allows for them to be processed and a thumbnail made, a quick look in the documentation didn't enlighten me, but then I didn't look for that long either.  (I'm running 2.9.2 svn 2475, under Slackware 13 which is a version post some image processing issues I reported to Stefan - might that explain why in my case?). 

I have found that sometimes elog will crash, but effectively after it has done the action - so if it crashes when asked to move files from one logbook to another, you find the entries have been moved.  In my case, I believe the crashes are due to memory issues, nothing I can state for certain.

It would possibly help Stefan and Andreas if you can tell whether the .bmp file appears in the relivent logbook directory (usually a subdirectory of ....../logbooks) - it will have been renamed as yymmdd_hhmmss_{filename}.bmp - except, of course, the date and time will be showing not these symbols - and if the entry with which you have tried to attach this .bmp file been written - using a text viewer on the file yymmdda.log (obviously the day will be today, i.e. the one just updated as you tried the entry.   I have come across orphan attachment files in directories in my time, possibly from when elog crashed part way through an action.

(If I am stating the obvious, apologies, I don't know your level of experience with elog or linux, so trying to cover all possible levels)

 Thanks for the info, David.

I do not see any *.bmp files in the logbook directory when this happens. The hang happens when the "Upload" button is hit, so there is no logbook entry yet either.

 Hi David,

Which svn version of elog are you running - what does it say at the very bottom of the page (this forum says ELOG V2.9.0-2435); there *is* and issue about loading files and thumbnails with svn 2473, but it may also be in one or two prior to that (I found it with 2473, anyway).  Also, is elog running (taking CPU time) and not responding to anything after you try this (and you have to kill the daemon and restart), or crashing out at that point? I've had both behaviours at one time or another, for reasons I now understand, not related (I think) to this one, but the more evidence, the better chance that someone will find the problem.

David.

 I'm running ELOG V2.9.2-2455. 

The elogd process continues to run, but no longer responds to requests.If, for example, I open a new browser tab and try to load the logbook, I eventually get a timeout. There is no ImageMagick "convert" process running.

2455 is before the image handling issue came about, so it's nothing to do with those changes.

I see Andreas also finds that ImageMagick is apparently not invoked by elog to make a thumbnail of a .bmp file.  I tested it with a 5MB and a 0.5MB .bmp file this morning, so I don't really think it's the size of the file that is causing the problem - or that is my first guess, anyway.   But I suppose it is worth asking, what is the size of the .bmp file(s) you are trying to attach?  Just a thought, there is a parameter in the Global section of the elog.cfg - "Max Content Length".  I forget the default, I had to increase it when I wanted to attach a huge pdf file, wonder if that might be the issue (I had an error message come up with the pdf file, I wonder...)

The elog daemon can get stuck running like mad and not responding to anything.  One example I know is if you erase an elog entry (e.g. delete one file in the logbook directory, I'm not talking about using elog's own delete facility) the indexing of the entries is broken, and elog cannot handle that, it just gets stuck, consuming loads of CPU time doing I don't know what. 

I've got to go and do something in real life now, but I may get a chance to 'play' later, see if I hit any point that the experts can then work through

 Hi David,

I've just tested it on my server running ELOG V2.9.0-2414, Scientific Linux 5.7 (RHEL 5.?) with ImageMagick 6.2.8: the attachment is uploaded but no preview is generated. No problem with the server.

What was the behaviour of your Solaris system? Did it upload? Did it create a preview?

BMP files are - in my experience - often very large. Could it be a file size problem? Did you try with a small BMP image?

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

Andreas Luedeke wrote:

David Wallis wrote: I'm running elog 2.9.2 on a Red Hat 6.3 server. This installation has been running for some time on a Solaris server, and was recently moved to the RHEL server. When a user tries to upload a .bmp attachment, the upload never completes, eventually timing out with a proxy error. At that point, the elogd process stops responding to requests and needs to be restarted. Nothing is in the log file other than a "Listening" message when elogd starts up. Png and pdf attachments seem to work fine. I was able to convert an image from .bmp to .png and upload, but that's not practical for my user. ImageMagick 6.5.4-7 is installed on the server. Everything else seems to be working normally. Is this a known problem, or have I missed something that needs to be installed on the RHEL server?  Hi David, I've just tested it on my server running ELOG V2.9.0-2414, Scientific Linux 5.7 (RHEL 5.?) with ImageMagick 6.2.8: the attachment is uploaded but no preview is generated. No problem with the server. What was the behaviour of your Solaris system? Did it upload? Did it create a preview? BMP files are - in my experience - often very large. Could it be a file size problem? Did you try with a small BMP image? Kind Regards Andreas   Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English

 Hi Andreas,

Bmp attachments worked fine on the Solaris server. Was running 2.9.2 with ImageMagick 5.5.7.

I don't think it's a file size issue, the image I'm testing with is only about 3 MB.