Search results

You can do invoices with PayPal, however we don't sell anything with invoices because we don't deliver things with payment terms (future payments). An invoice would be if someone wanted a quote for something, but hasn't paid and then a company's accounts payable department mailed a check for it...

Sorry, there isn’t any plan. There isn’t an invoice in the system since payment is made before product/service is given. From a business standpoint, an invoice is a request for payment for something (which we don’t do since payment is required first). Your PayPal account should serve as a...

Okay, so the next version also has a new mechanism so you can optionally define filters by using a PHP closure within your standard wp-config.php file. This will allow you to leverage your own filter code, but without cluttering/adding complexity to the standard UI. It still would be more...

You can do whatever you want really... that's why I was saying it's the best way to do it because it's not only flexible, you can literally do whatever you want with it. So whatever situation is unique to you, you can do. That particular example adds another cookie to the Cache Rule, but say you...

I'm not going to absolutely say no, but it would be very far down the priority list. It really would be better situated within the filter mechanism. It would be trivially easy for any third-party plugin to add whatever the custom cookie they are using and not relying on their users to write...

Maybe… although things like that are a balance between “easy to use” and functionality. If every possible thing was added, the settings/UI would become an overload of things that 99% aren’t going to use. One thing about the cache rule for guest page caching is it’s written to Cloudflare Cache...

It does work with WooCommerce, because WooCommerce uses WordPress Media to store images. I believe Rank Math does as well (although never used it, so can't say 100%... but it's my understanding that it stores media as WordPress Media). I think there's maybe some confusion on what R2 is/isn't...

If a plugin uses WordPress Media at it's core to store it's images (or files), it would work. If it uses something custom they built that's not leveraging the WordPress Media functionality, it would not store those files in R2. Unfortunately, WordPress core doesn't have an abstracted filesystem...

Licenses are $89 per site (it’s a perpetual license… meaning you aren’t forced to pay annually to continue using it). As far as compatibility with various third-party systems/plugins, if they utilize WordPress Media, they should work. If they don’t utilize WordPress Media, it’s not going to...

Let me know if there are any issues. I know it’s not the most ideal way of doing it, but it was the compromise/solution to some users taking advantage and them having 25 unrelated “dev” sites on a single license.

The licensing server automatically allows hostnames a level up. For example, if your license is for example.com, it would also work for a site with the hostname of staging.example.com or dev.example.com.

Oh ya... just in case anyone else sees this thread, the Pro version is an extension of the free version, it's not a standalone plugin (the free version is required as the Pro version extends it's internal PHP classes).

Are you getting any sort of error popping up? Do you have shell access on your server (might make sense to rub a test to make sure the underlying network connectivity is working… if the server can’t communicate to Cloudflare API endpoints, it would be a huge problem)?

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...