| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1938
|
Mon Sep 18 18:56:19 2006 |
 | Steve Jones | steve.jones@freescale.com | Question | All | 2.6.2-1714 | Re: "Supress Email Notification" checkbox |
| 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* |
|
1941
|
Tue Sep 19 17:32:28 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.6.2-1714 | Re: Re: Why are Preset fields blanked out? |
| Steve Jones wrote: |
I think I found it. Try this:
Locked Attributes = ApprovedDate, CompletedDate
##################################################
# Define CRState
#
Options CRState = PENDING{a}, APPROVED{b}, HOLD{a}, REJECTED{a}, COMPLETED{c}
{a}
{b} Preset ApprovedDate = $date
{c} Preset CompletedDate = $date
In my config when I remove the two attributes from "LOCKED ATTRIBUTES" the fields do not get blanked out.
|
No, even with that it does not get blanked out. Attached is the complete elogd.cfg with which it works fine in my case (R1714). Can you try that? |
| Attachment 1: elogd.cfg
|
[global]
port = 8080
[demo]
Comment = Test
Attributes = Author, CRState, ApprovedDate, CompletedDate
Locked Attributes = ApprovedDate, CompletedDate
Options CRState = PENDING{a}, APPROVED{b}, HOLD{a}, REJECTED{a}, COMPLETED{c}
{a}
{b} Preset ApprovedDate = $date
{c} Preset CompletedDate = $date
|
|
1942
|
Tue Sep 19 19:22:31 2006 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.6.2-1714 | Re: Re: Why are Preset fields blanked out? |
| Stefan Ritt wrote: |
| Steve Jones wrote: |
I think I found it. Try this:
Locked Attributes = ApprovedDate, CompletedDate
##################################################
# Define CRState
#
Options CRState = PENDING{a}, APPROVED{b}, HOLD{a}, REJECTED{a}, COMPLETED{c}
{a}
{b} Preset ApprovedDate = $date
{c} Preset CompletedDate = $date
In my config when I remove the two attributes from "LOCKED ATTRIBUTES" the fields do not get blanked out.
|
No, even with that it does not get blanked out. Attached is the complete elogd.cfg with which it works fine in my case (R1714). Can you try that? |
| Quote: |
Stefan, when I try that config in a demo logbook in my installation *but with all other items in [global] I get the same field-blanking behavior. I am going to try going back to a completely pristine .cfg, but I suspect this will work fine. I will need to add back in configuration items until I run into the culprit.
Ok, I found it. Try this config:
[global]
port = 8080
[demo]
Comment = Test
Attributes = Author, CRState, ApprovedDate, CompletedDate
Locked Attributes = ApprovedDate, CompletedDate
Type CompletedDate = date
Type ApprovedDate = date
Format CompletedDate = 1
Options CRState = PENDING{a}, APPROVED{b}, HOLD{a}, REJECTED{a}, COMPLETED{c}
{a}
{b} Preset ApprovedDate = $date
{c} Preset CompletedDate = $date
Setting the "Type" to "date" causes the blanking to occur.
|
|
|
1943
|
Tue Sep 19 20:28:15 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.6.2-1714 | Re: Re: Why are Preset fields blanked out? |
| Steve Jones wrote: |
Setting the "Type" to "date" causes the blanking to occur.
|
Ok, then don't set the "Type" to "date"  |
|
1945
|
Tue Sep 19 20:38:49 2006 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.6.2-1714 | Re: Re: Why are Preset fields blanked out? |
| Stefan Ritt wrote: |
| Steve Jones wrote: |
Setting the "Type" to "date" causes the blanking to occur.
|
Ok, then don't set the "Type" to "date" |
| Quote: |
Yuk! Thanks!
|
|
|
1948
|
Fri Sep 22 07:50:39 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.6.2-1714 | Re: "Supress Email Notification" checkbox |
| 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 |
|
1949
|
Fri Sep 22 07:54:58 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.2 | Re: new entry form - "minimalist" approach |
| frederic poncin wrote: | I'm playing with the configuration files in order to produce a "minimal" form.
At this time, I did not succeed in removing the following components:
- the "Fields marked with * are required" field |
This is handled by
Required attributes = ...
so just remove this line completely if you don't need them.
| frederic poncin wrote: |
- the "Entry time:" field
- the "encoding ELCode / plain / HTML" field
- the "preview" button
- the duplication of the Submit/Preview/Back buttons on the top and the bottom of the page.
|
These fields are always present and cannot be turned off. If you are concerned about screen space (PDA\?), you can change the CSS file for smaller fonts etc. |
|
1951
|
Fri Sep 22 08:50:08 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.2-1699 | Re: Email substitution quit working |
| David Spindler wrote: |
| David Spindler wrote: | I have recently upgraded from the 2.6.0-beta (I believe) to 2.6.2-1699. I just found out that on the day I upgraded, email substitution has stopped working. I have checked the discussion area and all the documentation and do not see any clues. The debug_log.txt file shows that the emails are being processed, but the fields are not being substituted correctly.
Thanks, in advance for any help,
David
|
I have not been able to find anything wrong in my config file, so I replaced 2.6.2 with 2.6.1 (apparently that was what I was running last, not the 2.6.0-beta) and my troubles have disappeared.
Anybody have any idea what has happened? |
This problem has been fixed in revision 1712. So I made an 2.6.2-2 for the Windows community just now. Please upgrade. |