fgilbane

Hi Anders:

Thanks for the quick response.

I use WPRocket for caching which has 2 settings for CSS: minify and combine. I turned off both and the problem went away. I then turned them back on one at a time and clearing the cache. And the problem hasn’t come back.

It turns out my WPRocket subscription expired 2 days ago and I just realized it earlier today since it appeared to be working, but that may have been an issue.

I haven’t been using a child theme. Though I can’t be absolutely sure I didn’t change something in the CSS, my intent was not to touch it when I moved to Hemingway to keep my life simple.

Anyway, I am all set, and love your them.

Frank

Thank you. Toggling the Load Javascript files in footer worked in every case but one. It works on Desktop with Safari, Chrome, Firefox, and Brave. And it works on Chrome and Firefox mobile, but *not* in Safari mobile on my iPhone 11 Pro running 13.2 or earlier versions of 13. But, t *does* work on my wife’s iPhone 7.

I noticed there were two “Toggling the Load Javascript files in footer” options in the Miscellaneous section that looked identical, so I toggled both.

Hi:

Everything is working now except on Safari on my iPhone pro 11 with iOS 3.2. See 1) below.

I tried excluding the script you sent but it didn’t help. I then turned off all JS minification and everything worked (including another problem not necessarily connected to Sassy, but occurred around the same time, where my hamburger menu links had stopped working). WProcket then looked into it got it to work with excluding a Sassy inline script, see 3), and jQuery, see (4.

Relevant correspondence with WProcket:

1)
ME: On MacOS the hamburger menu and sassy social sharing both work fine on Safari, Chrome, and Firefox. On iOS they both work fine on Chrome and Firefox, but on Safari Sassy Social buttons *don’t work*, but the hamburger menu does.
WPROCKET: Hm, I can’t reproduce this issue as yet. Could you make sure you’re testing in an incognito browser window and/or clear your browser cache so we can make sure you’re testing on the latest version of the site.
Which specific iOS device are you using? I’ll try to replicate the same conditions to see if I can spot the error that way.
ME: I still can’t get it to work on iPhone Pro 11, but it *does* work fine on my iPad Pro. If you still can’t reproduce it on an iPhone I’ll try a couple of more things and then report to Sassy and Apple.

2)
ME: I noticed you didn’t exclude the script that Sassy Social Share initially suggested I try and exclude (wp-content/plugins/sassy-social-share/public/js/sassy-social-share-public.js). I assume that it had no effect?
WPROCKET: Indeed, that didn’t seem to make any difference that I could see. However, I just added it back to the exclusions, in case it’s causing the iOS issue that you’re seeing. Let me know if that makes any difference.
ME: Still works fine. Don’t see any other issues.

3)
ME: What does the string you excluded from inline JS concatenation (heateorSssHorizontalSharingCountEnable) do?
WPROCKET: There is an Inline JS script related to sassy social share which needs to be excluded from Combine JS.
This is the whole script: https://jmp.sh/qTfDH9g
That string is just a way to identify the script to exclude it. You could use any unique string from within the script to identify it for exclusion.

4)
ME: Which problem did the exclusion of /wp-includes/js/jquery/jquery.js address?
WPROCKET: This is related to sassy social share. The above inline script relies on Jquery. If Jquery is included in the combined file it’s loaded too late – the inline script is already asking for it and it creates an error.

I have recently had this same problem, as well as problem of Sassy Social share links not working because JS optimization was breaking this script: wp-content/plugins/sassy-social-share/public/js/sassy-social-share-public.js according to the developer.

My JS optimization is done by WProcket so I tried to exclude the script. That didn’t work, but when I turned off all JS optimization that fixed both the hamburger links and the Sassy social share links – so I have left it off. WProcket is looking into why the specific exclusion didn’t work.

I’ll report back when I have more info.

Thank you!
I tried to exclude that script in WP Rocket and that didn’t work. But when I disabled all JS magnification the problem went away. I have left all JS magnification off for now and will follow-up with WP Rocket about the specific exclusion not working.