justinhill001

SOLVED. I had to identify the theme navigation JS and try excluding that in order to demonstrate to RapidLoad that there was a bug in their plugin. Once the issue was verified, they were very happy to work on it.

They have addressed the issue and released a new version of the plugin.

Menus are working correctly now.

I stand corrected. I blundered my way through to the location of the javascript for the theme and excluded all of it – i.e.

/wp-content/themes/twentyseventeen/assets/js/(.*).js

from RapidLoad’s optimisation and it made no difference. RapidLoad’s support has acknowledged the issue and are thinking about it.

@jordesign, I’ve dealt with Rapid Load in the past – fixing a problem with Google Site Kit – and when I bring this to them they will simply tell me to exclude the relevant JS from optimisation by entering its path in the field provided. For example, I fixed the Site Kit issue by entering “/wp-content/plugins/google-site-kit/dist/assets/js/(.*).js” into that field, which I learned elsewhere on this forum. RapidLoad support couldn’t tell me that.

RapidLoad also can’t tell me the name of the JS for the theme’s menu. I have to try and find that out somewhere else.

• This reply was modified 9 months, 1 week ago by justinhill001.

WP Rollback works as expected, and rolled twenty seventeen back to 3.3 seamlessly, in a couple of clicks.

That’s the good news. The bad news is that this didn’t fix my menu problem. Yet.

I am going through endless hoops dealing with caching and CDN but can now 99% confirm it’s RapidLoad that is messing up the menus on mobile devices. Rolling back to 3.3 was a red herring.

RapidLoad allows me to exclude specific CSS/JS from optimisation. I’ve already had to do this to get Google Site Kit working right. Turning off JS optimisation fixes the menu problem.

Can anyone advise what JS I should add to the RapidLoad exclude list to protect the menu stuff in twenty seventeen?

Specifically, it is the “delay javascript: load JS files on user interaction” option that breaks the menu.

• This reply was modified 9 months, 1 week ago by justinhill001.
• This reply was modified 9 months, 1 week ago by justinhill001.
• This reply was modified 9 months, 1 week ago by justinhill001.
• This reply was modified 9 months, 1 week ago by justinhill001.

It seems there’s a plugin called WP Rollback that will allow me to roll the theme back to a previous release. I’m going to try that tomorrow (after backing up!)

@motkar, thanks for your advice. I’m afraid I don’t understand it…

Update: I’m grateful to @properlypurple for introducing me to the Health Check plugin. Unfortunately, @jordesign, it seems that even if troubleshooting mode is enabled on the desktop, it isn’t when logging in from a mobile. So, I have to enter troubleshooting mode from the mobile itself, which is pretty frustrating going back and forth turning plugins on and off.

Frustratingly, I discovered in the course of all this that my menu opening problem doesn’t happen ANYWAY if I’m logged in. To be clear, if I browse the site while logged in on the phone, the menus load closed. If I log out, the menus load open.

So I installed the User Switching plugin. And:

In troubleshooting mode, with all plugins (except user switching) disabled, it looks like the menus are loading open when logged out via user switching. But this is really tricky to confirm; when I click a link is the phone loading the troubleshooting version of that page, or the live one? It’s very hard to tell.

But if this is true then the only remaining variable is the theme itself, and the possibility that it’s corrupt in some way. What would be the procedure to re-install the theme? Switch to another theme, delete twenty-seventeen, re-download twenty-seventeen, switch back to it? Losing all the theme customisation?

Oh, one other thing – just to prove I’m not imagining all this. If you run Google PageSpeed Insights, it shows little pictures of the site as it was loading. The menu is open in these images.

What’s that line from Jurassic Park?

Thanks for your assistance. I’ll try and dig into this in the next day or so. That said, I might try deactivating Rapidload first (either completely or disabling sections of it) to rule it in or out.

OK – do I need to actually set up the troubleshooting mode on the browser, or can I set it up on the desktop and then login to wp-admin on the phone?

Your list of “usual culprits” is interesting. I use Rapidload, which does all those things…

Thanks again for your advice!

Thanks, @properlypurple! Just one thing – the issue only presents on a mobile phone. Even with this troubleshooting mode enabled, won’t the mobile still load the live site?

To answer your question, it does it on all pages.

Just to clarify my issue w/ reference to motkar’s post – on my site the menu works correctly, staying closed, on a desktop browser when the window is narrowed to mobile-style. Opening/closing by itself only happens on a mobile device.

Just to close this out – I can confirm that Site Kit is still working and transmitting data some hours after setting the exclusion I mentioned above. Problem solved, and worth noting for other users of Site kit and RapidLoad.

James,

I have the paid version. I did raise a support case with RapidLoad, and they told me to add the Site Kit scripts to the exclusion list (but of course they couldn’t tell me what they actually were).

I will certainly confirm to them your comment that the default settings of the free version do interfere with Site Kit.

Thanks James. I’ve added /wp-content/plugins/google-site-kit/dist/assets/js/(.*).js to RapidLoad’s exclusion list. I’ll see how things go.

I’ve also discarded the Flying Scripts plugin. It was added by my hosting provider (WPX) during an optimisation but as far as I can see its functionality is duplicated by RapidLoad. RapidLoad does wonders for my PageSpeed and I can’t live without it.

I spoke too soon. A few hours later, the tags stopped firing again. Deactivating RapidLoad fixes it.

I suppose the delay before it fails is something to do with caching and CDN.

RapidLoad’s settings allow me to enter javascripts to be excluded from delaying and/or deferring and/or optimisation altogether and I want to try excluding whatever the Google tag files are from optimisation. Can you tell me the file name(s) I need to enter in that field? Is it just ‘gtag.js’?

• This reply was modified 10 months, 2 weeks ago by justinhill001.