Prices of variations in pull-down menus, it works, but not on bundled products

Have you found resolution? I have the same issue. My client once was using the Woo radio buttons, but since are not accurately updated nor responsive. We are switching back to the drop down for variations and also want the price to display in the drop down as well as some additional text. And this above code worked great with the radio buttons; however, with the drop down the <span> tags continue to show despite some effort with CSS. Any help would be greatly appreciated.

I haven’t had an answer on this one. Perhaps you asking will help some see it again.

Interesting that it works for radio buttons but not for drop-downs. Seems like the display method for lists shouldn’t be a factor.

My pulldown menus show a display like this… this is not the code of the page, this is the actual display of items in the variations pull down menu on a product.

ITEM NAME (<span class="amount">$37.50</span>)
ANOTHER ITEM (<span class="amount">$25.00</span>)

It’s supposed to look like this…

ITEM NAME ($37.50)
ANOTHER ITEM ($25.00)

I found in abstract-wc-product.php on line 975 the following code (which is the only location in a search of “<span class=”amount”>” in the WooCommerce files)…

$price = '<span class="amount">' . __( 'Free!', 'woocommerce' ) . '</span>';

The above code would appear to be the one that is showing up in my variation menus. But why would the span class tag show up around my prices?

And here’s my function code again, just making sure I have the current version on here…

//Add prices to variations
add_filter( 'woocommerce_variation_option_name', 'display_price_in_variation_option_name' );

function display_price_in_variation_option_name( $term ) {
global $wpdb, $product;

$result = $wpdb->get_col( "SELECT slug FROM {$wpdb->prefix}terms WHERE name = '$term'" );

$term_slug = ( !empty( $result ) ) ? $result[0] : $term;

$query = "SELECT postmeta.post_id AS product_id
FROM {$wpdb->prefix}postmeta AS postmeta
LEFT JOIN {$wpdb->prefix}posts AS products ON ( products.ID = postmeta.post_id )
WHERE postmeta.meta_key LIKE 'attribute_%'
AND postmeta.meta_value = '$term_slug'
AND products.post_parent = $product->id";

$variation_id = $wpdb->get_col( $query );

$parent = wp_get_post_parent_id( $variation_id[0] );

if ( $parent > 0 ) {
$_product = new WC_Product_Variation( $variation_id[0] );

//this is where you can actually customize how the price is displayed
return $term . ' (' . woocommerce_price( $_product->get_price() ) . ')';
}
return $term;

}

The problem has worsened with the 2.5 update. Now we’re getting that problem on more of the variations menus.

2.5.1 didn’t seem to address the issue.

You are using custom code to show prices in dropdowns, so core is not going to fix this for you. Wrap the price with strip_tags()

Thanks so much for responding. This has been an old issue.

Where would I wrap the strip_tags() around? I tried around ( $_product->get_price() ) and got a blank screen.

return $term . ' (' . wc_price( strip_tags( $_product->get_price() ) ) . ')';

Thank you for the syntax tip. I need to learn more about the proper spacing between parenthesis and code.

I tried that and no white screen this time. But it didn’t solve the problem. I still see the tags. Here is a page where the tags are in the variations pull down menu.

My bad.

return $term . ' (' . strip_tags( wc_price( $_product->get_price() ) ) . ')';

LOL. Oh those darn pesky placements. Thank you, Mike. My client will be very happy to see those spans gone.

By the way, can you point me to a good location about the proper spacing of parenthetical usage in code? I really want to know the ins and outs of those situations.