Advanced Custom Fields
Welcome to the official repository for Advanced Custom Fields WordPress plugin.
Hi Elliot,
Just updated to v4.1.5.1 using latest version of WP. Timepicker fields (timepicker only) are now not saving the data.
Datepicker fields fine.
I'm attempting to use a the post object field type using ACF 3.5.8.1 on WP 3.5.1 and getting a Catchable fatal error: Object of class WP_Post could not be converted to string ... /core/api.php on line 203. Relavant screenshots below:
Previously, to add an Add-on we used the function register_field.
http://www.advancedcustomfields.com/add-ons/users-select-field/
For backward compatibility, wouldn't it be better to maintain it? As it seems the method has changed:
http://www.advancedcustomfields.com/resources/tutorials/creating-a-new-field-type/
[Update]
I'm seeing that the class to add a new field is very different... Suppose that rewriting the premium add-ons required that... So, maybe it's unavoidable having to rewrite all user add-ons.
When you choose a single-element "Select" in Taxonomy field,
in the edit post page actually it turns out as "MultiSelect" style.
Hi,
I'm using ACF 3.5.8.1 with WPML 2.6.4.1 on WP 3.5.1 (all latest stable versions).
I was getting crazy with some fields in a post in a second language (English): each time I updated the post it didn't store the entered data.
I haven't made the ACF group translatable since I need to call it once in single.php and don't need different fields for different languages.
I've enabled debugging but didn't get any helpful message.
Then I've noticed that in the third language (French) the ACF contents were correctly displayed.
The posts in the third language are duplicated from the posts in the second language (I don't need to trnslate the posts in French, so display the English ones).
I've clicked on “Translate it separately” and in this way I was able to update the post without losing my data also in the second language.
Don't know the reason of this behavior, hope this could help fixing for next releases.
I'll write the same on WPML support.
It is currently not possible to have a tab within a repeater field.
It was a great disappointment to me that I could not add a tab as an item within a repeater field.
I was planning on using it for a bus timetable based system where one tab would denote one day of the week. There would be additional tabs added by the client as and when they needed them (i.e. for special services at Easter, Christmas etc).
Any plan to add this as a feature to the repeater field?
I see that you have commits referencing stable version numbers—thank you for that. It might be prudent to take that a step further and tag those commits, to ease checking out specific versions (so you don't have to search through the commit log to find the desired SHA reference).
I got a ACF for a specific category which I now separated in different tabs. Everything working fine - except that every tab is displayed double in the post editor.
inserting following line fixed it for me:
$post = get_post( $options['post_id'] );
Hi,
when making an option page / taxonomy field with a long name, the database truncate automatically the option_name field to 64 chars.
This appens when there is repeater on flexible content with names like this :
"_category_3_flexible_sidebar_1_flexible_sidebar_questions_0_flex"
I don't know how you can prevent this, maybe a warning for the user or a chars counter on option pages ceation or taxonomy/term.
For the taxonomies you can use a plugin process like Meta for taxonomies https://github.com/herewithme/meta-for-taxonomies this will prevent cases like this and use the WordPress API :).
Rahe
Running WP v3.5.2-alpha, which could be contributing to the issue.
Getting this when exporting php. After replacing "1array" with "array", it works fine.
See fields:
field_515b29ff36c42field_515b2a20b9a1bfield_515b2a31b9a1cfield_515b2a46b9a1dCode:
/**
* Install Add-ons
*
* The following code will include all 4 premium Add-Ons in your theme.
* Please do not attempt to include a file which does not exist. This will produce an error.
*
* All fields must be included during the 'acf/register_fields' action.
* Other types of Add-ons (like the options page) can be included outside of this action.
*
* The following code assumes you have a folder 'add-ons' inside your theme.
*
* IMPORTANT
* Add-ons may be included in a premium theme as outlined in the terms and conditions.
* However, they are NOT to be included in a premium / free plugin.
* For more information, please read http://www.advancedcustomfields.com/terms-conditions/
*/
// Fields
add_action('acf/register_fields', 'my_register_fields');
function my_register_fields()
{
//include_once('add-ons/acf-repeater/repeater.php');
//include_once('add-ons/acf-gallery/gallery.php');
//include_once('add-ons/acf-flexible-content/flexible-content.php');
}
// Options Page
include_once( 'add-ons/acf-options-page/acf-options-page.php' );
/**
* Register Field Groups
*
* The register_field_group function accepts 1 array which holds the relevant data to register a field group
* You may edit the array as you see fit. However, this may result in errors if the array is not compatible with ACF
*/
if(function_exists("register_field_group"))
{
register_field_group(array (
'id' => 'acf_options',
'title' => 'Options',
'fields' => array (
array (
'key' => 'field_515b28a209b94',
'label' => 'Top Bar',
'name' => '',
'type' => 'tab',
),
array (
'key' => 'field_515b28cb09b95',
'label' => 'Content',
'name' => 'topbar_content',
'type' => 'text',
'default_value' => '',
'formatting' => 'html',
),
array (
'key' => 'field_515b28df09b96',
'label' => 'Link?',
'name' => 'topbar-link_select',
'type' => 'select',
'choices' => array (
'none' => 'None',
'page' => 'Page or Post',
'custom' => 'Custom Link',
),
'default_value' => '',
'allow_null' => 0,
'multiple' => 0,
),
array (
'key' => 'field_515b291883261',
'label' => 'Page or Post Link',
'name' => 'topbar_link',
'type' => 'page_link',
'conditional_logic' => array (
'status' => 1,
'rules' => array (
array (
'field' => 'field_515b28df09b96',
'operator' => '==',
'value' => 'page',
),
),
'allorany' => 'all',
),
'post_type' => array (
0 => 'post',
1 => 'page',
),
'allow_null' => 0,
'multiple' => 0,
),
array (
'key' => 'field_515b295b83262',
'label' => 'Custom Link',
'name' => 'topbar-custom_link',
'type' => 'text',
'conditional_logic' => array (
'status' => 1,
'rules' => array (
array (
'field' => 'field_515b28df09b96',
'operator' => '==',
'value' => 'custom',
),
),
'allorany' => 'all',
),
'default_value' => 'Please include http://',
'formatting' => 'html',
),
array (
'key' => 'field_515b29a34050a',
'label' => 'Homepage Hero',
'name' => '',
'type' => 'tab',
),
array (
'key' => 'field_515b29b54050b',
'label' => 'Heading',
'name' => 'hero_heading',
'type' => 'text',
'default_value' => '',
'formatting' => 'html',
),
array (
'key' => 'field_515b29bf4050c',
'label' => 'Content',
'name' => 'hero_content',
'type' => 'textarea',
'default_value' => '',
'formatting' => 'br',
),
array (
'key' => 'field_515b29c74050d',
'label' => 'Button Label',
'name' => 'hero_button_label',
'type' => 'text',
'default_value' => '',
'formatting' => 'html',
),
array (
'key' => 'field_515b29e54050e',
'label' => 'Button Link',
'name' => 'hero-page_link',
'type' => 'page_link',
'post_type' => array (
0 => 'post',
1 => 'page',
),
'allow_null' => 0,
'multiple' => 0,
),
1array (
'key' => 'field_515b29ff36c42',
'label' => 'Hero Sidebar',
'name' => '',
'type' => 'tab',
),
1array (
'key' => 'field_515b2a20b9a1b',
'label' => 'Content',
'name' => 'hero_sidebar_content',
'type' => 'text',
'default_value' => '',
'formatting' => 'html',
),
1array (
'key' => 'field_515b2a31b9a1c',
'label' => 'Button Label',
'name' => 'hero_sidebar_button_label',
'type' => 'text',
'default_value' => '',
'formatting' => 'html',
),
1array (
'key' => 'field_515b2a46b9a1d',
'label' => 'Button LInk',
'name' => 'hero_sidebar_link',
'type' => 'page_link',
'post_type' => array (
0 => 'post',
1 => 'page',
),
'allow_null' => 0,
'multiple' => 0,
),
),
'location' => array (
'rules' => array (
array (
'param' => 'options_page',
'operator' => '==',
'value' => 'acf-options',
'order_no' => 0,
),
),
'allorany' => 'all',
),
'options' => array (
'position' => 'normal',
'layout' => 'no_box',
'hide_on_screen' => array (
),
),
'menu_order' => 0,
));
}
In your recent patch 4.1.5.1 you removed the option for radio field to contain '0' (zero) values.
I think what you wanted to accomplish here is to have no EMPTY values.
The problem is our radio fields contain '0' en '1' as a value. But since '0' is no longer possible it will select the first value it finds, in this case it's '1'. The stored values are not integers, but strings. This how ACF stores the values; as strings.
To replicate make a radio button field and fill the choices with:
1 : Yes
0 : No
This fix should be easy:
File radio.php @ line 59 change the following:
if( $field['value'] !== 0 && !$field['value'] && $i == 1 )
to:
if( $field['value'] != 0 && !$field['value'] && $i == 1 )
This will allow both values: 0 (int) and '0' (string).
Hope you can use this in your next update.
This is simply something to look into, and potentially still a bug. I'm not using the current version that's here on Github, but the lines I'm referring to appear to be the same in the version that I do have running.
The situation is I have two ACF forms on the same page. They're used for submitting different post types, and I just toggle which one is shown.
One of the forms (2nd one loaded) uses 2 relationship fields. The issue was that these fields weren't being populated with any data. The Ajax loader was spinning, but nothing would happen. After some digging, I found that the Ajax calls weren't even being hit.
https://github.com/elliotcondon/acf/blob/master/js/input/relationship.js @ line 24
The "postbox" variable contained only the first ACF form that loaded on the page, and therefore it wasn't finding that ".acf_relationship" element within it (since it's in my 2nd form).
How I'm getting around it for now:
$(document).live('acf/setup_fields', function(e, postbox){
postbox = $('.acf_postbox'); //new
$(postbox).each(function(){ // new
$(postbox).find('.acf_relationship').each(function(){ // and continue as normal
And now it's working as intended :)
Edit/update: also note that the frontend Ajax call wasn't working for the relationship fields when you weren't logged into the backend: was returning 0. I added the "nopriv" action below where the main one was enqueued, and it works both ways, now.
When selecting more than one page in a select post-object field in a page:
Warning: htmlspecialchars() expects parameter 1 to be string, array given in /homez.10/litup/www/wp-content/plugins/acf4-master/core/fields/post_object.php on line 341
I'm unable to reproduce this in a stand-alone environment, but I encountered this a few times on sites I manage.
The problem appears to be after an update. It may be a problem with WP's plugins_url.
Upon loading the post editor, some scripts and styles fail to load because the full filesystem path is being injected into the URL. This poisons $this->dir in acf.php and causes the enqueued resources to 404.
Possibly Related:
https://github.com/elliotcondon/acf-lite/issues/4
A hacked solution for me was to change:
https://github.com/elliotcondon/acf/blob/master/acf.php#L53
- $this->dir = plugins_url('',__FILE__);
+ $this->dir = plugins_url(basename(__DIR__));In WordPress 3.5, they introduced a few more hooks on the edit screen. Specifically, edit_form_after_title, which shows up between the title and the editor. This is a perfect hook for things like Subtitle and other fields you want shown before the main editor.
More info: http://make.wordpress.org/core/2012/12/01/more-hooks-on-the-edit-screen/
Would it be possible to add this as an optional area for ACF metaboxes?
Hi @elliotcondon
I was experiencing a strange issue, I hope you can help me.
It's kinda weird, and I got some time before to understand and replicate it.
I manage all my categories and taxonomies with ACF, removing the standard panels with remove_meta_box function and not with the plugin (since ACF currently allows only to hide default 'category' meta box and not the taxonomy ones). This is the final result:
It works perfectly, except for a strange bug I experienced: I keep the "edit post" page opened in a tab in the browser, while surfing the preview in another one and making some code changes (to CSS or PHP template files). After a while, when I refresh the preview page, the post became set with the default category. If I go back to the "edit post" page and press "Update" button, the post turn back to the category I set initially. Then after a while it happens again. But I noticed that if I close the "edit post" page tab, it doesn't happen anymore, so I thought it could be related to the Auto Save. What do you think about?
I noticed also that if I refresh the "edit post" page, the ACF category displays the default category as set on that post, not the one I chose before. Just to be precise: this happens only with Drafts post, the published one aren't affected (I suppose because the right category is yet stored in the database). The Pending Review seems not to be affected too. Hope to get your feedback soon. Thank you very much, P.
I discovered this issue with 3.5.7.2 so if it has been addressed please disregard. When upgrading from v.2 to v.3 (specifically v.2.1.4 to v.3.5.7.2) I've noticed an issue with WYSIWYGs in Repeaters. After initially upgrading, the "Add Row" button doesn't seem to be triggering whatever method renders the WYSIWYG in place of a standard textarea. The result is that any WYSIWYGs that are on the page when it is initially drawn render and function correctly, but any added to the screen after page load is complete with the "Add Row" button are not rendered as WYSIWYGs.
The quick work around for me was to simple re-save all of my field groups.
This is just an enhancement proposal.
When the user add custom taxonomies to post type, they appear like tags or categories boxes on edit post page.
If the user will use ACF to manage Taxonomies, he probably would like to hide their respective default boxes.
So, it would be a nice addition to include custom taxonomies to "Hide on Screen" options in Edit Field Group page (such as the current Categories and Tags).
Conflict with WP featured image
When I add an image custom field to any kind of post, page or custom post type, and I try to choose the image from the admin panel, nothing happens.
In the developer tools's console this is what appears:
Uncaught TypeError: Cannot read property '_views' of undefined - input.php:1215
I'm using WP 3.5.1 and this happens both with the stable and the github version of the plugin.
Don't know if this is a know issue or something on my end but I get this code at the top of my screen after activating Flexible Content. I'm using version 4.0 beta. It doesn't show code on stable version
ck if layout still exists if( isset($layouts[ $layout ]) ) { // loop through sub fields if( is_array($layouts[ $layout ]['sub_fields']) ){ foreach( $layouts[ $layout ]['sub_fields'] as $sub_field ){ // update full name $key = $sub_field['name']; $sub_field['name'] = $field['name'] . '' . $i . '' . $sub_field['name']; $v = apply_filters('acf/load_value', false, $post_id, $sub_field); $v = apply_filters('acf/format_value_for_api', $v, $post_id, $sub_field); $values[ $i ][ $key ] = $v; }} } } } return $values; } } new acf_field_flexible_content(); ?>
It appears that stale cache entries are not invalidating properly when new field groups are saved. My initial field group saved to the cache, and subsequent field groups never were added to the cache value. This means that they won't appear at all when editing posts.
The problem was resolved when I manually removed line 65 of field_group.php long enough for the cache to reset to the proper values. But the cache should be reset anytime a field group is saved or updated, and this doesn't appear to be happening.
I am using WP 3.5.1, ACF 4.1.0 and WP object caching with the memcached plugin.
It would be good if the sub fields of a flexible content layout could have the option to be required.
For options, it's a good practice to create a single option and store all your data in there as a serialized array rather than to create an option for each one.
Is adding an option on how the data is stored on the roadmap?
Having a wierd issue where when creating a relationship field after clicking update the entire group gets deleted without warning with all the fields...
I went back and recreated it and it was fine, went to edit the group again adding another relationship field and the same thing happened... everything is gone... no idea if it went into trash as there is no trash filter that I can find...
For some reason, any URLs enterer into a plain text or text area custom field are not detected and formatted by the "Auto-hyperlink URLs" plugin. Text input into the WYSIWYG area are. Any ideas how I can remedy this? I'd prefer to use the simpler fields.
I'm attaching a screenshot here, but the checkbox field doesn't seem to be working... all I got was a list of fields without a checkbox... only when I selected true/false I got a checkbox but then it was wrapped to the next line... shouldn't a checkbox show a checkbox input?
Running Version 4.0.0 ACF, Version 3.5.1 WP, on wpengine.
A few items do not update while caching is enabled, everything seems functional when it is disabled.
Here are the items I noticed affected
-- Field Group Ordering
-- Field Name
:)
Thanks again!
It is not currently possible to have a conditional field within a Repeater field.
It would quite often be very helpful to have this option. Are there any plans to add this as a feature?
Hi Elliot,
I have a problem with the import / export fields.
After exporting my php fields,
I set in draft my fields in ACF.
But it shows me only one field on all exported.
I wanted to re-imported and only 1 field is re-imported.
Is this a problem already raised?
Thanks
I have hit a wall...
I have a Flexible Content field named content_sections
The section that contains my relationship field is named featured_panel
The Relationship field name is featured_items this is set to any for the post types.
I am trying to use get_posts to loop through any post type and find the posts/pages that have the meta_value of the page that I am on so it will display my related items. I have tried numerous variations to get this to show something, but I keep getting an empty Array.
global $post;
$args = array(
'numberposts' => -1,
'post_type' => 'any',
'meta_query' => array(
array(
'key' => 'featured_items' ,
'value' => $post->ID,
'compare' => 'LIKE' ,
)
)
);
$posts_array = get_posts( $args );
if( $posts_array ) {
foreach( $posts_array as $related ) {
echo '<div>' ;
echo '<a href="' . $related->guid . '">' . $related->post_title . '</a>' ;
echo '</div>' ;
}
}
This returns nothing... I have tried changing the post_type to page or anything else... no go.
Thoughts??
When switching between tabs, any fields that were originally hidden by conditional logic are showing up.
Hi guys.
Please note that there is a support forum for any questions about ACF here:
http://support.advancedcustomfields.com/
Please only post issues here if you have found a bug / error and have code to reference
So I add the following to the acf/createFields function any is there a better way if not could this be added? could also add helper methods to simplify calls.
If this works for everyone I can send you a pull request.
//...
$field['name'] = 'fields[' . $field['key'] . ']';
// allow for lookup of date in $_POST prior to initial save and update.
$acf_field_name = str_replace('acf-field-','',$field['id']);
echo '<input type="text" value="'.$field['key'].'" name="acf_field_names['.$acf_field_name.']">';
do_action('acf/create_field', $field);
//...Example usage:
add_filter('title_save_pre', 'post_type_save_title');
function post_type_save_title($title_to_ignore) {
$title = $title_to_ignore;
if ($_POST['post_type'] == 'post_type') :
$fullname = $_POST['fields'][$_POST['acf_field_names']['first_name']] . ' ' . $_POST['fields'][$_POST['acf_field_names']['last_name']];
$title = trim($fullname);
endif;
return $title;Hi Elliot, big fan of your work.
One suggestion: would you consider using Chosen (http://harvesthq.github.io/chosen/) for selects? Some selects can end up being very large on big sites and adding chosen would provide a better user experience. The post-item field is a good example as sites may have hundred of posts. I'd also suggest using tags in this instance.
Cheers
The site inform to follow the link received in email response of purchase, but I bought before the version 4 and just have the serial number.
How to download the Gallery Addon?
Thanks.
Several times I have come across the need to create a metabox with "Reminders" or "Tips" for the person editing a post. It would be awesome to be able to create a "blank" metabox for me to type anything in. It would accept no values from the end user or be used in any way except to display information on the post-edit page or options page if using that add-on.
Thanks!
Since the taxonomy creates a select list/checkboxes/radio buttons, it would make sense to allow conditional checks on it.
Warning: Missing argument 4 for acf_everything_fields::delete_term() in ...plugins\acf4-master\core\controllers\everything_fields.php on line 663
I am deleting tags/categories in bulk via wp-admin default GUI. It issues warning with every term.
I only have the base ACF v4.0.0 installed
After importing XML file via Wordpress Importer, option "acf_next_field_id" wouldn't be increased and if I'll add another field after importing, this field will get wrong index.
Because of that, values wouldn't be saved to this new field.
Dirty method: I recommend you to hook "import_end" action and update "acf_next_field_id" on this event.
get_field() method tries to read/write cache using 'acf_get_field_' . $post_id . '_' . $field_key statement as a key.
But in the middle of a function $field_key could be changed at lines 136, 141, 145 (v3.5.6.3).
In this case, the value is saved with the wrong key, and will never be readed.
You need to save original $field_key parameter value.
p.s: In my case function tries to read cache with key 'acf_get_field_options_homepage' but writes with a 'acf_get_field_options_field_25'
If ACF fields are for a specific category the fields are displayed after selecting the category - but the tabs are not there. Only after setting the title for the post and saving the post the tabs are displayed.
It would be better to see the tabs right after selecting the category.
Thanks
Here's a screenshot of the two editors problem I get.
Here's browser version info.
It is sometimes accompanied by this error in the console, but not always. It may not be related.
I've seen a couple comments over on the WordPress forums about this. Let me know if I can do anything to help with testing.
Hi. Thanks for the plugin and your hard work! I'm experiencing an issue with loading this plugin when SSL is forced (enabled) in the Admin interface. Essentially the helper function helpers_get_dir() is using WP_PLUGIN_DIR to obtain the url. However there's a known issue with building URLs this way, see this open ticket.
Plugin authors are encouraged to use this technique to obtain the URL.
Any chance that can be refactored a bit to support SSL? Thanks!
Since the ACF update this past week, our entire website is having CSS and element alignment issues associated with the plugin. We have a subtle parallex effect on our home page that is being affected on larger monitors. For example, the more you zoom out (or the bigger the monitor), the background images are shifting to the right, being cut off, and the entire width diminishes. Any CSS or code changes does not change this. There are height and width problems as well that are fluid, or have a 100% width attached.
Absolute and fixed positions were also affected but I was able to adjust the CSS on most elements to correct the issues.
I haven't checked internal pages on the admin for ACF data errors themselves since I'm seeing other people having problems. So far the data being reflected on the actual website is correct, so I don't want to risk causing further problems.
Any assistance or feedback is greatly appreciated. I've included a screenshot of the alignment problem on larger screens.
http://www.fullcircledesign.co
The readme lists 3.0 as a minimum requirement, but the wysiwyg field calls wp_editor() on line 82, which has only been around since 3.3.
The upload is successful -- the attachment is created in the WP database. However it errors-out when trying to create the linkage. Here's the database view:
...it was successful in saving "saxophone" to a field named "butt" however no data from images save. I've tried "Image Object" "URL" and "image ID" with the same result
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.
