WAIT: Bricks + WPRocket Bugs on IOS

Bricks has a weird issue on mobile with defer JS on WPRocket where after visiting a page and going back to the menu the sub nav stops working.

There is overlap of features with WP Rocket and Bricks like emojis and lazy load which can cause issues. Their team is pretty happy to work with us assuming we can isolate issues. I’ve noticed their newest version of WP Rocket has a checkmark to defer specific plugins which could include conditions specific to Bricks. Ideally, we could have specific non-conflicting settings enabled when WPRocket is on.

"There is a known issue on iOS devices when Delay JavaScript Execution feature in WP Rocket is enabled. The option is causing the links need to be clicked twice to work.
We have it reported here: https://github.com/wp-media/wp-rocket/issues/3142

Unfortunately, there is no solution for the issue yet, and other optimization tools are facing the same problem.

As possible workarounds you can:

  • Try the FastClick library workaround - the same approach can be achieved with this helper plugin: WP Rocket | Use the Fastclick library. This workaround doesn’t fix the problem for every site.
  • You can disable WP Rocket’s Delay JavaScript Execution feature, and try the equivalent feature provided by WP Meteor plugin in case the issue isn’t there with them.
  • Try replacing the Delay JS script used with the one that was used in past versions where the issue didn’t happen:
    • The file can be found at /wp-content/plugins/wp-rocket/assets/js/lazyload-scripts.min.js
    • And a previous version of WP Rocket where the issue didn’t happen: 3.11.4.2.
  • Try one of the alternatives suggested in this article.
  • You could also try a solution like this one mentioned in the comments: Delay JS - Links needs to be clicked twice on iOS / Safari · Issue #3142 · wp-media/wp-rocket · GitHub (though I’m not sure how well it would work or if it would have unintended side-effects)

In the meantime, you can subscribe to the following GitHub issue to get notification about updates and the release date for the fix:

Hi Adam,
Thanks so much for your report!

I skimmed the GitHub thread and this seems to be a general problem with WPRocket (as you said), not a Bricks problem. Accordingly, I am confused about what we should do with the report.

Is it just meant as a hint for other users? If so, I would move it to “How To” if necessary, since as far as I can see there is currently nothing we can do about it.

Best regards,
timmse

1 Like