Shell execution generating error, posted by Steve Jones on Tue Sep 19 20:37:59 2006
|
When started as root *but not running as a daemon* shell execution results in the following errors that are sent to Standard Error:
[code]
|
Re: Shell execution generating error, posted by Stefan Ritt on Fri Sep 22 07:42:57 2006
|
[quote="Steve Jones"]When started as root *but not running as a daemon* shell execution results in the following errors that are sent to Standard Error:
[code]
|
|
Re: Shell execution generating error, posted by Steve Jones on Fri Sep 22 19:31:15 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]When started as root *but not running as a daemon* shell execution results in the following errors that are sent
to Standard Error:
|
Attribute and checkbox, posted by Arno Teunisse on Sun Sep 3 21:57:00 2006 
|
In the screen shots I see checkboxes before the attributes. How can I do that ??
In the doc I saw [B]Options <attribute> = boolean[/B]. But that creates a checkbox in the fill in form after the attribute. See second attached picture.
The first attached picture shows what I want but I can only get the result in the second picture. Can anybody help me in this one. ( Is there an [B]option |
|
Re: Attribute and checkbox, posted by Arno Teunisse on Mon Sep 4 22:36:03 2006
|
In the screen shots I see checkboxes before the attributes. How can I do that ??
In the doc I saw Options = boolean. But that
creates a checkbox in the fill in form after the attribute. See second attached picture. The first attached picture shows what I want but I can only get
the result in the second picture. Can anybody help me in this one. ( Is there an option checked for the attributes ?
Just answer |
|
Re: Attribute and checkbox, posted by Stefan Ritt on Fri Sep 22 08:55:22 2006
|
Well, what we use for such kind of check lists is the following:
Use [b]Preset test = file.txt[/b] where [b]file.txt[/b] contains exactly the ASCII code you mentioned, like
|
Email substitution quit working, posted by David Spindler on Tue Aug 29 15:28:51 2006
|
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.
|
|
Re: Email substitution quit working, posted by David Spindler on Tue Sep 5 15:59:47 2006
|
[quote="David Spindler"]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.
|
|
Re: Email substitution quit working, posted by Stefan Ritt on Fri Sep 22 08:50:08 2006
|
[quote="David Spindler"][quote="David Spindler"]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.
|
|
Top Text and Bottom Text only show "text" --- no files, posted by Steve Jones on Thu Aug 31 21:46:15 2006
|
Just compiled 2.6.2-1714 and "Top text" and "Bottom text" interpret everything as "text" --- nothing is interpreted as a file to be included, unless there
is a new syntax. |
|
Re: Top Text and Bottom Text only show "text" --- no files, posted by Steve Jones on Tue Sep 5 19:46:05 2006
|
[quote="Steve Jones"]Just compiled 2.6.2-1714 and "Top text" and "Bottom text" interpret everything as "text" --- nothing is interpreted as a file to be
included, unless there is a new syntax.[/quote]
|
|
Re: Top Text and Bottom Text only show "text" --- no files, posted by Steve Jones on Tue Sep 5 20:23:40 2006
|
[quote="Steve Jones"][quote="Steve Jones"]Just compiled 2.6.2-1714 and "Top text" and "Bottom text" interpret everything as "text" --- nothing is interpreted
as a file to be included, unless there is a new syntax.[/quote]
|
|
Re: Top Text and Bottom Text only show "text" --- no files, posted by Stefan Ritt on Fri Sep 22 08:21:39 2006
|
[quote="Steve Jones"]Stefan, I found the source of the problem. When you moved some files to "logbook_dir" you also told the code to look in "logbook_dir"
for top and bottom text files. The documentation indicates that the location dir should be "resource_dir".[/quote]
|
|
new entry form - "minimalist" approach , posted by frederic poncin on Mon Sep 18 16:53:09 2006
|
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:
|
|
Re: new entry form - "minimalist" approach , posted by Stefan Ritt on Fri Sep 22 07:54:58 2006
|
[quote="frederic poncin"]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:
|
|
Re: Why are Preset fields blanked out?, posted by Stefan Ritt on Mon Sep 18 15:21:56 2006
|
[quote="Steve Jones"]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?
|
|
Re: Re: Why are Preset fields blanked out?, posted by Steve Jones on Mon Sep 18 18:19:44 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]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?
|
|
Re: Re: Why are Preset fields blanked out?, posted by Stefan Ritt on Tue Sep 19 17:32:28 2006
|
[quote="Steve Jones"]
I think I found it. Try this:
[CODE]
|
|
Re: Re: Why are Preset fields blanked out?, posted by Steve Jones on Tue Sep 19 19:22:31 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]
I think I found it. Try this:
[CODE]
|
|
Re: Re: Why are Preset fields blanked out?, posted by Stefan Ritt on Tue Sep 19 20:28:15 2006
|
[quote="Steve Jones"]
Setting the "Type" to "date" causes the blanking to occur.
[/QUOTE]
|
|
Re: Re: Why are Preset fields blanked out?, posted by Steve Jones on Tue Sep 19 20:38:49 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]
Setting the "Type" to "date" causes the blanking to occur.
[/QUOTE]
|
|
Why are Preset fields blanked out?, posted by Steve Jones on Thu Sep 14 22:59:39 2006
|
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?
|
|
Re: Why are Preset fields blanked out?, posted by Stefan Ritt on Mon Sep 18 15:21:56 2006
|
[quote="Steve Jones"]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?
|
|
Re: Re: Why are Preset fields blanked out?, posted by Steve Jones on Mon Sep 18 18:19:44 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]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?
|
|
Re: Re: Why are Preset fields blanked out?, posted by Stefan Ritt on Tue Sep 19 17:32:28 2006
|
[quote="Steve Jones"]
I think I found it. Try this:
[CODE]
|
|
Re: Re: Why are Preset fields blanked out?, posted by Steve Jones on Tue Sep 19 19:22:31 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]
I think I found it. Try this:
[CODE]
|
|
Re: Re: Why are Preset fields blanked out?, posted by Stefan Ritt on Tue Sep 19 20:28:15 2006
|
[quote="Steve Jones"]
Setting the "Type" to "date" causes the blanking to occur.
[/QUOTE]
|
|
Re: Re: Why are Preset fields blanked out?, posted by Steve Jones on Tue Sep 19 20:38:49 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]
Setting the "Type" to "date" causes the blanking to occur.
[/QUOTE]
|
|
Unsubscribe from logbooks, posted by Chris Warner on Fri Sep 8 18:42:05 2006
|
| Is there a way for user to unsubscribe from a logbook? Can a user delete their own account? |
|
Re: Unsubscribe from logbooks, posted by Stefan Ritt on Mon Sep 11 17:25:54 2006
|
[quote="Chris Warner"]Is there a way for user to unsubscribe from a logbook? Can a user delete their own account?[/quote]
Yes. Yes.
|