You should be able to get the current product id using the using the $post global variable and use that with the WooCommerce function get_product() to the the product object and test its product type. public function __construct() { add_action( ‘add_meta_boxes’, array( $this, ‘add_meta_box’ ) ); } public function add_meta_box( $post_type ) { $post_types = … Read more
I have solved this problem after many researches, just comment two lines in meta_box.php file at end. $sanitizer = isset( $field[‘sanitizer’] ) ? $field[‘sanitizer’] : ‘sanitize_text_field’; to //$sanitizer = isset( $field[‘sanitizer’] ) ? $field[‘sanitizer’] : ‘sanitize_text_field’; at line 692 and $new = meta_box_sanitize( $new, $sanitizer ); to //$new = meta_box_sanitize( $new, $sanitizer ); at line … Read more
As @Milo pointed out, when you use code in OP $post_types is undefined inside the function, so WordPress will act just like it was not there at all. However, that means you are using an undefined variable, and if turn WP_DEBUG on you’ll see a warning, and so you can notice you are doing something … Read more
So I was really overthinking this problem. Hopefully my answer can help someone in the future. Basically all I needed to do was save the array from wordpress and check to see if the user_ID (Associative Array Key) was in the Array, if it was and the user needed to change the value I needed … Read more
First, you have a very basic PHP mistake: single quotes mean “string literal”. Variables won’t be processed. You are literally putting “$variable” into the generated code. Second, look at the third parameter of get_post_meta() $single (boolean) (optional) If set to true then the function will return a single result, as a string. If false, or … Read more
@Jeffrey’s answer is correct is you are the one registering the post types, simply remove the support argument for comments. But if you want to remove it from all custom post types (that may be registered by plugins too) you can do: $cptslugs = get_post_types( array(‘public’=>false, ‘_builtin’ => false) , ‘names’, ‘and’); foreach ($cptslugs as … Read more
You can specify the key you want in get_post_meta: echo get_post_meta( $home_starting_player, ‘pb_squad_number’, true ); WordPress loads all meta for any single meta call, so calling get_post_meta multiple times doesn’t introduce any extra overhead.
This has been present since before the block editor, and even the classic editor, and can be seen in WordPress 2.0. It even predates proper metaboxes! In the block editor, the presence of the author field depends on wether the user has the action wp:action-assign-author, but there is no direct capability that determines this. If … Read more
Hmm, a lazy workaround—as long as you’re not running PHP < 5.3.0—might be to use a namespace in your mu-plugins file. Something like this might do the trick: <?php namespace Arglebargle; \add_action( ‘wp_dashboard_setup’, ‘Arglebarle\remove_x_widget’ ); function remove_x_widget() { // If the meta box has already been removed, it shouldn’t be an // issue to ‘remove’ … Read more
add_post_meta() : Adds a meta field to the given post. Below is the example, <?php $post_id = 1; $meta_key = ‘_test’; $meta_value=”this is a test”; $unique = true; add_post_meta( $post_id, $meta_key, $meta_value, $unique ); update_post_meta() : if the given key already exists among custom fields of the specified post, another custom field with the same … Read more