>> In order that Fox default messages are not displayed, set
>> in config:
>>$EnableFoxDefaultMsg = false;
>>
>> Alternatively you could set parameters foxsuccess="..." and
>> foxfailure="..." in the (:fox formname .. :) markup directive
>> to some message of your choice.
>> See https://www.
On 11/19/19 2:45 PM, Hans wrote:
* Display captcha error message:
I'd like to display a "failed captcha" message beside the entry field,
similar to what I'm doing with validating an email address using
(:foxcheck:) and (:foxmessage:). It appears that the captcha message
can only be displayed
On 11/19/19 2:50 PM, Hans wrote:
* Test if comment successfully submitted
I'd like to print a message when a comment is submitted, not the
complete list of messages.
You may need to set up some redirection to a different page than the
page which contains all your comments. use the parameter
> * Test if comment successfully submitted
> I'd like to print a message when a comment is submitted, not the
> complete list of messages.
You may need to set up some redirection to a different page than the
page which contains all your comments. use the parameter redirect=SOMEPAGE
in your fox m
> * Display captcha error message:
> I'd like to display a "failed captcha" message beside the entry field,
> similar to what I'm doing with validating an email address using
> (:foxcheck:) and (:foxmessage:). It appears that the captcha message
> can only be displayed using (:foxmessage:). Th
I'm using Fox to create a comment submission form. Captcha is used to
validate submission. The form creates a new page and sends an email.
I'm trying to resolve several issues.
* Display captcha error message:
I'd like to display a "failed captcha" message beside the entry field,
similar to
2009/6/2 Randy Brown :
> I want the user to type in a form without worrying about markup. OTOH,
> I want what's saved on the page to be a Page Text Variable.
>
> For example, the user types into the textarea associated with the page
> text variable MyPTV:
>
> Line 1
> Line 2
>
> And the form saves
I want the user to type in a form without worrying about markup. OTOH,
I want what's saved on the page to be a Page Text Variable.
For example, the user types into the textarea associated with the page
text variable MyPTV:
Line 1
Line 2
And the form saves on the page:
MyPTV: Line1\\Line2
I
Monday, June 1, 2009, 8:56:53 PM, Randy Brown wrote:
> Does anyone know how to create a form that has a textarea in which
> newline markup on the page appears in the form as newlines, and
> newlines written into the form are posted as newline markup on the page?
i do not understand this.
Can you
Does anyone know how to create a form that has a textarea in which
newline markup on the page appears in the form as newlines, and
newlines written into the form are posted as newline markup on the page?
I know Fox can treat a section as if it were a PTV, but I need access
to the entered va
Wednesday, July 16, 2008, 3:10:36 PM, noskule wrote:
> I experienced the same problem with the FoxContact form, if the
> submission fails the other fields are empty.
> (:input text name1 "{$:name1}" size=60:)(:foxcheck ...
> (:input text name2 "{$:name2}" size=60:)(:foxcheck ...
> is there a wa
Hans schrieb:
> Wednesday, July 16, 2008, 6:24:04 AM, Scott Smith wrote:
>
>
>> For example, I type in 'destination': San Diego/2008. The slash is invalid
>> and the validation mark-up catches it and re-displays the form. The
>> 'destination' field is now blank. This doesn't happen with my other
Wednesday, July 16, 2008, 6:24:04 AM, Scott Smith wrote:
> For example, I type in 'destination': San Diego/2008. The slash is invalid
> and the validation mark-up catches it and re-displays the form. The
> 'destination' field is now blank. This doesn't happen with my other fields
> that have valid
I'm struggling with a form that has validation (an effort to make my forms
right and proper). One of the fields, 'destination', is used to create the
Target page. This field has validation, making sure it isn't too short or
too long and doesn't include funky characters. The validation works; the
cr
Thursday, June 12, 2008, 7:35:53 PM, Hans wrote:
> 2. I don't know why you got style="display:none" for your div. It
> should not be necesssary, as togglehide hides the div initially.
I am mistaken in that point. togglehide does not hide a div initially,
or set any initial state.
~Hans
Thursday, June 12, 2008, 7:13:31 PM, Scott Smith wrote:
> I fill-out the form, putting the following in the References textarea,
> (:togglehide image showtext="Show Floor Plan" hidetext="Hide image":)
> LFOA Floor Plan
> (:div id=image style="display:none":)
> Attach:Systems/lfoaflpln.jpg
> (
I fill-out the form, putting the following in the References textarea,
(:togglehide image showtext="Show Floor Plan" hidetext="Hide image":)
LFOA Floor Plan
(:div id=image style="display:none":)
Attach:Systems/lfoaflpln.jpg
(:divend:)
I hit enter, and the form displays this in References--
(:
Thursday, June 12, 2008, 6:17:42 PM, Scott Smith wrote:
> Sorry about the partial. I didn't know if putting the full form in an email
> would be bad form, like using all caps.
The tricky part is to provide a minimum on information, but have all
relevant details intact. For a form problem this may
Wednesday, June 11, 2008, 6:10:09 PM, Scott Smith wrote:
> Sorry about the partial. I didn't know if putting the full form in an email
> would be bad form, like using all caps.
Thanks, I can see the form now, it works here.
Now back to your question:
> In my Fox Form, ShowHide and/or ToggleHid
Sorry about the partial. I didn't know if putting the full form in an email
would be bad form, like using all caps.
This is set: $EnablePostDirectives = true;
Form:
(:foxmessages:)
(:fox projectform put=top target='{$$projecttitle}' ptvupdate=1
template=ProjectTemplates#new redirect=1 upload=1 :
Wednesday, June 11, 2008, 7:09:00 PM, Scott Smith wrote:
> Here's a snippet--
> ||'''References:'''||(:input textarea cols=80 rows=10:) ||
> So, you're saying it should be (:input textarea references "{$:references}"
> cols=80 rows=10:)
No. name=$:references refers to the PTV name 'references'
Here's a snippet--
||'''References:'''||(:input textarea name=$:references cols=80 rows=10:) ||
So, you're saying it should be (:input textarea references "{$:references}"
cols=80 rows=10:)
On Wed, Jun 11, 2008 at 1:53 PM, Hans <[EMAIL PROTECTED]> wrote:
> Wednesday, June 11, 2008, 6:10:09 PM,
Wednesday, June 11, 2008, 6:10:09 PM, Scott Smith wrote:
> For instance, I have a very large floor plan image I want to appear only
> when the togglehide link is clicked. I add this to my form and save. The
> results are part of the (:togglehide line appears in the displayed field and
> the other
In my Fox Form, ShowHide and/or ToggleHide fail to work.
For instance, I have a very large floor plan image I want to appear only
when the togglehide link is clicked. I add this to my form and save. The
results are part of the (:togglehide line appears in the displayed field and
the other parts of
Friday, March 7, 2008, 11:38:50 PM, Randy wrote:
> I've just encountered what could be a serious issue for many people:
> after I modify a page using Fox or Foxedit, my page history only shows
> the most recent edit - all the prior history vanishes. Editing the
> same pages using PmWiki's normal
I've just encountered what could be a serious issue for many people:
after I modify a page using Fox or Foxedit, my page history only shows
the most recent edit - all the prior history vanishes. Editing the
same pages using PmWiki's normal edit form properly prepends to the
history.
This
Wednesday, January 9, 2008, 6:57:25 PM, Sameer Kumar wrote:
> What I am therefore aiming for is only one page that would have a part
> of it editable using a form which would also contain non-form based
> text.
Using Fox and FoxEdit you could insert an foxedit link, which targets
the par
Wednesday, January 9, 2008, 6:57:25 PM, Sameer Kumar wrote:
> What I am therefore aiming for is only one page that would have a part
> of it editable using a form which would also contain non-form based
> text.
Using Fox and FoxEdit you could insert an foxedit link, which targets
the part of your
Hi Hans,
I'm so exciting to know your update for Fox forms and adding 'replace' function.
It would be very useful. And your explanation are clear enough to follow.
However, as a newbie, can I ask some example pages which do the 'replace'
job(just like you do in the 'FoxContacts' recipe)? Thanks in
> From: "Sameer Kumar" <[EMAIL PROTECTED]>
> Subject: [pmwiki-users] Fox forms
>
> I have just started exploring Fox Forms as an alternative to
Wikiforms.
>
> (While Wikiforms works fine, I am having difficulty as it does not
allow
> editing of the
> From: "Sameer Kumar" <[EMAIL PROTECTED]>
> Subject: [pmwiki-users] Fox forms
>
> I have just started exploring Fox Forms as an alternative to Wikiforms.
>
> (While Wikiforms works fine, I am having difficulty as it does not allow
> editing of the targe
Wednesday, January 9, 2008, 5:08:42 PM, Sameer Kumar wrote:
> could you please explain the comparative notions of the new
> foxaction "replace" and the 'plugin' called 'Foxedit'?
> Are they meant for two different things or is 'Foxedit' now redundant?
They are very different.
FoxEdit provides ma
Fox was designed to add content, and not to replace it.
I say "was", because I just uploaded a major upgrade, which indeed
allows replacement of content, using a new foxaction "replace".
I still have to document all the changes though...
Hans,
Thanks for the detailed response and the update.
Wednesday, January 9, 2008, 12:02:34 AM, Sameer Kumar wrote:
> I would like to know if it is possible to edit data originally created
> with Fox by re-populating the original form and resaving it.
> Currently, every time the Fox form is submitted, a new instance of the
> data is added to the page
I have just started exploring Fox Forms as an alternative to Wikiforms.
(While Wikiforms works fine, I am having difficulty as it does not allow
editing of the target page, which is crucial for the site)
I have accomplished the basic Fox setup. I can create a new page with
text in it using a
35 matches
Mail list logo
