rnbutler87

Hi, thanks for the reply. The plugin I have installed is the latest version (1.6.6):

View post on imgur.com

The problem occurs despite this.

Hi, I’m using the Smart button option and please see below a link to the screenshots of the settings page:

View post on imgur.com

Many thanks

• This reply was modified 2 years, 10 months ago by rnbutler87.

Hi, this is good to know! You’re right, the message field was a bit annoying to target and since building that functionality I have installed ACF extended (primarily for the bidirectional functionality). So I’ll look in to the dynamic field now instead.
Thanks again!

Hi thanks for the heads up. I’m actually using the acf/prepare_field on page load to populate a ‘Message’ field and then using an ajax call to update that message.

Thanks again.

Hi thanks for the detailed response!

I’m reluctant to split the callback in to two, because they are doing pretty much the same thing. The difference being it’s called on page load and the then via AJAX when someone clicks a ‘verify’ button. The callback just decides if the call is coming from a page load of an AJAX call. So I don’t want to duplicate the code for the sake of a couple lines.

However, I have changed it so that the filter only gets run on certain admin post edit screens (ie. not ACF). And I’ve also changed it to acf/prepare_field, as per your suggestion, so thanks for that.

The bidirectional field is working great now so thank you for your help.

Kind regards,

Richard

• This reply was modified 4 years, 4 months ago by rnbutler87.
• This reply was modified 4 years, 4 months ago by rnbutler87.

Hi, I couldn’t edit my reply fast enough to say I’ve figured out what the problem is.

I have this filter running in the backend post edit screens:

add_filter('acf/load_field/key=field_5f0588503f494', 'post_edit_content_verification');

post_edit_content_verification is a callback function called on that filter and also as the callback in an AJAX action: add_action("wp_ajax_post_edit_content_verification", "post_edit_content_verification")

The ‘Woof Woof Woof’ is a response in the callback for a failed nonce verification…

I’ve now fixed the problem by only calling this filter on post edit screens of a certain post type. The select drop down now works correctly.

However I’m at the limits of my technical knowledge when trying to understand why my very specifically named function was being called by ACF Extended…

I’m glad it’s fixed but I’m eager to understand how the crossed wires happened.

Any light you can shed would be appreciated.

Many thanks.

I’ve looked at this again and when I click the bidirectional ‘select’ drop down, using Google console I can see the AJAX request is returning ‘Woof Woof Woof’, which suggests a nonce issue?

This is the form data being submitted in the request:

action: acfe/fields_settings/bidirectional/query
s:
paged: 1
field_key: acfe_bidirectional_related
nonce: 49aede077c
post_id: 557

Any help would be greatly appreciated.

Many thanks.

Brilliant, thank you.

No problem, thank you for being willing to fix it!

Hi thats great thanks!

I’ll email you now.

Many thanks,

Richard

Hi,

Thanks for the quick reply.

I can confirm that testing your demo page from the iPad2 and Galaxy tablet results in the images being loaded in a new tab rather than a lightbox. However the demo works fine using a desktop browser such as Chrome or my iPhone 6s chrome.

I can write a bit of javascript and I do find that I have to use bog standard ‘for’ loops (rather than ‘foreach’) to get vanilla code to work in these older tablets.

If there is anything that can be done to get this working again I’d be super grateful for the help.

Many thanks,

Richard

THANK YOU!
This works perfectly now! Thanks for your super speedy response and detailed reply. Quality plugin and quality support. Thank you again!

Ok thanks!

Hi thanks for the reply. I’ve tried this but there seems weirdness with class attribution. Even when I close the open tab (set to open as default) it still maintains it’s open class.

My theme has an accordion shortcode itself but I’ve added the config file code to try resolve this. Incidentally, I’m choosing to use a third party plugin so that I’m not fenced in to using a specific theme at some later date.

Hi thanks for the reply.
It was just something I thought could be done. No problem, I’m using the shortcodes now and looking great. Thanks!