Re: How to configure eLog to send an e-mail notification when new logbook entry time is reached?, posted by Stefan Ritt on Wed Mar 25 14:21:31 2009
|
| Tero Suominen wrote: |
|
Hello!
First I would like to thank you for making such a good free software available:). Then right back into the busness. I have a question to developers. I used the following Options to get the logbook entry which defines the licences expiration date (See the attachement). Now I would like to ask on how to configure eLog to send an e-mail notification when this date is reached?
Attributes = Licence Expiration date
Type Licence Expiration date = date
Date format = %A, %B %d, %Y
BR,
Tero Suominen
|
That's not possible with ELOG, which is meant as an electronic logbook. You need a calendar application for that. |
|
Re: How to configure eLog to send an e-mail notification when new logbook entry time is reached?, posted by Tero Suominen on Wed Mar 25 14:35:23 2009
|
| Stefan Ritt wrote: |
|
| Tero Suominen wrote: |
|
Hello!
First I would like to thank you for making such a good free software available:). Then right back into the busness. I have a question to developers. I used the following Options to get the logbook entry which defines the licences expiration date (See the attachement). Now I would like to ask on how to configure eLog to send an e-mail notification when this date is reached?
Attributes = Licence Expiration date
Type Licence Expiration date = date
Date format = %A, %B %d, %Y
BR,
Tero Suominen
|
That's not possible with ELOG, which is meant as an electronic logbook. You need a calendar application for that.
|
Hi! Thanks for the quick response. Do you have any suggestions on which calendar applications I should start looking for for this purpose?
Thanks,
Tero |
Email notifications not working properly, posted by Stefan Ritt on Thu Mar 26 17:30:23 2009
|
I just found out that email notifications only worked for the first 50 users of this forum. So if you registered only recently, you might not have received any notification. This was a bug inside elogd which I hope to have fixed now (this entry notification will show...). If you get the first notification and do not want this, log in to the ELOG Forum, click on "Config" and remove the checkmarks from the logbooks you do not want to get notifications. |
Specifying the size of am image attachment, posted by Val Schmidt on Mon Apr 6 20:46:42 2009
|
Hello,
I'm curious, is it possible to specify (perhaps by default) the rendered size of an attached image. For example, I'd like all images uploaded to be scaled to 100% of the browser window size so a large image is not most off the screen. What I want is to specify the width="100" attribute of the <img /> tag, but it's not clear 1) how do to this for an attachment and 2) if it might be possible to do this in the config file for all img attachments.
Thanks,
Val |
|
Re: Specifying the size of am image attachment, posted by Stefan Ritt on Wed Apr 8 12:25:07 2009
|
| Val Schmidt wrote: |
|
I'm curious, is it possible to specify (perhaps by default) the rendered size of an attached image. For example, I'd like all images uploaded to be scaled to 100% of the browser window size so a large image is not most off the screen. What I want is to specify the width="100" attribute of the <img /> tag, but it's not clear 1) how do to this for an attachment and 2) if it might be possible to do this in the config file for all img attachments.
|
When you use the ImageMagick package, attached images are scaled to a predefined size using the option "Thumbnail size = ...". See the documentation for that option for details. |
|
Re: How to configure eLog to send an e-mail notification when new logbook entry time is reached?, posted by W.Koster on Thu Apr 9 09:54:39 2009
|
| Tero Suominen wrote: |
|
Hi! Thanks for the quick response. Do you have any suggestions on which calendar applications I should start looking for for this purpose?
Thanks,
Tero
|
You could write a shell script, run it through cron and send mail from that. (even in windows I assume)
|
Long cookie content is not handled properly., posted by Simon Patton on Tue Apr 14 22:51:15 2009
|
I discovered the infinite loop in 2.7.5 which can happen when a cookie's content is longer that the cookie array
designed to hold it. I also note that this issue has been addressed in 2.7.6, but the solution does not appear
to be correct and it can end up completely confusing the cookie extraction.
In 2.7.5 the code was:
for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; )
if (i < (int) sizeof(cookie)-1)
cookie[i++] = *p++;
While in 2.7.6 is became:
for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n';)
if (i < (int) sizeof(cookie) - 1)
cookie[i++] = *p++;
else
break;
This leaves 'p' pointing to the middle of the cookie's content and I can not see that this is corrected in the loop (sorry if I've missed that).
The solution I used to patch 2.7.5 was the following:
for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; ++p)
if (i < (int) sizeof(cookie)-1)
cookie[i++] = *p;
which simply truncates the contents of the cookie (which is assumed not to be an elogd cookie) but leaves 'p' in the right place to extract the next one. |
|
Re: Long cookie content is not handled properly., posted by Stefan Ritt on Wed Apr 15 09:26:37 2009
|
| Simon Patton wrote: | I discovered the infinite loop in 2.7.5 which can happen when a cookie's content is longer that the cookie array
designed to hold it. I also note that this issue has been addressed in 2.7.6, but the solution does not appear
to be correct and it can end up completely confusing the cookie extraction.
In 2.7.5 the code was:
for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; )
if (i < (int) sizeof(cookie)-1)
cookie[i++] = *p++;
While in 2.7.6 is became:
for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n';)
if (i < (int) sizeof(cookie) - 1)
cookie[i++] = *p++;
else
break;
This leaves 'p' pointing to the middle of the cookie's content and I can not see that this is corrected in the loop (sorry if I've missed that).
The solution I used to patch 2.7.5 was the following:
for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; ++p)
if (i < (int) sizeof(cookie)-1)
cookie[i++] = *p;
which simply truncates the contents of the cookie (which is assumed not to be an elogd cookie) but leaves 'p' in the right place to extract the next one. |
You're absolutely right about that. I incorporated your patch into revision #2192. |