doublesharp

Sorry for the delay. I had some dental work done and have been taking painkillers the past few days, so not much programming. There are some factors I didn’t consider when I did the POC even though it “works”, primarily the DOM element ID’s, so the is still a bit more to do. I’ll let you know once it’s ready to demo.

Thanks!

I did some testing last night and was able to get the validation to work on the front-end with some modifications, a big one being including the JavaScript on the front-end and not just the admin, so I’m not sure why you would be seeing a conflict on the front-end with this plugin enabled. If the JavaScript is being included, then it would likely be intercepting the submit click and not letting it continue due to differences in the CSS selectors that I am currently using for the admin.

If you’re interested I can give you a copy of the dev code so you can give it a try, it will require an additional constant ACF_VF_FRONTEND to be defined and set to true since typically you wouldn’t want the javascript included on the front end.

I haven’t tested this at all on the front end using acf_form() so my initial guess is that either something isn’t loading because it isn’t is_admin() or that the validation is failing but the CSS selectors to show the errors aren’t working.

Can you try using the Developer Tools in Chrome on the network tab to see if there is a request made to wp-ajax.php with the field info when you try to edit/post? You could also try setting the constant ACF_VF_DEBUG to true in wp-config.php which will load the non-minified javascript allowing you to set a breakpoint in the input.js file to see where it stops working – or perhaps there is simply a JavaScript error?

All done, pull request is here: https://github.com/rodrigoprimo/social-connect/pull/55

Thanks!

Yes. Choose Repeater for the parent field, then create sub-fields with a type of Validated Field and a sub-sub-field type of your choosing. For the field that you want to be unique choose Post Type & Key.

@koroikoroi – Firefox compatibility is fixed in 1.2.6 – no event object like Chrome/Safari. Thanks!

Errr… I mean version 1.2.5.1. Creating version tags does not always go as expected. Sigh.

@aboother – That is indeed the issue. Not sure why my system isn’t reporting the warnings/notices like yours, but I think I got them all in version 1.2.4. If you are still having issues with that version send me a note and I’ll have you try a beta version before pushing it out to everyone. Thanks!

@koroikoroi Version 1.2.3 will allow you to globally disable validation for Drafts/Preview by setting the ACF_VF_DRAFTS constant to false, or can be set per field in the field group configuration. The default behavior for drafts is to validate.

@aboother Version 1.2.2 fixes the alerts that you were seeing – it should now be properly associating the plugin version with the javascript includes.

Since you are getting lots of PHP notices, my guess is that something similar is messing up the JavaScript. After you update, can you use the developer tools in Chrome to get the request/response for the AJAX? This will work best if you set ACF_VF_DEBUG to true in wp-config.php so that it doesn’t use the minified version of the javascript and will ask you if you want to submit the form on success.

define( 'ACF_VF_DEBUG', true );

This might have been related to another issue – the plugin version wasn’t being passed to the javascript issue which could lead to the caching issue you saw. Version 1.2.2 corrects for this.

@koroikoroi both issues have been addressed in version 1.2.1.

1 – this was accidentally omitted when I refactored to support Repeater fields, the message you see is the default.
2 – updated UI javascript to display a notification at the top when the validation fails.

side note, corrected an issue where a form could validated by this plugin but fail the ACF validation resulting in an inconsistent data state.

@aboother Can you please upgrade to version 1.2 and give it another try? If you are still having issues please open a new ticket. Thanks!

@alfredmanchas, Version 1.2 should now support the Repeater Field containing Validated Field wrapped fields.

Thanks!

Jeez @jacobdubail and @koroikoroi, I can’t just enjoy my unemployment in peace huh ??

Version 1.2 should now support the Repeater Field containing Validated Field wrapped fields.

Let me know if you have any issues!