Squazz

The plugin works fine for me on Chrome. Really love it!
But I don’t have Safari available for me, so I’m unable to test how it work there ??

Woo! You’re awesome!

Just tested it, and it works flawlessly on my Honor 10 with Android P.

I love that you could actually solve it my removing JS, and also that you minified the JS & CSS!

Keep up the good work! ??
I updated the review to reflect your changes

• This reply was modified 5 years, 2 months ago by Squazz.

Sounds good!

Just don’t use too much JS trying to fix the scroll issue ?? Lightweight is (in my opinion) better than fixing something as minor as this ??

I’m not saying that you as a developer of a plugin, should enforce an upgrade of jQuery for the entire site. Yes, that would be extremely rude ?? But I don’t see any reason to lock down the version to the version WordPress is shipping. The fact that you as a plugin-developer finds it necessary to enforce / lock down the version of jQuery seems very rude too.

If you were dependent on something specific from jQuery one, it would be a different story. But I can’t figure of anything you would be dependent on. Between jQuery 1 & 2 there no breaking changes – except that IE 6, 7, 8 is no longer supported. Reference: https://blog.jquery.com/2013/05/24/jquery-1-10-0-and-2-0-1-released/
jQuery 3 is a different story: https://jquery.com/upgrade-guide/3.0/#jquery-core-3-0-upgrade-guide

I personally think, that as a developer of one of the most downloaded plugins for WordPress, you guys should aim higher for your code. Ensuring that your jQuery code is jQuery 3.x compatible would be a great mindset, and would then allow you to not lock down the version of jQuery.
You guys shouldn’t be thinking of workarounds. You should ensure your code is forwards compatible, and then lift the enforcement of the WordPress delivered jQuery.

Regarding the vulnerabilities, I’m trusting SNYK https://snyk.io/test/npm/jquery/1.12.4. They inform that there are two known vulnerabilities in the jQuery version WordPress is shipping with.
I know there are reasons for WordPress to keep jQuery at version 1.x as many themes and plugins are written with this version in mind. I still don’t like it, and I try to upgrade my websites to jQuery 3 if possible. But that’s an entirely different discussion.

And thank you for your time! ??

I’ve notified them ??

BTW: Have you considered fetching jQuery from https://code.jquery.com/ ? In that case people who have already visited a site doing the same, won’t need to download jQuery again. It could add performance boosts.

Also, this approach would enable you to not risking being blamed for injecting your own hacked version of jQuery via your plugin.

It seems NextGEN Gallery is the culprit.
– I hate that plugin already, so now it’s officially dead to me ??

Hi @remzicavdar
Totally understandable. Don’t get stressed about it, I have time ??

I’ll disable everything, and then go through the plugins one by one if disabling them helped.

I’ve tried out the same theme on another server (https://hedensted.tra.dk) and here it works just fine :/

Thank you so much! @remzicavdar ??

WordPress 5.2.2
Running PHP version: 7.2.20

Theme: Startup BlogVersion: 1.31 from https://www.competethemes.com/
– Made my own childtheme, nothing crazy here, and the problem persists even when I shift to only use the vanilla theme

Plugins
Activated:
Absolute <> Relative URLs
Admin Menu Tree Page View
Akismet Anti-Spam
Broken Link Checker
Elementor
FV Top Level Categories
Glue for Yoast SEO & AMP
Google Analytics for WordPress by MonsterInsights
iThemes Security
Jetpack af WordPress.com
jQuery Manager for WordPress
Klassisk editor
NextGEN Gallery
Redirection
RSS Featured Image
Structured Social Profiles
UpdraftPlus – Backup/Restore
WP-Optimize
Yoast SEO

Deactivated:
AMP
Autoptimize
Display PHP Version
W3 Total Cache
Super Progressive Web Apps
WordPress Import

Jetpack – Activated features:
Enhanced Distribution
Gravatar Hovercards
Image CDN
Lazy Images
Monitor
Notifications
Protect
Publicize
Related posts
Secure Sign On
Sharing
Site Stats
Sitemaps
Subscriptions
Widget Visibility

I have previously been using W3TC, Autoptimize and “Super Progressive Web Apps”, but those should have been disabled when you visited the site.

I have just run through the plugins, and tried to check if any of them should generate cache. Could you try looking again?

If there’s something specific you mean indicate that the content is cached, please do let me know, then I’ll look into if I can purge the cache even further

It is true that the scoring does not have an effect. Nevertheless, I guess people are using our plugin in order to get an overview over the state of their site. This is not possible unless you traverse through every post manually.

I would like the suggest this as a feature request. I find it rather important for useability and adoption of the plugin.

You are right, that was the problem ??
Was on my way in here to update the question as I saw you had already answered ??

In Chrome the console tells me this:

Resource interpreted as Stylesheet but transferred with MIME type text/html: “https://squazz-df5.kxcdn.com/wp-content/cache/autoptimize/css/autoptimize_a4b6a6c6c347f675c5c6938486ff81b6.css&#8221;.
Resource interpreted as Stylesheet but transferred with MIME type text/html: “https://squazz-df5.kxcdn.com/wp-content/cache/autoptimize/css/autoptimize_5d3b1c2d0be95d49aa25ba8aa2293f92.css&#8221;.
autoptimize_68a35a8d1376be081a04024c9eec6829.js:1 Uncaught SyntaxError: Unexpected token <

@dmajwool you have to add it in functions.php, as you do with almost all filters you write yourself ??

I wrote more about this on my danish blog: https://squazz.dk/teknologi/ninja-forms-capabilities/

It’s in danish, but a google translated version is here: https://translate.google.com/translate?sl=auto&tl=en&js=y&prev=_t&hl=en&ie=UTF-8&u=http%3A%2F%2Fsquazz.dk%2Fteknologi%2Fninja-forms-capabilities%2F&edit-text=

Sometime in the future, I plan to translate everything to english myself, but I havn’t got there yet :/

Thank you so much for both the update and your effort to make this work when WPML doesn’t care ??
I REALLY appreciate it, and I’m sure many others will too ??