ulfkri

I just added some data with PayPal IPN Simulator and everything looks fine to me.

I won’t recommend anyone else to remove the lines, because I might have broken something that I don’t understand, but I will try with this configuration for a while and see how it goes. So far it looks fine.

Since I didn’t find any other references to cdn.datatables.net, I would think that I have removed every reference to the JavaScript and CSS-files there, so I’m a bit confused as to why it didn’t break. Maybe they are not needed at all?

Hmm… I just tested around a bit…

The file class-paypal-ipn-for-wordpress-public.php enques scripts and styles from cdn.datatables.net, but also states in the comments that This function is provided for demonstration purposes only.

When I remove the calls to wp_enqueue_style and wp_enqueue_script in this file the problems described above goes away.

The back end table still looks the same to me (in admin), but I don’t have any data yet, so I don’t know if I broke anything.

None of the other files have references to cdn.datatables.net so I kind of expect that I must have broken something, but I don’t see anything wrong yet.

I’ll get back to you in a couple of days when I have data in the table.

I loose one point with Google PageSpeed Insights due to the calls to cdn.datatables.net. I guess the reason is that their javascripts are not minified and they are called with the version number (like this: dataTables.css?ver=1.0.8).

Suggestions from Google PageSpeed Insight are:

– Remove render blocking JavaScripts:
– https://cdn.datatables.net/….7/js/jquery.dataTables.min.js?ver=1.0.8
– https://cdn.datatables.net/….6/js/dataTables.responsive.js?ver=1.0.8

– Optimize CSS delivery:
– https://cdn.datatables.net/…10.7/css/jquery.dataTables.css?ver=1.0.8
– https://cdn.datatables.net/…/css/dataTables.responsive.css?ver=1.0.8

– Minify JavaScript:
– Minifying https://cdn.datatables.net/….6/js/dataTables.responsive.js?ver=1.0.8 could save 4.9KiB (61% reduction) after compression.

I also tested with tools.pingdom.com and see the 4 calls being made to cdn.datatables.net. I believe none of them are needed on the front end.

Removing cdn.datatables.net from the front end would fix all the issues above and improve SEO.

Apart from that it looks like the perfect plugin. I’ll come back and rate it when I have tested it for a while.

Jan, you should change your rating if this solution worked for you. The plugin works right out of the box for me.

Ah, thanks!

Actually, I see that this change was made to the sourcecode on Sep 2, 2014. You can see the change here: https://github.com/wp-plugins/quickshare/commit/8d15039d02616b512eb7283590251b31b5800515

I don’t know why this change hasn’t made it into the production code…