zem_contact_reborn 4.0.3.20

philwareham · 2015-02-26 13:26:05

Where is the most recent (compiled) version of this plugin? Stef’s version is the raw PHP file so I can’t paste it into plugin page. Cheers.

Bloke · 2015-02-26 13:53:54

philwareham wrote #288622:

Where is the most recent (compiled) version of this plugin?

You’ve got mail. Really need to get the new version released and stop clogging up Ruud’s 4.3.2.0 thread.

philwareham · 2015-03-05 08:29:22

Hi Stef,

Any chance you can compile and tag a beta of the plugin on GitHub, with the latest amends I committed rolled in?

Mighty want to look at the new attributes I added first and make sure all is well. In particular the autocomplete which is currently a value of on and off (the W3C spec) but you may want to also allow 1 and 0 (for consistency with Textpattern conventions).

Pat64 · 2015-03-14 14:15:10

Hi folks ;)

Uli, or any others, can you explain me in details how to proceed to populate a field into a zem_contact form?

Ref. http://forum.textpattern.com/viewtopic.php?pid=253414#p253414

Thanks lot by advance.

Cheers,

uli · 2015-03-14 15:36:40

Hi Patrick, here’s what I meant by “suffixing”, immediately in the shape of the code I used for a small publishing house:

<a title="Order this book" href="<txp:site_url />directorder?title=<txp:php>echo(rawurlencode($GLOBALS['thisarticle']['title']));</txp:php>&amp;price=<txp:custom_field name="price" />&amp;article=<txp:article_id />" class="order">Order <txp:title /></a>

It creates a link to a section directorder and adds parameters as “suffixes” to the URL, here ?title=NameOfTheBook&price=Value&article=IdOfTheBook. You usually would get along without resorting to txp:php but here I had book titles with accented letters and cedillas, like you have in France, too :)

On the directorder page with your zem_cr form you then can read the URL parameters with adi_gps and use the adi tags to fill in your form fields:

<txp:zem_contact_text name="book" label="book" default='<txp:adi_gps name="title" />' />

Edit: typos.

Last edited by uli (2015-03-14 15:38:31)

Pat64 · 2015-03-14 17:43:15

;)

Thanks lot Uli!

jakob · 2015-03-14 20:50:40

Depending on your setup, you could also just pass the <txp:article_id /> via the url and then use that to look up the respective item details on the form page.
You could then pass the relevant details into disabled/non-editable form fields or as a secret input item. That prevents people from manipulating the url to get another price, for example, or bots from sending you rubbish. You can also use that to filter what can be sent, e.g. in uli’s case to prevent orders being made for products that may no longer exist or are out of stock.

If you do use an article id, you should also check that a) it exists and b) is of the right kind, e.g. is in the correct section. Ideally, you want to be sure that all data passed via the url is cleaned before being passed on.

colak · 2015-03-15 16:34:48

since the first of March I have received 8 spam emails from different IPs which all share some similarities. There is no flood as such but I would rather not receive them as they also subscribe to our newsletter so I have to also delete them from the db. Is there a way which I could detect those common elements and stop them from posting or more importantly registering?

philwareham · 2015-03-16 09:07:06

colak wrote #289087:

since the first of March I have received 8 spam emails from different IPs which all share some similarities. There is no flood as such but I would rather not receive them as they also subscribe to our newsletter so I have to also delete them from the db. Is there a way which I could detect those common elements and stop them from posting or more importantly registering?

It would be nice to have a Recaptcha tag which could be used, as part of the zen_contact_reborn toolset. I’ve opened an issue and we can discuss there.

Recent versions of Recapture aren’t as painful for users as it used to be, I feel.

tye · 2015-03-16 22:12:52

How about a honeypot feature…. on other CMS systems I’ve found this to be the most effective by far….

Bloke · 2015-03-17 17:55:56

tye wrote #289126:

How about a honeypot feature….

The companion plugin pap_contact_cleaner does that… sort of. It adds fake inputs which are hidden to humans. Since bots are greedy, if the hidden fields contain anything, the message can be discarded.

But going forward, if anyone wanted to build a different type of honypot module to run alongside ZCR, that’d be ace. The core plugin is going to stick to being a platform for building relationships with customers I think. Bells and whistles such as this can then be built on the scaffolding.

colak · 2015-03-17 18:05:32

I’m still trying to figure out if they are bots or humans. I received another 2 emails (and postmaster registrations) since my last post here.

Textpattern CMS

Textpattern CMS support forum

#1477 2015-02-26 13:26:05

Re: zem_contact_reborn 4.0.3.20

#1478 2015-02-26 13:53:54

Re: zem_contact_reborn 4.0.3.20

philwareham wrote #288622:

#1479 2015-03-05 08:29:22

Re: zem_contact_reborn 4.0.3.20

#1480 2015-03-14 14:15:10

Re: zem_contact_reborn 4.0.3.20

#1481 2015-03-14 15:36:40

Re: zem_contact_reborn 4.0.3.20

#1482 2015-03-14 17:43:15

Re: zem_contact_reborn 4.0.3.20

#1483 2015-03-14 20:50:40

Re: zem_contact_reborn 4.0.3.20

#1484 2015-03-15 16:34:48

Re: zem_contact_reborn 4.0.3.20

#1485 2015-03-16 09:07:06

Re: zem_contact_reborn 4.0.3.20

colak wrote #289087:

#1486 2015-03-16 22:12:52

Re: zem_contact_reborn 4.0.3.20

#1487 2015-03-17 17:55:56

Re: zem_contact_reborn 4.0.3.20

tye wrote #289126:

#1488 2015-03-17 18:05:32

Re: zem_contact_reborn 4.0.3.20

Board footer