It appears this is a known issue with the block editor (aka Gutenberg). That Trac ticket suggests a workaround, too: replace your if ( ! is_admin() ) { … } with something like this: global $current_screen; if ( ( ! is_admin() ) && ( ! ( // Checks the value of WP_Screen::is_block_editor(). $current_screen instanceof \WP_Screen …
The is_virtual() method in WC_Product class it return boolean. It means that, if $product->is_virtual() return true, it is virtual product, vice versa if return false, then the product is physical. In your case, you can use this if( $product->is_virtual() ) { //is Virtual Product, do something here } if( !$product->is_virtual() ) { //is Physical Product, …
Your question needs some additional context, but here’s a generic approach to what you’ve described. if ( is_user_logged_in() ) { $user = wp_get_current_user(); // Does user have the required role? if ( in_array( ‘some_role’, $user->roles ) && ‘some_meta_value’ == get_user_meta( $user->ID, ‘some_meta’, true ) ) { // Special content… } else { // User doesn’t …
If you pasted the exact second block you’ll get errors because you are breaking up the closing and opening PHP tags <?php and ?>. Try this instead, or have a look at this for a better understanding, notice the difference … if ( is_page( ‘about’ ) || ’29’ == $post->post_parent ) { //Start of the …
I don’t think that is possible using some function (I can be completely wrong though). What you can do is check page slug using if() statement. Something like: global $post; $post_slug=$post->post_name; if($post_slug==’harry-potter’){ //something here }
Add a filter conditionally based on frontpage
I refactored the if conditional using suggestions from Jacob Peattie and the following fixed my issues. if ( ! is_page_template( array( ‘template-investment.php’, ‘template-tourism.php’ ) ) && ! is_tax( ‘listings’ ) && ! is_singular( ‘listing’ ) ) { The result correctly removed the sidebar.php from loading its code on specific templates, taxonomy, and single post type.
Your code looked good to me, so I believed that the PHP notice was unlikely caused by the code in question. But that issue could probably be caused by a previous version of that code. E.g. If you had used the init and not wp_enqueue_scripts hook to enqueue your script, then such notice is expected, …
There’s two main ways: You can use the post_password_required() function. This function returns true if the post has a password and false if the post doesn’t have a password, but it also returns false if the post had a password but the user has entered it and unlocked the post. You can get the post …
I am not exactly sure what you are trying to do. However, in the second line of code you have a closing bracket at the end, but there is no opening bracket in your code. Maybe that’s the problem?