plugins_url will output the absolute file path of the plugins directory in your WordPress install. This of course won’t work for a client (browser) calling a script. To access scripts from the plugins directory, you’ll want to use plugin_dir_url() which will get you the url of the plugin directory. Some things to note about plugin_dir_url() … Read more
when you are at the post URL, you don’t need to work with referer (which is not reliable moreover) but with $GLOBALS[“post”] because you are in the PHP code which generate the page then you can have the post ID with that : $post_id = $GLOBALS[“post”]->ID;
No, it just means it’s used by many plugins, not that Core includes it. Many of the functions in that library seem to use the JsonLdProcessor class that is also in that library, I’d check for that before including: if ( ! class_exists( ‘JsonLdProcessor’ ) ) { require_once( ‘jsonld.php’ ) }
script_loader_tag or script_loader_src filters are there to let you tweak the HTML of the script easily so you can add custom attributes: add_filter(‘script_loader_tag’, function($tag, $handle){ switch ( $handle ) { case ‘foo’: $tag = preg_replace( ‘/src=[\’|”|]/i’, ‘crossorigin $0’, $tag ); break; } return $tag; }, 10, 2); To avoid conflicting with other plugins, pass unique … Read more
You can’t predict if something will include your box further down the line, so to do it “the right way”, you’ll need to add your CSS/JS early. The not-so-right way could be to add output buffering and analyze the output to see if your box got included somewhere, and then add your HTML to the … Read more
You could also look to create a special CSS file that you setup an htaccess rewrite rule for. For example wp-content/yourtheme/custom.css And then add a rule in your htaccess: RewriteEngine On RewriteRule ^/wp-content/yourtheme/custom.css$ /wp-content/yourtheme/styles.php [L] You can then call wp-load inside this styles.php file, do any sort of logic required, before outputting your custom css … Read more
Your second wp_enqueue_script() contains the same handle (the same ID) as the first wp_enqueue_script(). The handle is the ID by which a registered script is known to WordPress internally. If you use this ID a second time, the second script won’t be registered. A working example could be this one: <?php add_action( ‘wp_enqueue_scripts’, ‘theme_enqueue_styles_and_scripts’ ); … Read more
It seems to me best to separate styles, from scripts and other assets. This worked: function my_theme_enqueue_styles() { wp_enqueue_style( ‘parent-style’, get_parent_theme_file_uri() . ‘style.css’ ); } add_action( ‘my_theme_enqueue_styles’, ‘wp_enqueue_styles’ ); function my_theme_enqueue_assets() { wp_enqueue_script( ‘behavior’, get_theme_file_uri( ‘behavior.js’ ), array(), null, true ); } add_action( ‘wp_enqueue_scripts’, ‘my_theme_enqueue_assets’ );
Yes. Dependencies work across all of WP, it doesn’t matter where you enqueue your script. All that matters is that you define your dependencies correctly, and you’re doing that. If, however, you plan to publish both the theme and the plugin as standalone versions, you shouldn’t rely on your plugin being used with your theme, … Read more
is_single() doesn’t work for the page post type, use is_page() instead. You’re also missing the first argument for wp_enqueue_script, the script handle. Source should be the second argument. function my_conditional_enqueue_script1() { if ( is_page() && in_category( 19 ) ) { wp_enqueue_script( ‘my-cart-script’, ‘/members/application/cart/views/public/js/cart.js’ ); } } add_action(‘wp_enqueue_scripts’, ‘my_conditional_enqueue_script1’);