Thanks for your post,
We are using latest version of “font-awesome” css file and fonts,
whenever we update or user reported this issue we also update the plugin to avoid conflict.
can you please send me your link ?
I would not recommend rename the font awesome file, most of the user don’t like this.
Regards
Not rename the file, the “enqueue” name you give is “font-awesome” – you can call that anything you’d like – “font-awesome-job-board”. That would give developers a way to “dequeue” your instance of the css file and make things like combining their own files easier to accomplish. I’m not saying you did it wrong by any means, just that when we as developers enqueue our files for plugins it is good practice to not tag our enqueued files generically:
Line 163 of job-board-manager.php
wp_enqueue_style(‘font-awesome’, job_bm_plugin_url.’assets/global/css/font-awesome.css’);
Could be:
wp_enqueue_style(‘font-awesome-job-board’, job_bm_plugin_url.’assets/global/css/font-awesome.css’);
Which would allow in a functions.php (or alternate plugin):
function wpdocs_dequeue_script() {
wp_dequeue_style( ‘font-awesome-job-board’ );
}
add_action( ‘wp_print_scripts’, ‘wpdocs_dequeue_script’, 100 );
We’re definitely not saying “rename your physical file”. Consistency in the way you enqueue your files for a plugin ultimately gives development greater flexibility.
Thanks again, as mentioned prior, great work on the plugin!
I didn’t mean rename physical,
if i use
wp_enqueue_style(‘font-awesome-job-board’, job_bm_plugin_url.’assets/global/css/font-awesome.css’);
that will load another font awesome file if already enqueued from another plugins or themes,
this will also increase site loading time, most of user don’t like this
please see the file i have added latest version of font awesome.
https://plugins.svn.wordpress.org/job-board-manager/trunk/assets
/global/css/
can you please reinstall the plugin and let me know the result,
Regards
