@fatsoma thanks for the update! This definitely fixes one of my ACF pet peeves.
The docs are still incorrect thou. The code example should say $row = get_row(TRUE); rather than $row = get_row(); because $format_values defaults to FALSE.
James, it helps a lot, thank you. So much so that I packaged your code and created a plugin out of it so that people can use it more easily. It is available from GitHub here. (Tried to submit it to wordpress.org’s plugin directory but was told they do not take any framework plugins anymore.)
Thanks again!
@acf-support thanks for your reply but I’m not sure you took the time to read my post. I think both myself and @emrl meant that we would like to see the ability to have two separate title fields: one that is used on the field group list and a separate one for the WP metabox.
Not sure how I can describe it more specifically.
Just in case someone stumbles across this in 2017 onwards: it turns out that contrary to what is stated in the docs for get_row() and the_row(), both functions return arrays keyed by field internal names and not field user defined names. So you will get:
Array
(
[field_5855ac26cb153] => 'John'
[field_5855ac26cb154] => 'Smith'
[field_5855ac26cb155] => 31
)
…instead of:
Array
(
[name] => 'John'
[surname] => 'Smith'
[age] => 31
)
…as the docs would have you believe. This makes both functions more or less useless for the end user. It has been raised with support back in September that either both functions should return arrays keyed by field names or the docs should be changed as they are misleading. Neither has been done.
@acf-support contrary to @emrl I think the addition of the Description field did not fully take care of this 🙂 I mean that with a lot of custom field groups it helps to somehow group them by name (eg. ‘<template_name> Functionality’) so that the custom field group list is a little easier to navigate.
But these group names do not look great when displayed on the actual page/post edit pages with metabox headers to the tune of ‘Homepage Template — Contact Us Section’ and ‘Options — Translations — For Email Use’ (options plugin). It’s usable but not 100% professional from a client’s perspective.
To sum up: would love to see the ability to define metabox titles separately.
