使用Advanced Custom Fields（meta_key/meta_value）获取自定义文章遇障求助

First, let’s walk through common fixes for your ACF meta query problem—this is a super common snag, so we’ll get it sorted out.

1. Verify Your ACF Field Details #

Double-check the Field Name (not the label) in your ACF field group for service_area_state. It needs to match exactly with the meta_key in your query—even a single typo (like underscores vs hyphens) will break things. Also, note the field type:

• If it’s a Select, Radio Button, or similar, confirm whether it returns a Value (string/integer) or Label in the field settings. If it returns an array (e.g., both label and value), your meta_value comparison will fail because ACF stores the raw value in the database, not the array.

2. Debug the Value of $arch_state #

Before running the query, let’s make sure get_field('service_area_archive_state') is returning what you expect. Add this line right after fetching the value:

var_dump($arch_state); // Check what this outputs—remove after debugging!

If it’s an array (instead of a string/integer), you’ll need to adjust your query to target the actual stored value. For example, if $arch_state is an array like ['value' => 'CA', 'label' => 'California'], use $arch_state['value'] instead.

3. Switch to meta_query (Recommended) #

WordPress has deprecated the old meta_key/meta_value parameters in favor of meta_query, which is more reliable—especially with ACF fields. Rewrite your args like this:

$arch_state = get_field('service_area_archive_state');
// If $arch_state is an array, extract the value first (adjust based on your field type)
if (is_array($arch_state)) {
    $arch_state = $arch_state['value'];
}

$args01 = array(
    'post_type' => 'service-area',
    'posts_per_page' => -1,
    'orderby' => 'title',
    'order' => 'ASC',
    'meta_query' => array(
        array(
            'key' => 'service_area_state',
            'value' => $arch_state,
            'compare' => '=', // Use 'IN' if $arch_state is an array of values
            'type' => 'CHAR' // Adjust based on your field type (e.g., 'NUMERIC' for integers)
        )
    )
);
$serv_areas = get_posts($args01);

This gives you more control over the comparison and ensures WordPress handles the query correctly.

4. Check Post Status & Permissions #

By default, get_posts() only returns published posts. If your service-area posts are in draft, pending, or another status, add 'post_status' => 'any' to your args to include them (or specify the exact status you need).

5. Debug the Actual Query #

To see exactly what SQL WordPress is running, switch to WP_Query temporarily and print the query:

$query = new WP_Query($args01);
echo '<pre>' . esc_html($query->request) . '</pre>'; // View the raw SQL

This will show you if the meta key/value are being correctly included in the query. You can even run this SQL directly in your database (via phpMyAdmin or similar) to see if it returns any results.

6. Confirm Meta Values Exist in the Database #

Check your wp_postmeta table to make sure:

• The meta_key for your field is exactly service_area_state (ACF doesn’t add underscores unless it’s a hidden field).
• The meta_value for your posts matches the value of $arch_state (case-sensitive, unless you use 'compare' => 'LIKE').

Once you’ve gone through these steps, your query should start returning the expected posts. Let me know if you hit any snags with specific steps!

内容的提问来源于stack exchange，提问作者Leo C