wp enqueue script was called incorrectly wordpress

#Wp enqueue script was called incorrectly wordpress code#
#Wp enqueue script was called incorrectly wordpress trial#

(they use a structure called “codemirror”) * Tweak: Use `admin_head` instead of `admin_enqueue_scripts` …

#Wp enqueue script was called incorrectly wordpress trial#

So my trial is to leave the plugin to load everywhere and then make a list of dequeued in functions.php.īut I tried all, something goes wrong: probably because such plugin author declares: In fact that plugin enqueues all my 32 codes everywhere, even if “generic codes” (I mean to be embedded everywhere) are just 12 and rest are for specific pages.Ī quick solution could be to load on a folder all the specific codes, since I call/embed them in their appropriate pages manually, but I wanted a clean way (even if I have no time to make a Child Theme). Unfortunately with me it doesn’t work, I guess because the codes which I try to dequeue are enqueued by plugin “custom-css-js”. Here’s what that type of file might look like.

#Wp enqueue script was called incorrectly wordpress code#

You can include this code directly in the functions.php file of your theme, but I generally load a separate file as a class either from a mu-plugin or the theme. I’ve limited the dequeues to the front page of the site in these code blocks, but you can use different page conditionals to remove the scripts and styles from where they are not needed. Wp_dequeue_style( 'woocommerce-inline' ) Īdd_action( 'wp_enqueue_scripts', 'prefix_remove_styles', 100 ) Wp_dequeue_style( 'wc-block-vendors-style' ) * Remove styles that have been enqueued by other plugins. To dequeue styles you can use the wp_enqueue_scripts hook: /** Wp_dequeue_script( 'storefront-header-cart' ) Īdd_action( 'wp_print_scripts', 'prefix_remove_scripts', 100 ) Wp_dequeue_script( 'wc-cart-fragments' ) * Remove scripts that have been enqueued by other plugins. To dequeue scripts you can use the wp_print_scripts hook. It will also show you the “handle”, which is needed to dequeue the asset.

Query monitor will show you all the scripts enqueued by WordPress for a specific page. Screenshot of site with Query Monitor running This will let you know which scripts and styles are enqueued for a specific page.

To find our which scripts and styles are enqueued, you’ll need to do a some detective work. I recently went on a performance rampage at Universal Yums and removed ~300kb of enqueued assets that were not needed on our home page- which shows there can be quite a bit of fat to trim. For example, WooCommerce loads at least 3 scripts and 4 styles on every page, even if ecommerce functionality (like a cart or products) aren’t shown on those pages. (i know you might run into version issues but its likely far less of an issue than if you load it twice).Many WordPress plugins load scripts and styles on every page of a website even though they may just be needed on a few specific pages.

Developers, please name your scripts “font-awesome” when you enqueue them. Tag but its href=”#” so that is not the problem but the onclick handler i guess targets the The other issue i seen this with was the BuddyBoss theme, they do something similar with an Just today i seen issues with two widely used WP products, the first was with Ninja Forms, they use the FA v5 CSS version and if the JS version of FA is loaded then you can’t exit out of the form edit screen as their Tag, this is not by its self a problem but the problem is when developers have been using just the CSS version and either style for that tag or use JS to fire a onclick method on that specific tag or even on a link or button which in all cases your going to have a bad time. That the JS version of FA will replace the item that has the FA class with a This is fine for “Joe Blogs” with his html website but once you are using a CMS (content management system) like WordPress which has plugins built by many many devs you have the situation that both the CSS and the JS can be used and this can lead to many problems. The main brewing problem with using Font Awesome in WP these days is that FA v5 introduced a new way to use it, in FA v4 it was always just a CSS file but now it can be used either as a CSS file or as a JS file. The fix to this is relatively simple and is resolved by the two devs using the same name to add the file, we use and we suggest “font-awesome”.Ģ. The first (less serious) problem is a common problem with JS/CSS libraries and WordPress and can affect FA v4 not just FA v5, that is the fact that two developers might add the script and use different names so the same file gets added to the website twice. It’s a little CSS (or JS in v5) file that you can add to your site to be able to use lots and lots of fancy icons on your site. This blog post is mainly to draw attention to the brewing problem with using Font Awesome v5 in your WordPress Plugin or Theme.