Search results

Still debugging it... Have not been able to replicate the issue in my end (not even with access to someone's servers that it was happening to). Thinking it might be a third-party plugin that is doing something/manipulating the media being uploaded in an unexpected way. That being said, there...

It’s in the “Previous Versions” section here: https://wordpress.org/plugins/app-for-cf/advanced/ But also, you don’t need to go back to previous free version for this, only the Pro.

You can download any specific version from the Updates tab here: https://appforcf.com/items/app-for-cloudflare%C2%AE-pro.1/updates

There were some changes to R2 uploading in 1.9.8 internally to make it more efficient, but still working out what is unique about the servers that it’s not working with. In the meantime, you can safely roll back to 1.9.2.

That part is intentional. At least as far as the file still exists if something goes wrong with the upload to R2. I'm going to send you a file privately to upload to your server to see if that fixes it for you.

If you look in the bucket in the Cloudflare dashboard, can you check if the file is in the bucket? Just trying to figure out if it was the transfer that failed or if the double check to make sure it was uploaded properly afterwards that is was the issue. Can get to your R2 dashboard here...

Right, but the Pro version is an extension of the free version (you must have it installed in order for the Pro version to work). The 1.9.8 version is a little unique in that the R2 transfer mechanism was made more efficient (it can transfer the files as a data stream rather than load into...

Are you using the 1.9.8 version of the non-Pro plugin as well? https://wordpress.org/plugins/app-for-cf/

If you are doing it via web interface/admin area, you might be running up against HTTP request timeout (assuming your site is using Cloudflare as a proxy ["orange cloud on DNS"]). 100 seconds to finish the HTTP request might not be long enough for the large files to transfer. If that's the case...

I went ahead and added a more specific filter that anyone can hook into for the next version. The app_for_cf_purge_cache filter allows you to control if a Cloudflare cache purge actually happens when requested. Additionally, it allows you to hook into the action to run your own code at that...

...so I poked around on this today and discovered that I forgot that the plugin is already handling it when using R2. Specifically, the URL of an image stored in R2 already has a cache-breaking mechanism appended to it, so if an image is updated (and specifically whatever is changing the image...

To be honest, I'm not sure there's a particularly "clean" way to do it. There's a couple issues: Not everyone uses the same email address for their WordPress admin user that they use to authenticate in Access (for example it's pretty common for people to use webmaster@yoursite.com for their...

Hmmm... those errors imply something is going on with the R2 servers. Specifically it tries to read the file back once it's uploaded to make sure it uploaded properly before it commits to deleting the local file. Just out of curiosity, are you running it with a ton of parallel processes or...

From: https://appforcf.com/threads/permissions-needed-for-app-for-cloudflare%C2%AE.3/ It does not, it's only the main zone settings. (Imagine if that was a thing and people clicked and wiped out their DNS records... heh) The widget name is informational, and only viewable in the Cloudflare...

Ya, the quick work around (before I get this update rolled out) is to temporarily up the memory PHP can use (enough to fit the largest files you want to migrate into memory).

Odd... I believe the API endpoints use the 2 newest options (TLS 1.2 and TLS 1.3), anything else is old and has security issues so they disabled using older SSL/TLS versions. Not so coincidentally, changing how files are uploaded (as a stream rather than loading into memory) was rolled out in...

Do you have shell access to your server? The sslv3 alert handshake failure error is saying the server is having an issue communicating with Cloudflare’s servers (most likely the server is trying to use an old/outdated SSL/TLS version that Cloudflare isn’t supporting).

It shouldn’t affect individual sites other than you can’t set a network-wide API token since that part was invisible. You should still be able to sty site-specific network tokens (needed in order to do things… like purge cache).

It's not because of WordPress 8.4, rather a line of CSS went missing somehow. This was missing from the admin.css file: .multisite #app-for-cf_settings .tab_content { display: revert; } ...not sure why it went missing, but it's been added back for the next version.

The ability to copy zone settings from a different zone on the same Cloudflare account has been added to the new version (1.9.7).