com_connect - form and contact mailer

phiw13 · 2020-02-01 07:11:43

jrmartin wrote #321454:

I had been trying to send a message by using autofill to enter the names and email address.

Interesting. When I use autofill (with Safari), i do not have that issue; can’t test with Firefox though as it does not “know” me and it does not read the macOS data (my ‘me’ card in particular).

colak wrote #321461:

[…] As such, by separating the boys from the bots, we are creating paid jobs.

hmmm that is definitely not an argument i would make in favour of the plugin. Ever seen the inside one of those manual “bot” factories? It is about as bad as the English 19th century textile factories

If you think that the pap_comconnect fields could be configurable, I would still keep them invisible but have them named by admins in the preferences.

Yes.

The other way is to have a help file stating the names of the fields and warning users to to use them in their actual fields.

That is already a step forward. (I actually always use tel and email by habit I think, or maybe it is a Japanese tradition ?).

jakob · 2020-02-01 07:45:49

I guess the true test is what the bots fill out. It’d be interesting to know what fields are most effective.

I doubt that bots are terribly specific in their market-focus – except maybe in non-latin languages – so cultural convention may play only a secondary role.

What could be a good idea, though, is to set autocomplete="off" for those fields to prevent the browser filling them out: autocomplete docs and support for autocomplete on / off is at least reasonable.

colak · 2020-06-02 07:48:09

I have a long form which for some reason refuses to post, every time returning errors that such and such fields are required, in spite of the fact that I fill them all.

The form is a survey we are conducting and includes 35 fields, consisting of text, select, check boxes and a textarea. Although the form requires about 5 to 6 minutes to complete, I’ve set the expiration to 1200 secs in order to allow for coffee breaks:)

I am using the latest stable 4.6 release on the latest txp stable version. At the moment the form is in an draft article, but I also tested it using a future date without any success.

The contact form on our site appears to be working just fine. Did I hit a limitation on the allowed number of fields?

Bloke · 2020-06-02 07:56:20

Might be the payload size. Can you please share your contact form with me? PM is fine. I’ll see if I can get to the bottom of it.

Last edited by Bloke (2020-06-02 07:56:58)

colak · 2020-06-02 08:34:43

Solved. We are allowed no spaces for the name attribute. Once I deleted those. All works as expected.

Stef, although I did send you an email, you can ignore it, unless of course you wish to snoop in:)

Bloke · 2020-06-02 08:58:33

Ah yes. That’s correct. I wonder if we should dumb down the name field automatically? I think we do that if you just use label, can’t remember offhand.

colak · 2020-06-02 11:11:57

Bloke wrote #323479:

Ah yes. That’s correct. I wonder if we should dumb down the name field automatically? I think we do that if you just use label, can’t remember offhand.

I don’t really know:)

What I did come across is a problem with the validation when using com_connect_select and the options starting with a comma. ie

<txp:com_connect_select name="txp" label="Does txp rock?" options=",Yes,Definitely,You bet ya" />

The Nu html checker returns:

Error: Element option without attribute label must not be empty.

The problem of course is that there is no other way to force a user to make a selection. From the help:

Drop-down selection list labeled ‘Department’, containing three options and a blank option (due to the comma before ‘Marketing’) shown by default, forcing the user to make a selection.

Also: As the rest of the help appears to be in en-gb, should labeled be labelled?

Bloke · 2020-06-02 11:15:57

colak wrote #323484:

a problem with the validation when using com_connect_select and the options starting with a comma.

I’ll look into that, thanks. Do you get the same problem if you use it as a container with the <txp:com_connect_option /> tags?

Should labeled be labelled as the rest of the help appears to be in en-gb?

Yes. Will fix.

colak · 2020-06-02 11:17:43

Bloke wrote #323485:

Do you get the same problem if you use it as a container with the <txp:com_connect_option /> tags?

Admittedly, I did not experiment with that tag yet. Will do and I’ll return.

colak · 2020-06-02 11:23:10

I just did. The validation issue remains.

colak · 2020-06-02 11:29:21

I did find this fiddle which appears to be valid. Basically the first option to the selection, should have no value.

>Edited to add that I also tested

<txp:com_connect_select label="Department">
    <option  value="" selected>Select</option>
    <txp:com_connect_option label="Marketing" />
    <txp:com_connect_option label="Sales" />
</txp:com_connect_select>

which works just fine. I’m now thinking how that could be automated using the com_connect_select tag, and one way could be that we could have something like selected="Select" or another word which when used, and when the list starts with a comma, <option value="" selected>Select</option> is rendered.

Last edited by colak (2020-06-02 12:01:10)

phiw13 · 2020-06-02 12:03:31

Yes, that validation issue is something I have flagged here and on Github (if memory serves) in the past.
I build my <select /> widget completely manually.

<txp:com_connect_select break="" class="" label="Subject" name="subject">
<option selected value="" label="Select one"></option>
<txp:com_connect_option class="" label="goods" value="goods" />
<txp:com_connect_option class="" label="services" value="services" />
[...]
<txp:com_connect_option class="" label="Other…" value="Other…" />
</txp:com_connect_select>

@ Bloke

I wonder if we should dumb down the name field automatically

hmm, underscores or hyphens to replace spaces ? Despite my dislike for underscores, that seems the better option.

Textpattern CMS

Textpattern CMS support forum

#205 2020-02-01 07:11:43

Re: com_connect - form and contact mailer

jrmartin wrote #321454:

colak wrote #321461:

#206 2020-02-01 07:45:49

Re: com_connect - form and contact mailer

#207 2020-06-02 07:48:09

Re: com_connect - form and contact mailer

#208 2020-06-02 07:56:20

Re: com_connect - form and contact mailer

#209 2020-06-02 08:34:43

Re: com_connect - form and contact mailer

#210 2020-06-02 08:58:33

Re: com_connect - form and contact mailer

#211 2020-06-02 11:11:57

Re: com_connect - form and contact mailer

Bloke wrote #323479:

#212 2020-06-02 11:15:57

Re: com_connect - form and contact mailer

colak wrote #323484:

#213 2020-06-02 11:17:43

Re: com_connect - form and contact mailer

Bloke wrote #323485:

#214 2020-06-02 11:23:10

Re: com_connect - form and contact mailer

#215 2020-06-02 11:29:21

Re: com_connect - form and contact mailer

#216 2020-06-02 12:03:31

Re: com_connect - form and contact mailer

Board footer