ERROR: Trailing slash when enqueuing styles vs. scripts

You shouldn’t use the path hardcoded like that.

It is better to use it like this (for themes)

wp_enqueue_script(
		'handle',
		get_template_directory_uri() . '/path/to/file.js',
		array(),
		'1234', true
	);

wp_enqueue_style(
		'handle',
		get_template_directory_uri() . '/path/to/file.css',
		array(),
		'1234'
	);

If you use it in a plugin, use plugin_dir_url( )

This will nicely load the relative path to the file, and work always, as opposed to hardcoded paths, which might not work when you rename plugin name for example (which is a part of a simple debug procedure)

• This reply was modified 4 years, 11 months ago by Anonymous User 14808221.
• This reply was modified 4 years, 11 months ago by Anonymous User 14808221.

I do not think this is the case, not only because I am a developer and do read the core code of those functions when I use them, and there is nothing that will remove or add your slashes if and wether you hardcode or not, but I also took the time to confirm this in a local install.

Your suggested code will throw an error on the first line (the CSS) because missing the / at the path start of the relative path.

If you really want to hardcode the path, this is what works:

$plugin_path = "/wp-content/plugins/your-plugin-name";
wp_enqueue_style("my_style", $plugin_path."/public/css/style.css", array(), false, "all");	
wp_enqueue_script("my_js", $plugin_path."/public/js/script.js", array(), false, true);

Note that I think you also missed the dependency in your code, I added it in above example for completeness.

Now, if you think you have found a bug in this behaviour and have clear steps to replicate it the right place to report for fix would be the Trac platform here https://core.trac.wordpress.org
The documentation is generated from the Code, so what is stated in the documentation generally is not human work, but generated by a program from the code, hence reflecting by the letter what is commented in code. There can hence not be any "mistake" in this sense in the Documentation if not also present in the code.

However, as I tested and deduced from reading the code the functions work just fine.
Even if your path would change, that wouldn't be due to the enqueue functions, since those cannot change the path you pass hardcoded.

Note again that with this hardcoded approach if someone renames wp-content or renames your plugin main folder the plugin will fail.

I hope this helps

I am happy your question has been answered, we would love if you would mark this topic as resolved in the sidebar.

This helps our volunteers find the topics that still need attention and more people will get helped, possibly like you did.

Cheers.