Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#76 2010-03-09 00:24:07
- tgv
- New Member
- Registered: 2010-03-07
- Posts: 3
Re: mem_form - Generic HTTP form processing
Another fix.
To make mem_form_select actually respect “required” attribute, at around line 822 replace
if (!empty($selected))
with
if (!empty($value)) or shorter if ($value).
Because an array with one empty element is not empty.
Cheers,
Kostya
Offline
Re: mem_form - Generic HTTP form processing
I must be doing something quite wrong as regardless of what tags I add, I get a constant
Textpattern Warning: tag does not exist on line 1120
I am using the latest downloadable v.0.6 and TXP v.4.2.0
Btw, does anyone know if there is a plug-in that would allow the sending of email attached files through a form on the site? ZCR does not do that, as far as I know.
Offline
#78 2010-04-21 02:07:15
- jeroenvg
- Member
- From: netherlands
- Registered: 2010-04-21
- Posts: 34
Re: mem_form - Generic HTTP form processing
is it possible to make a radio group required; meaning at least one option must be selected for the form to submit?
Offline
#79 2010-04-27 17:20:38
- jeroenvg
- Member
- From: netherlands
- Registered: 2010-04-21
- Posts: 34
Re: mem_form - Generic HTTP form processing
how would i go about translating mem_form’s (error) messages – the mem_form_lang array? can i do this with a callback hooking into mem_form? do i need the MLP plugin?
(i’m new to textpattern, and looking for examples)
Offline
#80 2010-05-05 17:09:40
- jeroenvg
- Member
- From: netherlands
- Registered: 2010-04-21
- Posts: 34
Re: mem_form - Generic HTTP form processing
jeroenvg wrote:
how would i go about translating mem_form’s (error) messages – the mem_form_lang array? can i do this with a callback hooking into mem_form? do i need the MLP plugin?
AFAICT, overriding the array from my own plugin is not how this is supposed to work:
// translate mem_form messages
register_callback('jvg_l10n', 'mem_form.defaults');
function jvg_l10n() {
$mem_self_lang = array(
'<index>' => '<dutch translation>',
...
);
}
Offline
#81 2010-05-05 18:11:25
- jeroenvg
- Member
- From: netherlands
- Registered: 2010-04-21
- Posts: 34
Re: mem_form - Generic HTTP form processing
i’m trying to parse a mem_form_hidden value from my own fields, using mem_form_value, like this:
...
<txp:mem_form_hidden
name="RealName"
required="0"
value='<txp:mem_form_value name="firstName" /> <txp:mem_form_value name="lastName" />'
/>
...
<txp:mem_form_text
break=": "
label="Last name"
name="lastName"
required="1"
/>
<txp:mem_form_text
break=": "
label="First name"
name="firstName"
required="1"
/>
...
but the value for RealName is always empty after submitting the form (both after a successful submit and one generating errors). am i doing something wrong?
Last edited by jeroenvg (2010-05-05 18:14:45)
Offline
#82 2010-06-02 01:49:30
- jeroenvg
- Member
- From: netherlands
- Registered: 2010-04-21
- Posts: 34
Re: mem_form - Generic HTTP form processing
jeroenvg wrote:
i’m trying to parse a mem_form_hidden value from my own fields, using mem_form_value […]
that won’t work, probably due to security measures against angle brackets (<, >). it will work, though, with mem_form_secret, like this:
...
<txp:mem_form_text
break=": "
label="Last name"
name="lastName"
required="1"
/>
<txp:mem_form_text
break=": "
label="First name"
name="firstName"
required="1"
/>
...
<txp:mem_form_secret
name="RealName"
value='<txp:mem_form_value name="firstName" /> <txp:mem_form_value name="lastName" />'
/>
(note the alternating single/ double quotes.)
Offline
Re: mem_form - Generic HTTP form processing
Adds better support for custom field level validation and form level validation.
Offline
Re: mem_form - Generic HTTP form processing
Thanks a lot Manfre !
Pascal
Offline
Re: mem_form - Generic HTTP form processing
Hello,
I try to integrate mem_form with mem_form_file into an existing ZCR formular as mentioned by Bloke in this post.
<txp:mem_form enctype="multipart/form-data">
<txp:mem_form_file label="File" name="myfile" />
</txp:mem_form>
the problem is, that textpattern says it doesn’t know the tag mem_form.
Fehler im Tag: <txp:mem_form enctype="multipart/form-data"> -> Textpattern Warning: Unbekannter Tag on line 1120
“unknown tag on line 1120”
I already several times switched the plugin off and on, but without change. I also reinstalled mem_form.gz.txt
I use textpattern 4.2.0 with latest mlp and mem_form 0.8.
Offline
Re: mem_form - Generic HTTP form processing
After some tests and rereading this thread …
It´s the same issue as datorhaexa already reported.
I tested version 0.8 on two installations of textpattern 4.2.0, with mlp and without, and I switched all other plugins off, reinstalled and so on, I get everytime this error message: “Textpattern Warning: tag does not exist”. What to do?
Offline
Re: mem_form - Generic HTTP form processing
with this plugin, my users after registration (mem_self_register) can write articles directly from site.
I understood it right?
<txp:txp_me />
Offline
Re: mem_form - Generic HTTP form processing
Katalonian wrote:
with this plugin, my users after registration (mem_self_register) can write articles directly from site.
I understood it right?
That is indeed possible, but you need one additional plugin to process the form on submission. I used mem_simple_form for that purpose; but you could also use mem_moderation with mem_moderation_article if you don’t mind moderating article submissions, or mem_public_article.
Offline
Re: mem_form - Generic HTTP form processing
wow! you need to create some article for using your plugins )
I try it all! thanks! great!
<txp:txp_me />
Offline
Re: mem_form - Generic HTTP form processing
Trying to use a forum thread as a bug tracker doesn’t really work for various reasons.
- I don’t always get the email about the thread being updated.
- Different problems get interleaved.
- I’m forget about them and don’t re-read the older pages of a plugin thread looking for unfixed issues.
In an effort to fix this communication disconnect, I have moved all of my plugin code over to bitbucket, /Manfre/txp-plugins. I’ve enabled the issue tracker and wiki (for documentation). With this new channel of managing my plugins, I will continue to ignore issues reported in this plugin thread, but now it will be intentional instead of accidental.
Offline