zem_contact_reborn 4.0.3.20

jdykast · 2008-03-27 13:57:51

When using $evaluation -> add_zemcontact_status(1); to prevent ZCR from submitting is there a way to change the error message that gets returned? I’m not using it to detect spam and I would like to give the user accurate information about why the form did not submit.

Maybe something like:

$evaluation -> add_zemcontact_status(1);
$zemErrorMsg = 'Insightful and informative error message.';

Thanks

ruud · 2008-03-27 14:08:57

If you only have one possible error message, then you can change it in zem_contact_lang.

jdykast · 2008-03-27 18:38:08

As I thought about things a bit more I realize I was asking the wrong question. I’m not checking for spam but I do want the ability to prevent the form from submitting and to signal various errors. Is there a way to pass errors back to ZCR? (There is the possibility for multiple errors so it doesn’t seem like changing the language file is an option.)

ruud · 2008-03-27 19:14:12

Jason, you could do this without even editing ZCR: create a plugin that offers a tag like <txp:jdy_zem_contact_checks /> and place that tag at the end of your zem_contact form (inside the form). That way, the taghandler for that tag is called after all the earlier form tags have been processed. Since the $zem_contact_error and $zem_contact_form/values/labels arrays are globally accessible, you can read the form values/labels and use those to add errors based on the additional checks you want to perform. The tag itself should return an empty string.

Logoleptic · 2008-03-27 19:55:21

Ruud, your response got me thinking a bit. Could a similar approach be used to extend the validation capabilities of ZCR with tools like checking for proper date format? How would one go about assigning checks to particular fields?

Ordinarily I’d do that kind of validation with JavaScript if I’m using ZCR, but doing it on the server has definite advantages.

ruud · 2008-03-27 19:57:35

Sure, that’s possible. Assigning checks to specific fields might be done by specifying which fields to check in the attribute of the tag that does the validating, for example: <txp:abc_zem_contact_check_date name="field1,field3" />

Logoleptic · 2008-03-27 22:25:08

Thanks, Ruud. I’ll add this to my growing list of “plugins I should work on Real Soon Now.” If someone else gets to it first, then so much the better. :-)

jdykast · 2008-03-28 02:05:03

These are probably obvious answers but I still need to ask…

1. Is there a way to tell ZCR a field has been flagged with an error so that it can be given the error class?
2. Other than checking for a specific error message within $zem_contact_error is there a way to see if a field has already triggered an error message?

I’m working on an unsubscribe function and I’m using my “preflight” function to compare a provided email address with the email addresses within a db. (I want to verify the address actually exists within the db before removing that subscriber.) I want ZCR to ensure the user has supplied a valid email address and, if so, I want to see if that email address exists within my db. In the event that an invalid email address is provided an error would be triggered by ZCR as well as my preflight function but I don’t want to return two error messages.

EDIT:
By the way, Ruud, thanks for the tip. The ability to do some preflight checks is amazing!

Last edited by jdykast (2008-03-28 02:06:46)

ruud · 2008-03-28 07:33:24

yes, see the plugin help, specifically the part about styling. When an error occurs, that field gets a different class.
not inside ZCR, so you’d have to remove duplicate errors manually by checking the error array.

jdykast · 2008-03-28 12:27:59

For the answer to number 1, I think I wasn’t clear in the phrasing of the question. To keep using my example of looking for an email address, is it possible for ZCR to pass the address as valid but for my preflight to flag it with an error because it didn’t exist in the db? I understand ZCR’s ability to give a field the error class but is it possible for my preflight function to do the same? At this point I don’t see how I can do anything more than adding a message to $zem_contact_error. I don’t see how it’s possible for my function to add the error class to a field if ZCR passes it as error free.

ruud · 2008-03-28 15:06:11

Hmm.. you’re right, that isn’t possible without hacking the plugin.

jdykast · 2008-03-29 02:20:01

At this point it’s not worth it for me to hack around with ZCR. My current use for this preflight functionality is pretty basic and I think what I have now is going to do just fine. Thanks again for the tip.

Textpattern CMS

Textpattern CMS support forum

#265 2008-03-27 13:57:51

Re: zem_contact_reborn 4.0.3.20

#266 2008-03-27 14:08:57

Re: zem_contact_reborn 4.0.3.20

#267 2008-03-27 18:38:08

Re: zem_contact_reborn 4.0.3.20

#268 2008-03-27 19:14:12

Re: zem_contact_reborn 4.0.3.20

#269 2008-03-27 19:55:21

Re: zem_contact_reborn 4.0.3.20

#270 2008-03-27 19:57:35

Re: zem_contact_reborn 4.0.3.20

#271 2008-03-27 22:25:08

Re: zem_contact_reborn 4.0.3.20

#272 2008-03-28 02:05:03

Re: zem_contact_reborn 4.0.3.20

#273 2008-03-28 07:33:24

Re: zem_contact_reborn 4.0.3.20

#274 2008-03-28 12:27:59

Re: zem_contact_reborn 4.0.3.20

#275 2008-03-28 15:06:11

Re: zem_contact_reborn 4.0.3.20

#276 2008-03-29 02:20:01

Re: zem_contact_reborn 4.0.3.20

Board footer