Thread

Hi guys, just a small issue with safecracker, the following works:

{if error:title}{segment_1}{/if}

But this doesn’t

{if error:title}My custom error message{/if}

Any ideas? Only need to do this because my ‘title’ isn’t a title, its a name

Hi, DaveNZ. Can you tell us which version/build of EE2.x you’re using? See EEWiki:// HowTo Determine My EE Version

Also, which version of SafeCracker are you using? Is it 2.0 or 1.3?

How about what’s in your template?

Hi Sue, Using 2.1.3, with latest version of safecracker (downloaded yesterday). The template is a pretty standard form, opening tag is:

{exp:safecracker channel="donations" return="donate/thanks/ENTRY_ID" logged_out_member_id="1594" safecracker_head="no" error_handling="inline"}

sorry, in my first post I mean to say that this works

{if error:title}{error:title}{/if}

, not sure why I put segment_1 in there!

Hi, Dave. You’ll need to have a bit of patience with us - we’re also getting used to using SafeCracker.

When I look through the code, I see the following in the SafeCracker language file:

'required' => 'The %s field is required.',

which appears to be the way the error is handled. It’s an error in the title, so the text for the title is in the %s.

If you want another language key more specific only the title field being missing, a Feature Request would be the way to go.

As far as the Captcha goes, I’m going to split the thread off because that’s a separate issue.

Yep I understand the lang file issue, but regardless of that you should be able to use the conditional {if error:title}{/if} or {if error:title != ''} to write your own message, if any error is returned for a particular field. Surely? Hopefully you guys got support from Barret Newton as part of the deal 😊

Hi CrescendoNZ,

It would stand to reason that the example from your first post (see below) should work. That is not the current behavior

{if error:title}My custom error message{/if}

I am taking this to the team for further investigation. In the mean time you can sort of work around it by combining both steps:

{if error:title}{error:title}. Additional clarification text if needed{/if}

Best regards,
Barry

Thanks Barry, hopefully its something thats relatively simple to patch. Can’t really use the workaround as my ‘title’ field is actually a name and it doesn’t make sense. So have just disabled inline error handing in the meantime

Dave, I’m going to leave this thread open for the moment until we can get a definite bug report number or an explanation from Barry (one of our wonderful testing team) on what the functionality should be. Sound OK to you?

Great thanks Sue!

(Responding to put to the bottom of the queue, nothing substantive to add to the thread. Housekeeping post.)

Hi CrescendoNZ,

We can confirm that it is indeed a bug and we’ll have a report for you to follow shortly.

Thank you for your patience!

Best regards,
Barry

Just wondering if this is fixed yet? Its been nearly a month

Hi CrescendoNZ,

There has not been another release as yet. Just so that we all get a public track of what is fixed/dealt with we would ordinarily create a Bug Report. In this case would you mind creating one for this issue? Please make sure to reference this thread.

Cheers

Greg

So it was identified as a bug on the 9th of March and only now are asking me to file a bug report? Something that simple should have been fixed by now, starting to worry about how slow EE development is - when Barret Newton owned safecracker this would have been fixed within a day or two.