Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 455 of 808  Not logged in ELOG logo
IDdown Date Icon Author Author Email Category OS ELOG Version Subject
  66168   Mon Jan 26 14:16:03 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindowsV2.6.3Re: Default value radio button

 

Robert-Jan Schrijvers wrote:

Is it possible to attach a default value for a radio button when submitting a new form/record, for example: 

I now have an item "Confirmed" Yes/No, and I want the "no" option to be selected by default when a new form/record is created.
Does anyone know how to arrange this?

Thanks in advance!

You need something along these lines:

Attributes = ..., Confirmed
Options Confirmed = boolean
Preset Confirmed = 1 
  66167   Mon Jan 26 14:07:02 2009 Question Robert-Jan SchrijversRobert-Jan.Schrijvers@isoft.nlQuestionWindowsV2.6.3Default value radio button

hi there,

Is it possible to attach a default value for a radio button when submitting a new form/record, for example: 
I now have an item "Confirmed" Yes/No, and I want the "no" option to be selected by default when a new form/record is created.
Does anyone know how to arrange this?

Thanks in advance!

RJ

 

  66166   Thu Jan 22 09:30:13 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5-2130Re: Import csv with another date

 

Michael Dannmeyer wrote:

Hello,

i have problems with importing csv files. What i want to do is the following:

Import a list of log entries from a csv file with another date like the actual date

I tried to do this but the only thing which happend was that all the entries have the actual date in elog. Then i created a seperate Date column in the csv file an tried to import this.

It worked but in the default date column i have the import date and in a second date column i have the date from the csv file.

Is there a chance to get the csv column imported in the standard Date field? 

Or is there a possibility to hide/supress the default date field and only display the imported date field?

Thanks

Michael

 

Importing dates from CSV files was not implemented for a good reason: There are dozens of date formats (such as "1/22/09", "Jan 1 2009", "Mon 1 January '09") and it is almost impossible to handle all formats. I changed now the code to catch at least some formats, such as the internal RFC2822 compliant date which is also used internall by elog. An example of this format is "Thu, 22 Jan 2009 09:26:00". This date format will also be used if you export a logbook via a CSV file. Another format I added is "1/22/09". So give a try to the new code (I made an intermediate release for windows V2.7.5-3) and see if it works for you.

  66165   Wed Jan 21 14:31:01 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.7.5Re: Stack error when email notification is active

 

Michael Ambrus wrote:

 

Michael Ambrus wrote:

 

Stefan Ritt wrote:

 

Michael Ambrus wrote:

Stack error is caused when an entry is submitted in a e-mail notification enabled log when a new entry is submitted. This error does not happen on linux (same Elog version, same config file).

Please let me know if there is anything I can do to help.

 

-----------------------------2916890032591
Content-Disposition: form-data; name="attfile"; filename=""
Content-Type: application/octet-stream


-----------------------------2916890032591--

timezone: 0, offset: 0
      6 [main] elogd 2816 _cygtls::handle_exceptions: Error while dumping state
(probably corrupted stack)
Segmentation fault (core dumped)

 

Cygwin is not officially supported. Can you try the Windows binaries? 

 

Sorry, I didn't know there were any (I've not used Elog for years and I think Cygwin was the only way back then). Tried them now and they seem to work. At least no stack error is caused. I'm getting some other error, but I think it's the handshake with the SMTP. I'll validate it's OK until tomorrow.

Windows binaries also solved the issue with the "Top grop" in my other bug rapport.

Thanks for the help!

 

 

 

Unfortunately can't validate this right now. I'm at a remote network trying to get ELOG on my Windows laptop working with e-mail notifications. Either my normal ISP will not allow the SMTP to accept relaying from external networks, or something else is wrong.

The Windows binary is behaving somewhat differently, it seems to behave like earlier versions. I.e. the error message seen on the browser (Error sending Email via "smtp.xxx.xxx") is very limited. Logging (level 6) will not revile much and -v doesn't output any hints either. Assuming the first possible cause, I registered a account at gmail to try see if their SMTP would allow e-mail relaying. Trying with the Windows binary version I seemingly leads to the same result (i.e. I don't see much and the error seen at the browser is the same). However, when trying to run ELOG on a machine at my home network the message is different:

Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. w40sm7583927ugc.6

The message does not surprise me (from previous experience, TLS was what made made postfix complicated to set up too). But what does surprise me is that the messages differ between the two (ELOG V2.7.5 running on a Linux machine and the Windows binary of the same version). Does Linux/Windows versions differ by conditionals in the code or did I somehow get an older Windows binary?

It would also be helpful knowing if ayone has got ELOG working with smtp.gmail.com.

Regards /Michael

 

The Windows Binaries are not recompiled for each minor modification. You should check the SVN revistion (the number which shows up at the very bottom of the page, which is 2153 in this case). It might well be that the Windows Binaries do not yet contain the modification for extended SMTP error report.

Furthermore, TLS is not supported in elogd, only plain SMTP is possible. 

  66164   Wed Jan 21 14:19:45 2009 Reply Michael Ambrusambrmi09@gmail.comBug reportWindows2.7.5Re: Stack error when email notification is active

