The get_template_directory_uri() function returns the URL to the root theme. If a child theme is used and you want to return the URL to the current child theme, use get_stylesheet_directory_uri() instead. https://developer.wordpress.org/reference/functions/get_stylesheet_directory_uri/
Comments of post author are given a class bypostauthor , you can personalize it through css.
Dequeueing the enqueued style will be sufficient. But you need to be careful to dequeue it after it is enqueued. It is enqueued at the default priority of 10, so make sure that when you hook into wp_enqueue_scripts you do so at a higher/later priority. add_action( ‘wp_enqueue_scripts’, ‘wpse_escutcheon_scripts’, 11 ); function wpse_escutcheon_scripts() { wp_dequeue_style( ‘escutcheon-fonts’ … Read more
The list_attributes is a method of WC_Product class called with -> operator and the wc_display_product_attributes is a simple function. This will fix the issue: add_action ( ‘woocommerce_product_meta_start’, ‘show_attributes’, 25 ); function show_attributes() { global $product; wc_display_product_attributes( $product ); }
How to build two WordPress site using two different themes with same database (No ! I am not taking about multisite network)?
From a cursory overview, the cross-sells are added via the same ajax add to cart script as regular shop loop archive products and I don’t see a way to distinguish between when it’s a cross-sell and when it’s not. You could run a script conditionally only on the cart page, and then listen to the … Read more
Alright figured it out. As Jacob pointed out, it should go into the script that makes data-name show as a tooltip. So I added the following: if (jQuery(window).width() < 480) { jQuery(this).removeAttr(“href”); } My final code: jQuery(document).on({ mouseenter: function(e) { if (jQuery(window).width() < 480) { jQuery(this).removeAttr(“href”); } setTimeoutConst = setTimeout(function() { tooltip.open(e); }, 200); }, … Read more
You can use set_query_var(‘playlist_id’, $tp_atts[‘id’]);. When you later call locate_template with $load = true, it will call load_template, which extracts the query variables making them global, and accessible to the template file (in this case, as $playlist_id).
The cache should really get cleared based on some change you made, not based on some manual cache clearing. Can you not disable caching in the Customizer preview by turning it off when is_customize_preview()? Then you can flush the cache at the customize_save_after action: add_action( ‘customize_save_after’, ‘sc_clearcache’ );
How to pass data from a plugin to functions.php