Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
ACF Feature Request Voting
-
get_fields_group('group_name') // returns associative array. $fields_group = array('field_name' => 'field_value', ...);
<?php $fields_group = get_fields_group('group_name'); ?>
<?php if ($fields_group): ?>
<?php foreach($fields_group as $field_name => $field_value): ?>
<?php echo($field_name)?>:
<?php echo($field_value)?>
<?php endforeach; ?>
<?php endif; ?> -
There is a "taxonomy" field in the ACF addons, but this field is not working with repeaters and occasionally when multiple taxonomy fields are being used in the same post. It would be nice to have it fixed and/or eventually become part of ACF core.
Secondly, a Google Maps addon exists but it won't work inside taxonomy terms edit pages and breaks in some other cases (I think it doesn't work inside repeaters either).
I don't know if this is a coding issue within the addons or ACF core, but it would be nice if they get fixed. -
I would like to see a better threaded style support forum or stack exchange type site for ACF. ACF is a great tool that that I can only see getting better. I see tons of great comments and suggestions here but it is tough to follow what comment goes to what and what people are working on and not working on already. I already have created solutions to some of the things I see here and I am sure other people have too. There are other problems I would like to attack but I wonder if it has already been solved and the solution is somewhere within these pages of comments.
-
A column at the media-library displaying posts where an image ore file is used by acf-fields. May there can be an seperate media-library owned by acf.
-
== IMAGE default value ==
It would be nice to have a default value for the image field type. Sometimes there is an image not set yet, but it would be nice to see, what place it would take.
In my case I want to add a section seperator-image as a flexible content, so the client only has to add "Seperator" where he can use either the default seperator image given by default-value or he can upload his own image. -
UPDATE: Available since ACF 3.3.6
= Add post_id argument support to [acf] shortcode =
The [acf] shortcode for fields is missing the post_id argument compared to the regular get_field/the_field() API calls.
The patch below implements this while keeping this argument optional.
acf_add_post_id_argument_to_shortcode_3.2.8.patch.txt489B -
= Move source code over to github.com =
Moving the source to a public repository at github should improve the workflow of contributing from people and allow it to grow more rapidly.
There are many benefits for maintaining ACF as well by going that step.
A couple of ACF plugins are already maintained on github, too. -
I love this plugin it really helps on every website I do. I have made a repeater field with Layout row and have several input fields, image field, sub repeater fields and a WYSIWYG editor inside the repeater field, but as I add extra rows the meta box gets quite large, would it be possible to make repeater fields of Layout row collapsable.
-
= Add field[s] to Gallery images =
I'd love a way to add fields to Gallery images, similar to the Repeater Field. With that, for example, a URL could be added to images on a per-gallery basis, rather than attaching a URL to the image itself in the WP Media Library.
A close second would just be to add a URL field to images on a per-gallery basis ;) -
The shortcode feature is very useful, is impossible to use it for retrieve fields from the options page add-on.
I imagine the shortode work in this way
[acf field="field_name" options="true"]
or if is possible
[acf field="field_name" options]
so you use the "options" attribute to intend to retrieve the field from the options page, like in the other apis -
Great plugin!
Need to add a button to the Gallery field to add all the images at once its anoying to click 1 by 1 and waste a lot of time.
Thanks for this plugin. -
@loru88 try
[acf field="field_name" post_id="option"] -
@admin
great, it works, compliments for you work! -
I have a site where i used ACF. Now i want to send newsletter to clients. Clients are saved as post type with ACF fields attached. Clients has relation with other field from other post type.
I want to send newsletter to a client post type. Send newsletter based on conditions from fields values. -
It would be awesome to be able to re-arrange fields, this way you are not forced to use either a "table" or a "row" layout.
Good use example would be a section with a heading and three columns of text in a repeater field.
I would like the three columns to be in a table, but the heading to be in its own row above.
I'm not sure how difficult it would be, but hopefully thats something you may be interested in adding. -
== Date Field Stores Timestamp/Date Formats ==
This is something I currently do with action hooks in the functions file, but it would be great if there was an option to display date fields in the back-end using the format option as it is currently but have the dates converted to timestamps when they are stored as custom fields. This would make date comparisons a lot easier inside of queries (i.e. before pulling the data from the database)
Edit: As well as timestamps, maybe other date formats -
Relationship field - would it be possible to include the post type and/or date as per the regular Wordpress wysiwyg editor's insert/edit link button? As it stands, the possible links the relationship field throws up (even after limiting them in the Field Group editor) is very confusing and increasingly open to creating mistaken relationships (that one doesn't necessarily realise unless you are in the habit of checking every link you make from the front end (or have the time to)).
-
'Other' for 'select', 'checkbox' and 'radio button' fields. While I realise this would mean packing more into these fields than what their simplicity demands, it would be so smooth if 'other' could be chosen from the list of values these fields have been originally setup with so that (with the radio field especially), when selected, another input slot opens in which one can include a value not originally listed.
In a dynamic site, it is impossible to think of all the values one will need when setting up these fields.
Presently, I have to manually create this option by including a conditional (true/false) field with an extra text input field, in case the value I need is irregular and, hence, not listed. (i.e. if it is not listed I then tick the conditional and the new value listed in the text input field will come into play.)
This makes coding for a radio button field big and bothersome on my end, when it would be too smooth and exceptionally great if this big bothersomeness could be packed into the actual field, instead, and disappear. -
Date picker field: As I am generally including archival entries, the date for these entries are not just a few months back by which the monthly scroller of the date picker can easily be used, but years and years back. This makes the date picker impractical since, to pick the date 14 August 1992 you have first to scroll through every month of the twenty intervening years: 12 x 20 = 240 previous arrow clicks which = 'no way'.
It would therefore be most useful if as well as scrolling through months, one could also scroll through years. -
Maybe I'm griping because ACF's wysiwyg editor doesn't work on SHOPP pages - so all my other ACF bugbears have come out to play.
(Though don't for a moment doubt I think this is a terrific plugin and appreciate your continued attentiveness to it: an attitude I find inspiring.) -
= Password field with md5 SHA1 =
A field that can set and store password with md5 or SHA1 encryption to database. Probably use it for logging in custom pages/posts. -
Collapse/expand option on repeater rows.
That way if you have large fields in your repeater group (WYSIWYG etc) you could easily reorder rows that otherwise might be difficult to move (as they might be the height of the window or greater). -
= Option for post_parent in Relationship Field =
Would be great if I could check «Only Children of Current Post/Page» (or something along those lines) in the Relationship field. Sometimes I want the user only to choose from children of the page being edited. -
= Gallery/Image: force image size/ratio =
For the gallery/image field there should be an optional "force size" image-size validation mechanism. When images are uploaded using the gallery (/image) field and they do not match the required size, the border should get red and the post shouldn't be stored.
Our galleries almost always need images with specific sizes to match the layout, so this feature would be great! -
I've adjusted my own copy of the shortcode code so that I can get the url of images (since the shortcode returns an array for those, which is pretty much useless). It be great to see something like this as the default:
function acf_shortcode( $atts )
{
// extract attributs
extract( shortcode_atts( array(
'field' => "",
'post_id' => false,
'array_key' => false,
), $atts ) );
// $field is requird
if( !$field || $field == "" )
{
return "";
}
// get value and return it
$value = get_field( $field, $post_id, $array_key );
if(is_array($value))
{
$value = $value[$array_key];
}
return $value;
}
That's from line 443-470 in /core/api.php for anyone else who can use it. Then, in the shortcode call I do this:[acf field="picture" array_key="url"]
or, in it's entirety:<img src="[acf field="picture" array_key="url"]" />
-
Compatibility with Media Tags plugin for better image sorting.
Because Wordpress doesn't have very robust native Media Library organization, many WP websites with large image galleries use Media Tags to sort their images. Currently of all the available plugins, Media Tags seems to do the trick with the most benefits. The ONLY drawback is that ACF is not compatible with Media Tags image sorting when adding images to fields.
DETAILS OF THE ISSUE:
Currently when attempting to add images in an ACF row, the media uploader dialog box appears as normal. There is the Media Library tab which works just fine for selecting images, but on the Media Tags plugin tab when you select a tag to sort and find tagged images, the Select Image button disappears and you are not able to select any image for the field within the uploader dialog box. This happens right after Media Tags sorts and displays the selected images. In fact, you have to close the box and start over if you want to add an image in the field. Is there a work around to this? Thanks for any help or suggestions. -
@MPSwebdev - interesting. I'm sure its a very small conflict issue. I'll look into it and see if I can make them compatible.
-
add support WPML for "option page addon"
Actually, when you save values, you get the same values for each language -
Add support for "Option page addon" with WPML
Actually, when you save values, you get the same values for each language -
In the Location Rules, the same way you now have "Page Parent", could you add "Post Category Parent"?
-
== Easier Update of ACF when using custom options pages and/or fields ==
I'm not even sure this is possible.. I don't know the limitations of a plugin, but here goes:
Currently when updating ACF one has to temporarily go into the functions.php file to outcomment any calls to create a custom options page or if one has custom acf fields.
This would have to be outcommented in order for the plugin to update without errors:
<?php register_options_page('my options page'); ?>
If it's possible it'd be nice if this was sensed by the plugin and it did the trick for you! Obviously I understand that this is a small issue but when you use ACF on nearly every site you build it can be hard to remember what sites you have to do this for when updating.. It's a splinter under the nail but nothing more.. -
@tonytiger
If you wrap your register_options_page in a conditional you won't have to comment it out in order to update.<?php
if(function_exists("register_options_page")){
register_options_page('New Page");
}
?>
-
Default value on Color picker
-
== Required subfields within repeater ==
Subfields of a repeater really beg for an optional "required" state. -
Can we have a max count on the Gallery field like there is on the repeater, my clients are finding it too easy to use and uploading too many images!
-
For the flexible content field I would like to update order of the layouts, at the moment if I want to drop in a new custom layout option I can't insert it before existing layouts.
-
Ability to make Field Labels hidden.
When creating a custom field group (that only has one field), if you set the "Style" to "standard Metabox" you end up having two titles which can be redundant.
For example, a Gallery. The custom field group is called "Gallery" and then the actual field label is, respectively, "Gallery." You can see in the attached file it looks a bit odd.
Would prefer to just not have it at all, and keep the Field Group as the only title displayed.
There is a work-around: by just leaving the field label blank (still saves despite appearing as a required field) or just putting a space. Seems a bit hacky and it also still outputs the label which displays an awkward space
Screen Shot 2012-12-06 at 3.13.00 PM.png324 x 201 - 34K -
== Drag content between nested repeater fields ==
When you have a nested repeater say for categories of images and need to drag images and text fields between categories since it is nested, fields would match up. -
= Group Display of posts inside Relationship Fields =
Even though there is a search field, it would be a better experience pages and posts listed inside a relationship field could be grouped by category or by parent page. Sometimes page titles and posts may have the same name. It would be nice to be able to distinguish between them. This may require a new interface, perhaps a modal window that would allow for a larger list view instead of the small scrolling box. -
= ADMIN WYSIWYG Field =
A "reverse" field to fill information for the admin user, specially to provide some how-to and help on how the user should use the fields.
I mean "reverse" because at the Field Group edit screen we would get the actual WYSIWYG to fill information, and at the post/page/options screen we would see the HTML output.
This would be king to provide some guidance for my clients, and it would be even better if it plays well with conditional logic, repeaters, etc. -
– Include Taxonomy Add-On by default
– Make the Taxonomy Field select working with Conditional Logic (by value) -
There should be a way for acf-lite and acf-full to play nice with each other. Right now, if i want to use ACF to create an options page for my plugins using acf-lite, and a user is using acf on his site, everything breaks.
Maybe have acf-lite detect if the plugin is activated and have it disable itself. That way, if a user has acf installed no plugins that use acf will break.
Is this possible?
