ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1952
|
Fri Sep 22 08:55:22 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | | Re: Attribute and checkbox |
Well, what we use for such kind of check lists is the following:
Use Preset test = file.txt where file.txt contains exactly the ASCII code you mentioned, like
[ job done] [ customer ] [ activity ] [ What should be done ]
[] BLA Check job1 Backup mail check
[] BLA1 Check job2 check error report
[] Bla2 Check job3 check MQ jobs
So one can put the "X" in the "[]" manually. I know, the individual lines are no real elog attributes, but it works nicely for some check lists. Drawback might be that a use can edit the whole text, but sometimes I find that's even a plus, since the user might add some comments. |
1955
|
Fri Sep 22 19:42:21 2006 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.6.2-1714 | Re: "Supress Email Notification" checkbox |
Stefan Ritt wrote: |
Steve Jones wrote: |
Steve Jones wrote: | Is there a way to allow email notification but have the "Suppress Email Notification" checked by default? We had complaints about the enormous amount of email so I turned off email notification for edits/replys, but there are times that I would like to allow email to be sent out -- this would imply allowing email by unchecking the "Suppress" box. |
What I think would be needed is:
Suppress Email on edit = 0|1|2
^
Where a '2' denotes that the "Suppress Email Notification" shows up but *checked* |
Just to a
Suppress default = 1 |
Quote: |
Not quite what I am looking for. What I need is:
"New" Logs
- Always send an email -- do not provide an option to check the box.
-- use Suppress Default = 2
"Edits and Replys"
- Provide the option to send an email, but by default the "suppress" box is checked
-- need Suppress Email on edit = 2
|
|
1957
|
Mon Sep 25 15:30:48 2006 |
| Dimitrios Tsirigkas | dimitrios.tsirigkas@cern.ch | Question | Linux | 2.6.1 | Invalid addresses block email notifications |
Hi Stefan,
We have had problems with some users who subscribe for elog notifications using fake email addresses. When this happens, e-mail notifications stop working for all users and I have to find out which is the problematic email address and fix it myself. Is this a known problem? Is there a fix in a version newer than 2.6.1?
Thanks,
Dimitris |
1958
|
Mon Sep 25 18:23:54 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.1 | Re: Invalid addresses block email notifications |
Dimitrios Tsirigkas wrote: | Hi Stefan,
We have had problems with some users who subscribe for elog notifications using fake email addresses. When this happens, e-mail notifications stop working for all users and I have to find out which is the problematic email address and fix it myself. Is this a known problem? Is there a fix in a version newer than 2.6.1?
Thanks,
Dimitris |
Hi Dimitris,
in fact I have the same problem here with the forum. So far I did not find a clever solution, but I have some thought on how to minimize it:
- Do the self registration by sending a key to the registered email address. Only by using that key the account can be activated. This way at least on ensures a proper email address initially. There are however ways to temporaryly generate email accounts, which kind of bypasses this system. Furthermore, if an email address becomes invalid because the domain is switched off, this does not help.
- Email at least an error notification to the admin in case of failure.
You would say "why not removing the invalid email address"? Well that's kind of hard, since I send the email notification to all recipients in one email. Therefor I cannot figure out which is the offending email address. If I would send the emails separately to everyone, this can easily take minutes, which in turn would block the email server for that time. A solution would be a multithreaded server, which in fact is planned, but will not come so soon. If you come up with another clever solution please let me know. |
1959
|
Mon Sep 25 21:09:58 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.2 | Re: Entry Submission Help |
kcmin wrote: | 1. When an entry is submitted is it possible to have it return to the submit page instead of a summary of the entry. In the ELog.cfg syntax on the site it mentions something about this. However It says something about a file being present in the resource directory. I am not sure what to do here. |
You can hand-write a HTML file which gets displayed after submission, but that's probably not what you want. Unfortunately there is no option to go back to the submit page, so you have to click New again. If you want to enter a bulk of data, you can also do a CSV import. Maybe that's easier for you. Just write a comma-separated-value file, and import it via "CSV Import".
kcmin wrote: | 2. When you submit an entry is it possible for the fields to stay set to the value that was selected on submission of the last entry. You would need to still be able to change them though. |
The Duplicate command was made for that. Just select an entry which is close to your new one (might be the last one entered), and click Duplicate. This gets you to what you want. |
1960
|
Fri Sep 29 18:35:09 2006 |
| marta flood | marta33911@aol.com | Question | | | Entering information |
I am not sure how to get to the page I need to log my clinical time for school and I have no idea how I got here
Thanks,
Marta |
1961
|
Mon Oct 9 22:32:11 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.6.2-1714 | Re: "Supress Email Notification" checkbox |
Suppress email on edit has been implemented in the current SVN revision just similar to the Suppress default flag having possible values of 0, 1, 2 and 3. |
1962
|
Tue Oct 10 08:52:50 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | | Re: Conditional E-Mail Attributes |
Grant Jeffcote wrote: | My version shows V2.6.2-1699.
I noticed you have 1714, is that the latest binary or your compiled CVS release?
|
Try this one: http://midas/elog/download/windows/elog262-3.exe which is the most recent. |