ace0930

@diondesigns The CSS is so long that I can’t write them all here, the reason I’m only writing one of them here is to give a general idea of what I’m doing and why I need $wpdb.

@threadi This is working but I’m not sure it’s great for performance and considered a good practice.

Okay, I found out I need to use get_var.

@kaushiksomaiya Okay, thanks.

@longnguyen89 But I wanna display it on a specific post type and not a specific post. If I pass the post ID to the third parameter, it won’t work on other posts even on the same post type? If I leave the third parameter empty, it then does not show on all the posts of the same post type.

For example, if there are three posts (apple, orange, and watermelon) where they got the same post type ‘fruit’, if I specify the post ID (say like apple, assume the ID is 123) to the third parameter. It then only shows on apple? And if I leave the third parameter empty, then all of the post (apple, orange, and watermelon) won’t also show the field value even they’re on a same post type?

Hi, thanks for responding. What if I want to display the custom field value from a specific post type instead of one post?

Assume the slug of the custom post type is ‘apple’ and the custom field ID is ‘testing_data’, I’ve tried this code but it’s not working.

<p>
    <strong>Display:</strong> <?php rwmb_get_value( 'testing_data', ['post_type' => 'apple'] ) ?>
</p>

@mrclayton I’ve tried using the filter woocommerce_is_checkout but it adds the class .woocommerce-checkout to the body and causes the styling to be wrong.

Here is the code:

add_filter('woocommerce_is_checkout', 'loadCheckout');

function loadCheckout() {
    $switchState = true;
    return $switchState;
}

@rainfallnixfig Problem solved. Thank you so much!

@mrclayton I found where is the problem coming from, the CSS and JS file won’t be loaded if this setting is not set: WooCommerce Setting > Advanced > Checkout Page

Any idea how to solve this? I’m using a custom checkout page but for some reason, I cannot set up the custom checkout page by this setting instead of using custom PHP to redirect the checkout page to the custom page.

The PHP code I’m using is:

<?php

    add_filter('woocommerce_get_checkout_url', 'my_checkout');

    function my_checkout($url) {
        global $woocommerce;
        return $checkout_url = 'https://example.com/custom-checkout-page/';
    };

?>

Hi, thanks for responding.

It’s not only Stripe, the form field of all the payment method is in such situation as well,

Sure, here is the URL: https://demo.weecoo.net/design-set/wc-1-itsid-9/

Can you give an example of getting the custom field value by PHP way? So I know how to do this in the future when I learn PHP…My use case will be clicking the button on the frontend to get the custom field value.

@tonyrobins The word ‘support’ means it can be used already or it simply means the server support PDO but actually not yet been configured ( like download or install )?

But will PDO causes any problem because it’s not the default method of accessing the database for WordPress although it’s faster.

@tonyrobins Thanks for the quick response. I just got one more question about the database access method.

I saw the word ‘support’ for PDO_MYSQL in the debug which means that I can use PDO already? But I saw WPDB got better compatibility, may I know what compatibility means here? Is it means it’s safer to access the database through WPDB?

Interesting, let me try.