iSoftware

We just released a new version with more supported fields.
Let us know how this works!

Hello,

What version of Gravity Forms are you using?

There is a dependency on the mb_detect_encoding since we parse the forms in order to change field attributes.

As GF 1.9 is here, we will focus on making the transition easy for existing users.

An update is on the way but we dont have an ETA.

Thank you for reporting this.

This plugin is not designed to work with GF 1.9+
We are working on a solution for porting forms created pre 1.9 to the new schema but dont have an ETA yet.

You should disable this plugin if you wish to work with 1.9+ or revert to 1.8.xx latest

Thank you

Hello and thank you for your input.

Can you provide an link to your form at the site hosted on iPage where we can have a look at the error that is produced.

iSoftware

Thank you for your input.

We have tested this on MAMP Pro but could not reproduce this error. Should this issue come up again please let us know.

iSoftware

If you are reffering to HTML validation for Gravity Forms then you should look at our other plugin specifically for that at Gravity Forms Html5 Validation

Hi,

The plugin is tested to work on latest Gravity Forms 1.8.22.

Using Output HTML5 option set to Yes and No Conflict Mode either On or Off should work.

Are you using some other plugin that extends Gravity Forms?

I managed to reproduce this and is fixed in ver. 2.7.3

I cannot reproduce this so I would like your assistance.

The gform_placeholder script is listed as a dependency for the following scripts:

gform_form_admin
gform_form_editor
gform_gravityforms

the first two are used in the admin so I guess that gform_gravityforms is not loading on your front end?

After looking at the form I can deduct that either another plugin or the X theme is messing with the email field, to perhaps mask something out.

Unfortunately we do not have access to X theme in order to see what is going on under the hood.

The GF HTML5 Placeholders plugin uses DomDocument and XPath by design to alter the field attributes in absence of better GF hooks. This does not play well with embedding scripts inside fields.

The GF team is working on GF 1.9 beta’s that includes built-in support for placeholders but I do not know when they plan to release a production version of 1.9.

Not sure if this helps, but thank your for input.

This is Gravity Forms designed behavior. If you disable css GF setting it doesn’t output scripts in front end both css and js.

We do not want to alter the default behaviour of the GF setting, even though this doesn’t feel right for the Placeholder.js script.

As an alternative, you can manually enqueue the Placeholder.js script using wp_enqueue_script(‘gform_placeholder’) if you so choose to disable front end scripts.

Thank you again for your insight.

Gravity Forms has this script built-in at ver. 2 something. We just incorporate the latest version of this script (3.0.2) and override the built-in with de register and register statements. The enqueuing is being handled by gravity forms, not our plugin anymore.

This script does not depend on jQuery so you shouldn’t have a problem.

As far as 1.9 beta is concerned, this plugin is not compatible and should not be used together. Our testing is conducted with the latest production version of GF (1.8.19 atm).

Hi nicomollet,

This issue is resolved in Gravity Forms HTML5 Placeholders ver. 2.7.2

We removed the original script that was jQuery dependent and overriden the build-in Gravity Forms script ‘gform_placeholder’ to use the latest version of Placeholders.js found at https://jamesallardice.github.io/Placeholders.js/.

Thank you for your input

Hi hilj,

We have tested the plugin with 1.8.19 and I cannot reproduce your problem.
Do you have a live installation where I can have a look at your form?