Search results

Is it still happening? That's going to be a client-side error (browser). It could be that something is affecting the JavaScript on your page or possibly browser extensions that alter the page source (things like ad blockers). Do you by chance have a URL doing it that I'd be able to look at?

Just FYI, I ended up changing the constant to be CLOUDFLARE_SITE_URL. While other systems use CLOUDFLARE_DOMAIN, it's not exactly correct... it needs to be a URL (not just a domain). Given that, I went the route of using a constant that is more "correct" vs. follow what feels like incorrect...

If the front-facing URL of the site is different than the hostname for the license, the Pro version will not be activated. For example, if you had a Pro license for mysite.com, the only site within a multisite network that would have the Pro plugin would be mysite.com. So even if...

The Pro version of the plugin is license is attached to the hostname of the site. Meaning a single Pro license doesn't give someone unlimited Pro usage across 100,000 sites (if they had that many in their multisite setup). That being said, if the primary site within a multisite network has a...

If the URL you gave before is valid, it looks like a redirect is happening, but not to the full URL. A request for this: https://networkservices.stream/wp-content/uploads/2020/12/blue-vector-1.png ...is being redirected to this: https://networkservices.stream The fact that it's not even...

Are you missing the "c" in "concat"? You just have it showing "oncat" in your copy/paste. It also needs the https:// at the beginning of the R2 bucket hostname. The expression should look like this: concat("https://media.networkservices.stream", substring(http.request.uri.path, 19))

FWIW, it probably does make sense to give people flexibility to remap domains if needed (for anything, not just headless WordPress). So while use of the site_url filter would work already, there may be a situation where you don't want to remap everything. For that scenario, I added 2 new...

If I'm being honest, I don't have any experience with headless Wordpress, but if it's just a matter of swapping the internal site URL (cms.domain.com) with the frontend URL (domain.com), I don't think it would be particularly difficult. Specifically, the plugin already makes used of a singular...

The selective purge is automatic. You just *also* have the ability to do a full purge whenever you want. 😀

That’s how it already works. In fact, I’d argue it works a little better than the Cloudflare plugin since that one doesn’t get all the relevant URLs to be purged when a post is updated.

Hmmm... what's the permissions for that particular file? If you do a full ls for the file, you should be able to see it: ls -al /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/boot-fs.php Normally, that's going to be a general permission issue at the operating...

Ya, it was always planned to add support for third-party things (the Turnstile support was abstracted out already for that exact purpose). I just figured it made sense to add stuff as people wanted it, rather than try to cover all the things no one asked for. :) Will probably focus on Contact...

Right, but you are talking about something different. You are talking about a partial cache that relies on your origin server to piece the page together. This is a network edge cache system where the request is served in full from Cloudflare data centers, without needing to go back to the origin...

It’s rolled out in the latest version of you do the update from WordPress.org. It still will most likely need the existing cron task to be deleted after that.

It does not. It wouldn't make a lot of sense to serve cached content to logged in users since parts of the page is going to be unique to them (for example showing them they are logged in). If you *are* seeing cached content being delivered to logged in users, maybe your site is using...

I can switch your license to a new domain if you’d like, just let me know the new domain. Licenses are always bound to a specific hostname/domain (it would be a new license in that case).

Oops, wp-content/plugins/app-for-cf/src/DigitalPoint/Cloudflare/Base/Pub.php.

Yep, it’s already scheduled for the next release.

I think I figured out what's going on. It's dependent on PHP versions, so that's why I wasn't able to see it until I started switching through various PHP versions (some versions of PHP don't like being told what the variable name is going to be for named parameters). In the...

It certainly is something to consider if WordPress is taking ~4s to generate a page. Personally, I don't, but my sites tend to be lightweight/fast so they definitely aren't taking that long for the origin to spit them out. You may want to double check if you have Cloudflare's Smart Tiered...