charroma

It’s not just about the plugin, the plugin is secondary. It’s about the missing form tag and breaking the browser native functionnality to auto-fill with a previous data entry. Like in the following screenshot.

The only thing missing is a <form> tag around the input fields.

In my own opinion you overrelied on javascript (React) and complicated the forms code, like many plugins and WordPress (Gutenberg), instead of a simple php form. If the new interface needs a scroll progress indicator, it’s a sign it’s not a good UI.

Version 6
There is not really a step to reproduce. In version 6, all the input fields were enclosed within a html form tag. It allowed the browser to show previous entries in a field with the same name.

It also allowed me to hook the plugin qtranslateXT to the field for an easier translation. Notice the left blue border of the field.

Version 7
In version 7, the tag form was removed. Now the field history is gone and I can’t hook the plugin to the field anymore. The field are now showing “[:fr]Statistiques[:en]Statistics[:]”.

There is something fishy when the page loads. The fields show the correct language and then a javascript trigger and reload the fields. https://ufile.io/d4hfpt8e

Sorry, I created my own solution as this was time sensitive for a client.