Yeah, it’s not a great doc.
In your options array, you would format it like this: 'fields' => array('key_123', 'key_321'),
You can find the key for your fields by going to the admin screen for where you edit the fields and click “Screen Options” from the top right and select “Field Keys”. That will show you the key for each field.
Here’s a nice graphic that shows it: http://thestizmedia.com/show-field-keys-acf-pro/
Not that I can see, but you can specifically include certain fields, which can be cumbersome but works for now.
https://www.advancedcustomfields.com/resources/acf_form/
I hope this actually happens soon! However, if it does, I would caution the developers to try an make it backwards compatible with the current plugin’s (date and time picker) data and values that it saves so that if we want to switch to the ACF core version we can easily do so without losing values from the old field.
+1. Never thought of this, but it would be great to have.
I know this is old and possibly unmonitored, but did this ever get added in?
Also, note this thread, which seems to imply there might be a core fix for this in the near future.
https://core.trac.wordpress.org/ticket/31383
Interesting. I hadn’t dug into the code, but this seems like it’s the problem. Hopefully someone at ACF sees this and can do a bug fix!
I know this is an old post, but I am facing the same bug. Any change this could get a fix soon?
Hey Elliot, was this issue ever successfully resolved? I’m getting into my first Buddypress project and trying to scope out what plugins I should use for what fields.
Thanks!
z
Excellent, that’s great news!!
Just a thought re-reading this, but could it be a toggle in the screen options sort of like the field id so it’s only there when needed?
Apologies if you’ve already tried this stuff.
I would try completely uninstalling and then reinstalling the whole plugin. I’ve updated to the latest version and nothing like that is happening. Uninstalling won’t delete the data within the fields, so you won’t risk losing work (although I would still do backups, just in case, as always). If that doesn’t fix it, the new update might have caused a conflict with another plugin you have installed. Try turning them off one by one and see if that corrects the problem and then let Elliott know here in the forums that there is a conflict.
Hopefully that helps.
(not the plugin author)
Confirmed, happening on mine after update as well. No functionality lost, just a minor css bug.
I was having this issue as well. Removing and reinstalling from a new download solved the tab problem for me, thanks Elliot.
However, the taxonomy field as a js select box if still not behaving right. Similar to this issue: http://support.advancedcustomfields.com/forums/topic/tax-relationship-failed-with-select-box/
I was able to discover what was wrong finally. Another custom post type I hadn’t converted was preventing post creation. Thanks!
That was the problem indeed, it turns out. The ID of the field was changed, I think, when I upgraded.
Still trying to figure out why the new_post isn’t working in this installation. I’m using the exact code on both sites for creating a new post, but no luck on later one. I’m guessing it’s something I haven’t found in my own work though, so I’ll keep looking. Thanks Elliot!
$newapp = array (
'post_id' => 'new_post',
'new_post' => array(
'post_type' => 'appointment',
'post_status' => 'publish',
'post_title' => 'tempslug',
),
'field_groups' => array('414'),
'form_attributes' => array (
'id' => 'new-app-form',
),
'submit_value' => 'Post Appointment',
'update_message' => false,
'return' => add_query_arg(array('adminTab'=>'apps', 'sub-tab'=>'available', 'appcreated'=>true), get_the_permalink()),
);
acf_form($newapp);
That’s awesome, thank you!
FYI, Version 5 has this functionality built in via the acf_form function now. You can create new posts, including title and content, from the front-end without custom functions.
Check it: http://www.advancedcustomfields.com/resources/functions/acf_form/
Oh, and I just noticed the new front-end validation! AWESOME.
@sethta, the idea for adding a class to fields is awesome. +1 for that.
