Rocket Loader stop working Visual Composer FrontEnd Editor

bug

#1

When I turn on Rocket Loader, WordPress Visual Composer FrontEnd Editor is stopped working. Does anyone have a solution for it? :cry:

**My page rules settings:**
*example.com/wp-admin*
Cache Level: Bypass

http://example.com/*
Always Use HTTPS

*example.com/*preview=true*
Cache Level: Bypass

#2

I just now had this issue. Elementor doesn’t like Rocket Loader. Their suggestion was to add a Page Rule to disable Rocket Loader for Elementor…matching URLs that have “elementor” in them.

I was in a hurry, so I just turned Rocket Loader off while I edited the page.


#3

You don’t need the page rules to by-pass /wp-admin or preview pages, as they are not cached by default.

Also, you can set Always Use HTTPS on the Crypto tab.

So that would liberate your 3 page rules and you could use one to avoid using Rocket Loader.

However, since Visual Composer is always accessed from within /wp-admin, you could keep that first page rule and try adding the setting Rocket Loader to turn it off.


#4

I believe Elementor runs within a frame in wp-admin, which would require a rule to match Elementor outside of wp-admin. Here are their instructions on the topic:
https://docs.elementor.com/article/360-elementor-cloudflare-rocket-loader


#5

Ah, OK, I was just thinking Visual Composer. BTW, it would seem the 2 rules on the Elementor page could be just the first? :slight_smile: Have you tried?


#6

No. Next time around I’ll give it a try.


#7

If you check the help section of Crypto, following instruction will appear:

Reply to all requests for URLs that use “HTTP” with a 301 redirect to the equivalent “https” URL. If you only want to redirect for a subset of requests, consider creating an “Always use HTTPS” page rule.

That’s the reason I have created always use HTTPS page rule. Am I wrong?

Kindly guide me.


#8

I’m still confused is this useful for me or not?
example.com/wp-admin
Cache Level: Bypass

Am I need one more page rule? Such as,
example.com/wp-admin
Rocket Loader: OFF

At this time, I don’t have any plan to buy page rules! :disappointed_relieved:

Please guide me.
Thank you!


#9

You should see Page Rules as a way to create exceptions to the settings you apply to your website. Say for instance you domain is example.com.

Crypto > Always Use HTTPS
All pages from example.com, www.example.com, api.example.com, m.example.com etc will be redirected to HTTPS for visitors requesting http.

Now let’s say you need for some reason to have api.example.com NOT using https. Then you should turn Always Use HTTPS off on the dashboard, and create rules to match the other parts of your website for which you want HTTPS on. For example.

api.example.com > some settings
example.com Always use HTTPS

So that for the API section you’d not have Always Use HTTPS, for everything else, you would.

You should ask yourself this: do I want all pages from my website on HTTPS? If the answer is yes, then you should set this at the dashboard. If the answer is no, then you have to create the appropriate page rules.


#10

You can keep this page rule, and edit it to add the setting: Rocket Loader: Off


#11

Thank you so much for in-depth information regarding CloudFlare’s HTTPS or HTTP settings. I will follow your guideline.


closed #12

This topic was automatically closed after 30 days. New replies are no longer allowed.