• davisshaver

• in reply to: Field group location rules – conflict on initial load
• December 5, 2013 at 2:59 am

This reply has been marked as private.

• davisshaver

• in reply to: Field group location rules – conflict on initial load
• December 4, 2013 at 8:49 am

Smart idea – ‘testing’ was in fact the default category. To test this theory, I switched the default category to one not represented in the above screenshots. Under this scenario, I expected field group B (the second screenshot) to appear on a new post. However, field group A still appears.

Would you be willing to access our development site and take a look? I can make an account if you are willing.

And thanks again. Seriously. Can’t believe this is free support. You should offer a tiered service! ACF has become really essential to our development efforts.

• davisshaver

• in reply to: Setting correct priority on publish_post action
• October 25, 2013 at 3:11 am

Thanks Elliot, just signed up. Looking forward to it.

• davisshaver

• in reply to: Setting correct priority on publish_post action
• October 23, 2013 at 10:43 pm

Didn’t realize that! I will use !wp_is_post_revision( $post_id ) to return out of the revision case. Thanks again.

PS Looking forward to conditional logic in repeater box. Happy to beta test if you need someone :).

• davisshaver

• in reply to: Setting correct priority on publish_post action
• October 23, 2013 at 3:49 am

It appears that this action is running twice when I publish a post. I used th following code as diagnostic and received two emails. Any idea what’s going on?

function dfm_hook_test() {
wp_mail( '[email protected]', 'Action run', 'ok' );
}
add_action('acf/save_post','dfm_hook_test', 20);

• davisshaver

• in reply to: Setting correct priority on publish_post action
• October 23, 2013 at 1:45 am

Thanks Elliot! Appreciate the help.