Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renamed assets won't upload to Cloudflare R2 #209

Open
dgagnon720 opened this issue Apr 27, 2023 · 0 comments
Open

Renamed assets won't upload to Cloudflare R2 #209

dgagnon720 opened this issue Apr 27, 2023 · 0 comments

Comments

@dgagnon720
Copy link

Describe the bug
It is not 100% of the time but only sometimes and I didn't know why it works or not but with Cloudfare R2, when an asset with the same name already exist and the option to overwrite it is disabled, Media Cloud renames it but it won't upload the renamed assets to the cloud and it keeps refers to it in the post.

To Reproduce
Steps to reproduce the behavior:

  1. make sure overwrite existing files is disable under cloud storage settings
  2. Uploads a file to the cloud
  3. upload a second file with the same name

Expected behavior

  1. media cloud will rename it
  2. check your cloud storage and the renamed file did not exist.
  3. if you added the media in the post editor, the post still refers to the renamed asset in the cloud but this file did not exist.

Screenshots
If applicable, add screenshots to help explain your problem.

Server (please complete the following information)

  • Operating System: Linux
  • PHP Version: 8.1
  • Web Server: Nginx
  • Using PHP-FPM? YES
  • Using WordPress Cron? YES

How did you install the plugin?
Downloaded form freemius

Additional context
This isn't happens everytime but once in a while and I have more than one site with this setting (Wordpress 6.2, php 8.1, media cloud 4..5.20, Cloudflare R2) with the same behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant