Search results

I could probably make an option to disable cache busting, but it does seem like it would make more sense for that plugin to be able to recognize full URLs (including parameters) if they are trying to pick up URLs via regex. Alternately, if it's just a matter of the plugin using a default local...

It's not possible to do it for arbitrary domain that isn't related to the license. It does allow you to run on a test site for your site (for example test.example.com), but if the domain itself is completely different, there's not a way for it to pick it up as the license key is hashed against...

Wouldn't that be the opposite? It knows it's *not* on the domain root, so it doesn't do things as if it was. It doesn't add www to the suggested R2 domain, it takes what the site is already using and prefixes it with media., but it's only that... just a default, you of course can pick anything...

For individual files, you can already do that by manually moving a media item from R2 to local. I did add the ability to define extensions to exclude by default when uploading a new file in the next version. If you add this to your wp-config.php file, it will not send files with the extension...

It’s a little tricky because people can have different sites using different versions. That’s why there’s not just a universal download link (with it being both site and version specific). Alternately, you can download the right version for your site from the license page here...

If you edit the wp-content/plugins/app-for-cf/src/DigitalPoint/Cloudflare/Base/Pub.php file, and change this: $cloudflareAppOptions = $this->cloudflareRepo->option(null); ...to this: if (is_plugin_active('gravityforms/gravityforms.php') && !empty($GLOBALS['post']) && $GLOBALS['post']...

Gravity Forms has a support document more or less saying you can never cache it’s pages: https://docs.gravityforms.com/faq-on-cache-and-script-optimizer-issues/ Probably similar with Stripe (and other payment processors). If you are letting guests (people without accounts) make payments...

What exactly isn’t working as expected if you enable the Guest page caching within the plugin? I’d rather address whatever isn’t specifically working in your setup rather than reinvent it from scratch (again).

Guest pages are are the HTML pages rendered for people not logged into an account on your WordPress setup. They are a little different because logged in users have parts of the page unique to them (for example showing their avatar or username they are logged in as). Guest pages are able to be...

Cloudflare does allow it, but only with their Enterprise plan. There isn't really a way to bypass Cloudflare's own requirement for certain things for certain plans they offer (it would be great if everything was available for no cost, but I suspect it would be hard for them to stay in business...

The caching mechanism is at the network edge (meaning it doesn’t go back to the origin server to serve the cached content, so it can’t check any logic on the origin like something from a plugin). That being said, you can fine-tune the cache key. For example you can choose to ignore query...

It definitely has potential downsides. Like if you are adding different admins on a regular basis you need to regenerate the rules for the new admin email addresses. It’s also not uncommon for certain plugins to be doing things within the wp-admin area that isn’t strictly for admin users...

If something needs inbound access to the WordPress admin area, you would want to whitelist their IPs (if that’s an option) or maybe whitelist the specific URL you need to allow them to access. That being said, the error you posted is a Cloudflare API error. Double check that the API token you...

I was able to track down a potential issue, but it's limited to multisite setups. Are you by chance using a multisite setup?

I’ve actually reached out to them before, but never heard back. It would be nice if WordPress had an abstracted filesystem where everything just worked with that without custom code needed for every plugin to work with every other plugin. But unfortunately it’s a drawback of WordPress. I did...

It's already on the radar, but it's also not something that's not currently a high priority. It's not quite as simple as just offering different pricing, it would require a lot of backend work as well with rebuilding how the entire licensing system works. Also might need to change in general how...

it’s really just fopen itself. If opening the file as a stream (with fopen) fails for whatever reason, it falls back to reading the file into memory. I could put together a custom debugging version that outputs some additional info when using CLI. Might help track down the “why” it may not be...

Actually, I just remembered, if a site specifically disables the WordPress cron system via the DISABLE_WP_CRON constant in their config.php file, it *still* runs, just not as a background task. It might be worth checking WordPress' internal cron "option" which tracks queued cron tasks. SELECT *...

Updated the categories on individual posts/pages, or edit the categories themselves as a whole (like renaming categories)? Hmmm... not able to replicate it (works as expected when I test it). A couple things to check... Does the WordPress site have WordPress' cron system disabled? The purge...