Michael Ambrus wrote:

Stefan Ritt wrote:

 

Michael Ambrus wrote:

Stack error is caused when an entry is submitted in a e-mail notification enabled log when a new entry is submitted. This error does not happen on linux (same Elog version, same config file).

Please let me know if there is anything I can do to help.

 

-----------------------------2916890032591
Content-Disposition: form-data; name="attfile"; filename=""
Content-Type: application/octet-stream


-----------------------------2916890032591--

timezone: 0, offset: 0
      6 [main] elogd 2816 _cygtls::handle_exceptions: Error while dumping state
(probably corrupted stack)
Segmentation fault (core dumped)

 

Cygwin is not officially supported. Can you try the Windows binaries? 

Sorry, I didn't know there were any (I've not used Elog for years and I think Cygwin was the only way back then). Tried them now and they seem to work. At least no stack error is caused. I'm getting some other error, but I think it's the handshake with the SMTP. I'll validate it's OK until tomorrow.

Windows binaries also solved the issue with the "Top grop" in my other bug rapport.

Thanks for the help!

 

 

Unfortunately can't validate this right now. I'm at a remote network trying to get ELOG on my Windows laptop working with e-mail notifications. Either my normal ISP will not allow the SMTP to accept relaying from external networks, or something else is wrong.

The Windows binary is behaving somewhat differently, it seems to behave like earlier versions. I.e. the error message seen on the browser (Error sending Email via "smtp.xxx.xxx") is very limited. Logging (level 6) will not revile much and -v doesn't output any hints either. Assuming the first possible cause, I registered a account at gmail to try see if their SMTP would allow e-mail relaying. Trying with the Windows binary version I seemingly leads to the same result (i.e. I don't see much and the error seen at the browser is the same). However, when trying to run ELOG on a machine at my home network the message is different:

Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. w40sm7583927ugc.6

The message does not surprise me (from previous experience, TLS was what made made postfix complicated to set up too). But what does surprise me is that the messages differ between the two (ELOG V2.7.5 running on a Linux machine and the Windows binary of the same version). Does Linux/Windows versions differ by conditionals in the code or did I somehow get an older Windows binary?

It would also be helpful knowing if ayone has got ELOG working with smtp.gmail.com.

Regards /Michael

  66163   Wed Jan 21 08:45:25 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.5 2142Re: Elogd crashes with: *** stack smashing detected ***

 

Niklas wrote:

Create a list of elog cookies, and store only these as parameters. Examplef:

int process_http_request(const char *request, int i_conn)

{
...
const char *cookie_list[] = { "upwd", "unm", "elmode", "urem", "wpwd", "apwd", "uname", NULL };
...
...
...
         /* store cookie as parameter */
         for(i=0; cookie_list[i]; i++) {
            if(strcmp(cookie_list[i], str) == 0) {
               setparam(str, cookie);
               break;
            }
         }

...

 

I'm not sure if this works, since your test

i < (int) sizeof(cookie)

still will stop parsing cookies if there is one which is too long. So I added your test plus changed the parsing to:

for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; )

   if (i < (int) sizeof(cookie)-1)

      cookie[i++] = *p++;

   cookie[i] = 0;

 


The modification is in the curren SVN revision (# 2162). So have a look and check that it works.

  66162   Tue Jan 20 17:18:06 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.5-2130Re: SMTP problems - Error sending Email via "smtp.glocalnet.net"

 

Michael Ambrus wrote:

 

Apparently 'MAIL FROM' syntax used by my ISP expects the address to be within <>.

Adding those in the config file fixes the problem:

Use Email From = <user@domain>

Note that the documentation indicates that the brackets should not be there and I'm not sure if this is a bug or not yet. According to this link the brackets should be there but I think to be consistent with other e-mail related attributes in the config file, they should be added by ELOG.

The 'Email' attibute however seems to work fine without the brackests. I.e.

Email All = user@doman

is OK.

I'm not very familiar with SMTP but I was fiddling around with this some time ago setting up a postfix MT. I eventually succeeded with my ISP, but not with gmail's SMTP. Apperently there are differences with the log-in procedure.

 

I added some code to elogd which always places <> around the "MAIL FROM:" in the SMTP communication. So I hope that problem should be solved from now on. Thank you for your detailed analysis and your hints. 

  66161   Tue Jan 20 16:10:22 2009 Reply Michael Ambrusambrmi09@gmail.comBug reportWindows2.7.5Re: Top group causes: Internal error, no valid header!

Michael Ambrus wrote:

Having "Top group" in a config-file for Windows will cause:

 

GET / HTTP/1.1
Host: eudr6j03j:8084
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.0.5) Gecko/20
08120122 Firefox/3.0.5
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: sv-se,sv;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: unm=mambrus; upwd=U2lzc2kx; urem=0
Cache-Control: max-age=0


Internal error, no valid header!

 

Removing "top group" makes elogd.exe work. The error is repeatable and the same config file works on the same version of Elog on Linux. Elog was compiled with Cygwin.

 Windows binaries took care of this problem as with Message ID: 66157.

Problem solved, thanks!

 

ELOG V3.1.5-3fb85fa6