ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1900
|
Tue Aug 15 13:10:30 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Author in duplicate message |
Silvia Borghi wrote: | Preset on Duplicate Author = $long_name |
This was not implemented so far, but is a good idea. So I put it into SVN revision 1713. You either get the SVN update or wait for the next release of ELOG. |
1901
|
Tue Aug 15 13:25:00 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.2 | Re: Cannot get email to work at all, configuation problem? |
Checker Anderson wrote: | Okay, I got it working but I had to change the authentication method of my mail server to Pop before SMTP. I do not know why the username/password doesn't work - it does work with Outlook Express. I would rather use the username/password method, but atleast things are working now. |
That's really strange, since elog does not do any pop at all. So "pop before SMTP" won't help. The elogd message log in the previous message seems truncated to me, you should get something like
Email from stefan.ritt@psi.ch to stefan.ritt@psi.ch, SMTP host mail.psi.ch:
220 MAILSEND02.psi.ch mailsend02vs01 Tue, 15 Aug 2006 13:22:24 +0200
HELO pc4534.psi.ch
250 MAILSEND02.psi.ch Hello [129.129.228.115]
MAIL FROM: stefan.ritt@psi.ch
250 2.1.0 stefan.ritt@psi.ch....Sender OK
RCPT TO: <stefan.ritt@psi.ch>
250 2.1.5 stefan.ritt@psi.ch
DATA
354 Start mail input; end with <CRLF>.<CRLF>
Date: Tue, 15 Aug 2006 13:22:23 +0200
To: stefan.ritt@psi.ch,
From: Stefan Ritt <stefan.ritt@psi.ch>
User-Agent: Elog Version 2.6.2
Subject: Updated ELOG entry
X-Elog-URL: http://localhost:8080/demo/7
X-Elog-submit-type: web|elog
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
...
In your case there should even be more than that due to the authentication (our sever does not use username authentification). Maybe you have an error there in the authentication. |
1902
|
Tue Aug 15 13:44:45 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | | Re: Conditional E-Mail Attributes | Conditional attributes have been made working in email notifications sometime in version 2.6.0. You might have to upgrade to the recent version, but then it should work. |
1904
|
Fri Aug 18 15:31:53 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | | Re: Conditional E-Mail Attributes | If I try that little configuration file:
[global]
port = 8080
password file = passwd
smtp host = your.smpt.host
[demo]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject, Email Type
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Options Email Type = plain{1}, html{2}
{1}Email encoding = 1
{2}Email encoding = 2
then the email encoding changes from plain to HTML depending on the conditional attribute Email Type. Maybe you misunderstood the concept of conditional attributes. In the above config the attribute Email Type determines the condition {1} or {2}, which leads then to different values of the email encoding. But it's important to have the line
Options Email Type = plain{1}, html{2}
in order to set a condition. |
1906
|
Sat Aug 19 18:45:22 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | | Re: Conditional E-Mail Attributes |
Grant Jeffcote wrote: |
Stefan Ritt wrote: | If I try that little configuration file:
[global]
port = 8080
password file = passwd
smtp host = your.smpt.host
[demo]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject, Email Type
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Options Email Type = plain{1}, html{2}
{1}Email encoding = 1
{2}Email encoding = 2
then the email encoding changes from plain to HTML depending on the conditional attribute Email Type. Maybe you misunderstood the concept of conditional attributes. In the above config the attribute Email Type determines the condition {1} or {2}, which leads then to different values of the email encoding. But it's important to have the line
Options Email Type = plain{1}, html{2}
in order to set a condition. |
I use conditional attributes to select the fields I would like displayed on a form or page.
I understand how they work but wish to set the Email Encoding automatically depending on which item they choose from a drop down list (ie. which form they are using)
For example, if they choose 'Fred Bloggs' from the conditional drop down attribute 'Name' it will set the page so that only 'Fred Bloggs' required attributes are viewable. I wish to send this page in Plain text when submitted.
If 'Fred Jones' is chosen then only attributes applicable to 'Fred Jones' are shown. When he submits his entry then I need the email to be sent in HTML.
The email encoding option would have to be set under either Fred Bloggs{1} or Fred Jones{2} conditions.
Attributes = Name,
Options Name = Fred Bloggs{1}, Fred Jones{2}
{1}Email encoding = 1
{1}Email All = sed@frd.fg
{2}Email encoding = 2
{2}Email All = sdf@fgd.hg
I can get options like 'Email All = sed@frd.fg' to change to another email address when used as above but not Email formatting.
I have all the other conditional attributes working fine otherwise but would really like to be able to add this option.
Thanks for your help. |
Can you please try the above configuration example, and can you please tell me exactly which version of elog you are using? If I try that example with ELOG V2.6.2-1714, it works fine (it DOES change the email encoding). |
1931
|
Mon Sep 11 16:32:52 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.2-1714 | Re: Auto-refresh ELog display |
Alan Stone wrote: | We have multiple LCDs at a console, and usually one is dedicated to displaying a browser
with the local ELog. Meanwhile, others are making entries from another machine. If
no one clicks on refresh, the ELog display becomes stale. Is there a method to have
the ELog reload every X minutes?
Thanks, Alan |
The JavaScript is one possibility as Steve mentioned correctly. Another possibility is to use the RSS feed capability of ELOG. Use any RSS reader, and it will notify you immediately if there is a new entry in ELOG. Have a look at http://midas.psi.ch/elog/config.html and search for RSS on how to configure this. |
1932
|
Mon Sep 11 17:25:54 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6 | Re: Unsubscribe from logbooks |
Chris Warner wrote: | Is there a way for user to unsubscribe from a logbook? Can a user delete their own account? |
Yes. Yes.
Just click on "Config", and you will see a page where you can unsubscribe from each logbook and a button to remove your account. |
1934
|
Mon Sep 18 15:21:56 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.6.2-1714 | Re: Why are Preset fields blanked out? |
Steve Jones wrote: | The snippet of code below sets an attribute to a date depending on the selection. Problem is, if attribute ApprovedDate was previously set, selecting any other value for CRStatus will blank out ApprovedDate (the same occurs for CompletedDate). Why would this be occurring when the conditionals are mutually exclusive?
##################################################
# Define CRState
#
Options CRState = PENDING{a}, APPROVED{b}, HOLD{a}, REJECTED{a}, COMPLETED{c}
{a}
{b} Preset ApprovedDate = $date
{c} Preset CompletedDate = $date
|
I don't understand your problem. If I use following config file:
[demo]
Theme = default
Attributes = Author, CRState, ApprovedDate, CompletedDate
Options CRState = PENDING{a}, APPROVED{b}, HOLD{a}, REJECTED{a}, COMPLETED{c}
{a}
{b} Preset ApprovedDate = $date
{c} Preset CompletedDate = $date
and make an entry, then edit it, selecting approved, then submit, then edit again, then select completed, then I get following:
which looks ok to me (the previous ApprovedDate does not get blanked out). Can you reproduce that behaviour? |
|