doublesharp

Thanks @askjoo – I do my best ??

Your use case sounds very similar to mine. Hoping to get some more advanced functionality added soon, thanks for the review!

The code required a bit of tweaking to get this to work. I’ve updated the code so that all of the JavaScript is loaded at the bottom, but I had to make a few changes so that the masking code (for example) doesn’t execute until the DOM is ready.

I’m working on some updates for the 2.0 version of the plugin so just incorporated these changes there. You can download a beta to try out from here, and let me know how it is working for you: https://www.dropbox.com/s/o775s22b7ewyun7/validated-field-for-acf.zip?dl=1

So you are aware, the biggest change outside of cleaning up the coding and adding some filters/actions is the support for validation User meta fields in addition to Post metas and Options.

I will mark this as resolved as it will be included in the next release.

Thanks!

@skarck, I don’t see any reason why that would be a problem. Did you make the change and test it out by any chance? The code is relatively small and only loads on the admin (unless you tell it to on the front end, which isn’t as standard) so performance for hasn’t really been an issue, but improvements are always good.

J

Thanks for your review @!dianalbert. If you have any issues or questions please let me know.

That’s great to hear @mazinger, thanks for the review!

You’re welcome @antongorodezkiy, thanks for the review!

Oops, I misread your message. The Validated Field plugin only works with ACF fields, which in turn are meta fields. The title, content, etc are not meta fields and are stored on the post itself and this don’t go through ACF, so this plugin won’t provide validation.

That said… I do this on some of my sites by hiding the non-meta fields (like title), use a “title” meta field through ACF, then use a hook on the action indicating the meta field has been updated to change the “real” value on the post. Works well for me so far, and I hope to add this functionality at some point in the future.

If there are specific things you are looking for please let me know so I can prioritize them. I’m also considering adding some as “premium” features, still tbd.

Thanks again!

I’m not familiar with the other plugin you mentioned, but this is certainly the one I would use ??

There’s a difference between making a field required and validating its contents, so it ultimately depends on your requirements.

Good luck!

Hi @bkno – Post Type would ensure that the value is unique regardless of which meta_key it is stored under (maybe some kind of GUID?), whereas Post Type + Field/Meta Key will apply the uniqueness to a particular field (useful for things like phone numbers). If you use the latter, you could have the same value stored under different meta keys, but set to be unique for each meta key.

The third option you didn’t mention is Post + Field/Meta key which behaves like the other that includes the meta_key, but instead of making it unique for the post type it applies the uniqueness per post. This is useful for some field types where you are allowed to select multiple values.

Hope that helps!

Great, I’ll mark this as resolved for now, if anything changes just post an update and I will reopen the issue. Thanks!

@jeffreyd000 I’ve not been able to verify this bug. Can you let me know what version of WordPress, ACF, and Validated Field you are using?

Thanks!

Thanks for researching this issue. The naming conventions within ACF have changed over the years so it wouldn’t surprise me if they are out of sync. I will looking into getting this resolved as quickly as possible (I’ve been away from my computer for the last week and need to catch up on some things).

Sorry you are running into trouble, hopefully we can get it fixed quickly.

J

Yes, and if you look at the output you have 5.2 not 5.4:

Current PHP version: 5.2.172.0

The latest version of the plugin should work for you, but again I would recommend running something newer on you Web server.

The web server must be running an older version or you wouldn’t see the json_encode() error, the second argument was added in php 5.3.

Ah the options were added in PHP 5.3. I just tagged version 1.7.7 of the plugin to check the PHP version and conditionally handle the debug options for json_encode().

That said, I would recommend upgrading to a newer version of PHP. It will be a lot faster and use a lot less memory.