As requested on https://wordpress.org/support/topic/feature-idea-avoid-versioning-remote-libraries/

Quote:

I’ve noticed that the plugin doesn’t remove the (wordpress default?) ?ver=4.9.6 from remote urls, like Google Fonts, jQuery, and so on.

I think that’s because it doesn’t find anything local to get filemtime for, so it throws up hands and returns without changing the src.

It’s possible that without this ?ver= param, loading from a canonical source, a viewer browser could have some libraries already in cache from another site. a mild perf boost.

Adding the following line to the top of the autover_version_filter function fixes this behavior, so that if it can’t find the file locally, it gets no ?ver= param at all.


	$src = remove_query_arg( 'ver', $src );
Arguably a defect in wp core, not autover, but seems like a nice opportunity to make this plugin even better…

Thanks,
Chris

Using a local instance with autover installed this notice appeared:
Notice: Undefined variable: filetype in /vagrant/wp-content/plugins/autover/autover.php on line 134

The plugin is incompatible with the "nextgen-gallery" WP Plugin, and this must be fixed.

Fatal error: Cannot redeclare class simple_html_dom_node in /www/wp-content/plugins/autover/simplehtmldom.php on line 115

Getting this Notice when accessing the Gitium/commits page:

PHP Notice: Undefined variable: filetype in /www/wp-content/plugins/autover/autover.php on line 197 when calling autover_version_filter(), request: GET /wp-admin/admin.php?page=gitium/gitium-commits.php, request_id: b886268f9382083fbf7e23e2db1bef44

We need to explain that

add_action('wp_enqueue_scripts','autover_add_style_and_script');

adds the scripts and styles to the frontend and

add_action('admin_enqueue_scripts','autover_add_style_and_script');

adds the scripts and styles to wp-admin.

Some users tend to simply copy paste the examples without checking the entire code and they end up with weird styles on wp-admin.