Support

function get_acf_labels($name = null) {
	global $wpdb;
	
	// Query DB to find either a single row or all acf field names and labels
	$fields_table = $wpdb->prefix . "acf_fields";
	if ($name) $fields_query = "SELECT name, label FROM $fields_table WHERE name = '$name'";
	else $fields_query = "SELECT name, label FROM $fields_table";
	$records = $wpdb->get_results( $fields_query );
	
	// Sort results into associative array, using field name as key for label values
	if (sizeof($records) > 0) {
		foreach ($records as $record) {
			$labels[$record->name] = $record->label;
		}
		return $labels;
	} else return false;
}

function acf_values($content) {
	// get values from ACF api, field labels from custom function
	$fields = get_fields();
	$labels = get_acf_labels();
	
	// if succesful, output list of values with field labels
	if ($fields && $labels) {
		$content.= "<ul class='acf_values'>";
		foreach($fields as $name => $value) {
			$label = $labels[$name];
			$content.= "<li><label>$label</label> $value</li>";
		}
		$content.= "</ul><!-- end acf_valus -->";
	}
	return $content;
}
add_filter('the_content', 'acf_values');

function get_field_label($field_name,$post_id = false)
{
	global $post, $wpdb; 

	if(!$post_id) 
	{ 
		$post_id = $post->ID; 
	}
	
	$query = 'SELECT meta_value FROM wp_postmeta where meta_key = "'.get_post_meta($post_id,"_".$field_name,true).'"';
	
	$field = unserialize($wpdb->get_var($query));
	
	return $field['label'];
}

Is there any update to this? I use the Headway Theme in combination with Loopbuddy.

I just can't get the field label to show, no matter what I try, all I can get to display is the ugly field name.

Utter misery that I find myself in. The only way I can display the field value is by using hard coded labels, that always display regardless of the custom fields that exist.

The biggest problem I have is that I'm unable to display a list of different information under the same label.

I can do it by using the WP built-in custom fields, but in Headway and with Loopbuddy, the line breaks are not respected, so if there are multiple values they all show in a row (no wpautop)

Trying to use html in the custom fields doesn't work.

ACF solves the line break problem, but it doesn't allow me to show the labels, only the names in their ugly_name_format rather than their Ugly Wart Diameters.

It is possible to use CSS to set widths on divs or spans, but it limits the length of the field labels for the purposes of alignment.

Since it is Headway and Loopbuddy, I am not able to edit the template files as such, or at least not with my current knowledge.

What I don't understand, is that when using the built-in custom post fields the Labels display fine. Why not so with ACF? Is there a reason we are being forced to use the names_with_underscores and no CAPITAL Letters or spaces?

I'm desparate :(

Thanks Eliot, I already know what the label is. What I am trying to say is that by using the Wordpress Framework I am currently using, I do not appear to be able to display this information on the page. All I can get is:

rug_sizes

when what I want is

Rug Sizes

I tried ACF some months ago in the hope of finding a solution to the problem, but it v3 was the same, as is the problem with every single fields plugin out there.

The only thing that works is the built-in WP custom fields, because this appears to not force me to create field names in lowercase letters and underscores, but the problem is it refuses to accept any wpautop filters, so if I want a field to accept multi-row data I have to wrap it in a div and use css margins to get everything to line up nicely.

This limits the length of the field names above and below.

What I can't find an answer to anywhere, is why this is happening.

The framework I use is called Headway, which does not use templates in the same way as ordinary themes, and the way I am formatting the display of posts is through a plugin called loopbuddy.

The problem appears to be between Loopbuddy and ACF (and all other existing fields plugins), but they refuse to answer my questions, and nobody else seems to know either. It has turned out to be one of the most frustrating things of my development career to date.

Guy