livingmiracles

Hi @isaumya,

Thanks for letting us know what you could. We’re just loving this plugin overall that we use on most of our WordPress sites, which felt like an answer to a prayer for us. So we wanted to at least check in with you and see if there was any way we could recreate the type of Cloudflare caching that this plugin provides on our Joomla and Moodle sites as well. Thanks for at least confirming that there isn’t a way.

Take care.

Hello,

Since it has now been a little more than six months since I first opened this support topic, I wanted to check back in. Has BestWebSoft by now implemented the compatibility fix to this “reCaptcha by BestWebSoft” plugin so that it will work with the “Restrict Content Pro” and “Paid Memberships Pro” membership plugins? Any update about this would be greatly appreciated.

Thank you.

Great, thank you for the extra info!

Hi @isaumya,

Thank you for confirming this. It is unfortunate that this occurs with visual page builders, but if that’s the way it is, we’ll deal with it.

Thank you for also mentioning that SEO redirect option. I had seen it before but hadn’t tested it out yet. I tried it on the site and, from what I can tell, it works very nicely. Not sure how it specifically works though, as I didn’t see any change occur in the .htaccess file on the site after enabling the option. If you’re open to sharing more about how this option for redirecting logged-out users only works exactly, I’d be curious to hear and appreciative of the info.

As for this issue itself, it feels as solved as it can be for us for now. So I’ll mark this topic as resolved with this reply. Thanks again!

Hi @andrewsupport,

This issue/incompatibility is not resolved for us and we have not found a solution yet for this. At this point, we are indeed waiting for BestWebSoft to investigate the issue and make the necessary changes in the next plugin update to resolve this. I don’t believe there is anything more we can ask until BestWebSoft resolves this issue.

Great, thank you, @isaumya, for reviewing the log results I shared and confirming that this all looks correct to you in how it is working.

In this case, I feel this support topic is now resolved.

Any update about this yet? I would like to mark this “issue”/question as resolved, but I would just want to have those log results reviewed/checked first before doing so.

Thank you.

Hello,

+1 to this thread. As @jontprice mentioned, we have the same question/desire. It would be very helpful to have some control over this so that we can utilize the other benefits of these database optimization functionalities.

We hope this gets implemented soon if it isn’t already possible somehow. Thank you.

Thanks, @isaumya.

I had checked the browser console to see if any errors were occurring, but I didn’t see any. However, I’m not sure which of the other changes I recently made on my site did it but this issue appears to be resolved and I can use the front-end visual builder on my Divi site with this plugin. In this case, it does appear that this was indeed a configuration issue on my end and not an issue with the plugin.

As for the other “issue,” I went ahead and changed the settings and checked the log afterward. It appears the plugin is clearing Cloudflare cache for the page I’m editing, as well as the author’s page, the feed for the author’s page, and then the home page. I do have the “Purge cache for related pages only” setting enabled. My understanding is that this would only clear cache for that particular page but perhaps I misunderstand and it clears a little bit more than that? Is there another setting I should enable instead so that only that particular page, or at least to not the home page included, have their Cloudflare cache purged?

The following are the log results I got after I made a small edit to a particular page, saved the page, and then manually cleared the Cloudflare cache for that page using the “Purge cache for this page only” option in the admin toolbar:

[2021-06-14 04:25:12] [preloader::task] Preloading complete
[2021-06-14 05:06:46] [cache_controller::purge_cache_queue_write] queue file not exist
[2021-06-14 05:06:46] [cache_controller::purge_cache_queue_write] URLs in purge queue Array
(
    [purge_all] => 
    [urls] => Array
        (
            [0] => https://example.com/EditedPage/
            [1] => https://example.com/author/AuthorPage/
            [2] => https://example.com/author/AuthorPage/feed/
            [3] => https://example.com/
        )

)

[2021-06-14 05:06:46] [cache_controller::purge_cache_on_post_edit] Purge Cloudflare cache for only post id ### and related contents - Fired action: clean_post_cache
[2021-06-14 05:06:46] [cache_controller::purge_cache_queue_write] URLs in purge queue Array
(
    [purge_all] => 
    [urls] => Array
        (
            [0] => https://example.com/EditedPage/
            [1] => https://example.com/author/AuthorPage/
            [2] => https://example.com/author/AuthorPage/feed/
            [3] => https://example.com/
        )

)

[2021-06-14 05:06:46] [cache_controller::purge_cache_on_post_edit] Purge Cloudflare cache for only post id ### and related contents - Fired action: edit_post
[2021-06-14 05:06:46] [cache_controller::purge_cache_queue_write] URLs in purge queue Array
(
    [purge_all] => 
    [urls] => Array
        (
            [0] => https://example.com/EditedPage/
            [1] => https://example.com/author/AuthorPage/
            [2] => https://example.com/author/AuthorPage/feed/
            [3] => https://example.com/
        )

)

[2021-06-14 05:06:46] [cache_controller::purge_cache_on_post_edit] Purge Cloudflare cache for only post id ### and related contents - Fired action: clean_post_cache
[2021-06-14 05:06:46] [cache_controller::purge_cache_queue_write] URLs in purge queue Array
(
    [purge_all] => 
    [urls] => Array
        (
            [0] => https://example.com/EditedPage/
            [1] => https://example.com/author/AuthorPage/
            [2] => https://example.com/author/AuthorPage/feed/
            [3] => https://example.com/
        )

)

