Ibby

So I’ve managed to do this to an extent. I am using the following snippet:

/**
 * Change price format from range to "From:"
 *
 * @param float $price
 * @param obj $product
 * @return str
 */
function iconic_variable_price_format( $price, $product ) {
    $prefix = '£';

    $min_price_regular = $product->get_variation_regular_price( 'min', true );
    $min_price_sale    = $product->get_variation_sale_price( 'min', true );
    $max_price = $product->get_variation_price( 'max', true );
    $min_price = $product->get_variation_price( 'min', true );

    $price = ( $min_price_sale == $min_price_regular ) ?
        wc_price( $min_price_regular ) :
        '<del>' . wc_price( $min_price_regular ) . '</del>' . '<ins>' . wc_price( $min_price_sale ) . '</ins>';

    return ( $min_price == $max_price ) ?
        $price :
        sprintf('<img src="https://hillfarmfinest.com/wp-content/uploads/2018/12/per-piece.png"> %s%s / <img src="https://hillfarmfinest.com/wp-content/uploads/2018/12/per-kilogram.png"> %s%s', $prefix, $min_price, $prefix, $max_price);

}

add_filter( 'woocommerce_variable_sale_price_html', 'iconic_variable_price_format', 10, 2 );
add_filter( 'woocommerce_variable_price_html', 'iconic_variable_price_format', 10, 2 );

I now need to make the sure the sale price comes up correctly. There are two scenarios:
1/ When the per piece price is on sale
2/ When the per kg price is on sale

Some more tinkering required hmm…

@joyously, sorry my mistake for not explaining fully, that code is placed in the page body area to output the variables onto the actual page. It is those HTML outputs I want to make available via the REST API.

@diondesigns, I am converting all of my code to mysqli, so this will be fixed. Would the REST API not be able to output the echos in this case? The error status was just for debug and I should have deleted it.
Also what you said at the end there has peaked my attention; how do I use the built-in db access available to WP? I am not very experienced with WP-PHP though I knnow my way around. I usually just define a function for the db connection and then call the connection when required. It sounds like I’m doing it wrong from what you said.

Strangely, it’s still not working. I’ve done as you said in footer.php:

</div> <!-- end main-container -->
</div> <!-- end site-wrap -->
<div id="ps2id-offset-element" style="height:120px;width:0;position:absolute;"></div>
<?php wp_footer(); ?>

</body>
</html>

Ok, so, it turns out, WC seems to really dislike moving the coupon field. I used the following hook in my functions.php to move the coupon code field to after the customer details:

// Add coupon code area above order total, old section hidden via CSS
remove_action( 'woocommerce_before_checkout_form', 'woocommerce_checkout_coupon_form', 10 );
add_action( 'woocommerce_checkout_after_customer_details', 'woocommerce_checkout_coupon_form' );

As soon as I add this, the button breaks. I have a feeling this is because my code isn’t removing the original coupon form for some reason even though the remove_action is targeting it correctly…
I presume this is because it now thinks there are two coupon code fields and so the fom script breaks.

I’ve removed the snippet for now and it is working fine! Now to try and work out why exactly this is happening….

Hi Melinda,

Thanks for the response, I’ll give that a try.
I’m usually quite meticulous with modifying the loops or CSS (I always define my own classes specifically for these sorts of changes) so I’m not sure how I could have affected the native functionality on the checkout page.

I’ll give your suggestion a try and see what comes of it.

Thanks.

Hi @icegram,

Thanks for the reply. I can’t see how to import one of the demos. How do I do this?

The key I’m using is from the WordPress salt generator. I guess I can try changing it to another one…

But that’s interesting because the error is thrown due to no secret key hmmm. I wonder what the issue can be.

Ah yes, sorry, I forgot to disable the coming soon plugin.

I’ve found a work around by setting the default display state to ‘none’. It’s actually working quite nicely!

Thanks for your help.