Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For now, let's see what will happen if we do not add a Custom error text and we disable the Debug mode.

Following the configurations demonstrated, the Plugin validation error has been replicated:

  • "Validation Error" is printed out to show app designers that the validation has failed
  • "reCAPTCHA error" is a Default default error text printed out if no Custom error text is added
  • protected by reCAPTCHA widget does not show an red error message like what happened in What is a reCAPTCHA widget error?

In this case, Debug mode is disabled, so you will see the default error text.

But note that if Debug mode is enabled, you will see neither default error text or Custom error text (if you have added it).

More on Debug mode in Custom error text & Debug mode.

Info
titleEdit Invisible reCAPTCHA: Other configuration properties
  • An important note to take down is thatthe default error textdoes not explain much to app designers on what "reCAPTCHA error" actually means.
  • A meaningful error text or message is strongly encouraged in order to give app designers a rough idea of what the error is and how to start fixing it.
  • This is why we have two other configuration properties called the Custom error text and Debug mode to help prevent app designers from facing problem like this.

You can refer to Custom error text & Debug mode sections for more information on the two other configuration properties.

Tip: Hover on the tooltips (? icon) in Edit Invisible reCAPTCHA configuration to read what each configuration properties mean.

...

  • Custom error text is designed to be printed out to end-users only when there is a Plugin validation error.
  • Debug mode helps app designers indicate the problem or error in different formats (depending if enabled or disabled).

Image Added


Image Added

image to be inserted here later..

...