[2021-06-14 05:06:46] [cache_controller::purge_cache_on_post_edit] Purge Cloudflare cache for only post id ### and related contents - Fired action: edit_post
[2021-06-14 05:06:46] [cache_controller::purge_cache_queue_start_cronjob] Purge queue cronjob started successfully - Timestamp 1623647206
[2021-06-14 05:06:54] [cloudflare::purge_cache_urls] Request URL: https://api.cloudflare.com/client/v4/zones/ZoneID/purge_cache
[2021-06-14 05:06:54] [cloudflare::purge_cache_urls] Request Body: {"files":["https:\/\/example.com\/EditedPage\/","https:\/\/example.com\/author\/AuthorPage\/","https:\/\/example.com\/author\/AuthorPage\/feed\/","https:\/\/example.com\/"]}
[2021-06-14 05:06:55] [cloudflare::purge_cache_urls] Response: {
  "result": {
    "id": "ZoneID"
  },
  "success": true,
  "errors": [],
  "messages": []
}

[2021-06-14 05:06:55] [cache_controller::purge_siteground_cache] Purge whole Siteground cache
[2021-06-14 05:06:55] [cache_controller::start_cache_preloader_for_specific_urls] Adding these URLs to preloader queue: Array
(
    [0] => https://example.com/EditedPage/
    [1] => https://example.com/author/AuthorPage/
    [2] => https://example.com/author/AuthorPage/feed/
    [3] => https://example.com/
)

[2021-06-14 05:06:55] [preloader::task] Preloading URL https://example.com/EditedPage/
[2021-06-14 05:06:56] [cache_controller::purge_urls] Purged specific URLs from Cloudflare cache
[2021-06-14 05:06:56] [cache_controller::generate_new_prefetch_urls_timestamp] New timestamp generated: 1623647336
[2021-06-14 05:06:56] [cache_controller::ajax_purge_single_post_cache] Purge Cloudflare cache for only post id ### and related contents
[2021-06-14 05:06:57] [preloader::task] Preloading URL https://example.com/author/AuthorPage/
[2021-06-14 05:07:00] [preloader::task] Preloading URL https://example.com/author/AuthorPage/feed/
[2021-06-14 05:07:02] [preloader::task] Preloading URL https://example.com/
[2021-06-14 05:07:04] [preloader::task] Preloading complete

If this all looks correct to you in how it is working, then I believe this “issue”/question is resolved.

Thanks, @georgesupport, for your response.

In this case, is there any ETA on the release of this update that will contain this login reCAPTCHA v3 compatibility fix and implementation on all login pages/forms? This information would be really supportive to us as we’re actively trying to find a solution for this right now.

Hi @isaumya, thanks for your response.

Yes, I’m using the Page Rule mode for caching and the URL indeed has the cache buster in it. The following is the full query string when I use the Divi’s “Enable Visual Builder” on a page in the front-end of the site: ?et_fb=1&PageSpeed=off&swcfpc=1

Ideally, I’m hoping to avoid using the Worker mode, unless I really need to on a site. We have many WordPress sites, many that use Divi, and many that can receive a lot of traffic/requests, so we would quickly use up that daily 100K requests limit if we’ll need to use that mode on many of our sites.

As for what I’m noticing with the single page/post caching, I don’t believe from what I can tell that the Home page is showing the contents of the single page/post that the Cloudflare cache is being cleared for. It isn’t a terrible thing that this is happening, just not ideal. Also, this doesn’t seem to clear the cache for other pages or posts on the site from what I’ve seen so far. It only seems to affect the current page/post the edit was made on and the Home page each time.

Thank you @isaumya! I ended up figuring this out and I’m seeing the correct cache-control headers now! I’ve been testing the plugin out more on some sites and it seems great so far. ????

I did run into at least one other issue so far and have some other questions, but I’ll open a new topic for those.

Hello,

I’ve been trying to set up this plugin on one of our most basic WordPress sites (miraclesacademy.org) and I can’t seem to get the static or dynamic page caching to work either. I’ve read through the FAQs and I’m not sure what the exact issue is on our site.

Here is part of the Header response I’m seeing:

cache-control: private, no-cache, no-store, proxy-revalidate, no-transform
cf-cache-status: BYPASS
server: cloudflare
x-wp-cf-super-cache: cache
x-wp-cf-super-cache-active: 1
x-wp-cf-super-cache-cache-control: s-maxage=31536000, max-age=60
x-wp-cf-super-cache-cookies-bypass: swfpc-feature-not-enabled

So the values for x-wp-cf-super-cache and x-wp-cf-super-cache-active look appropriate but then the cf-cache-status value is displaying “BYPASS” for some reason…

This feels like a great plugin and could be exactly what we’re looking for and need across our many WordPress sites, so we’d really like to get it to work to do some further use case testing.

Are you able to help us troubleshoot what could be causing the caching to not function properly? Please let me know what other details would be helpful for me to provide to figure this out.

Thank you.

Hi @benmeredithgmailcom,

Yes, that does clarify the situation. Thank you very much! ??

Hi @devnihil

Thank you very much for your response! From the information you shared, we were able to eventually (and somewhat accidentally) discover that by unchecking the “Inline all CSS?” option in the Autoptimize plugin (via Settings > JS, CSS & HTML > CSS Options) that we have installed on these sites, this would resolve this issue of the Open Graph (OG) <meta> tags not being seen by Facebook anymore.

So with what feels like a miraculous discovery, this issue feels finally resolved!

Thanks again and take care,
Living Miracles