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

Review the need for filter_sideload_move_temp_file_to_s3() with WordPress 4.4 #74

Open
fklein-lu opened this issue Nov 19, 2015 · 2 comments

Comments

@fklein-lu
Copy link
Contributor

The according to the documentation, the filter_sideload_move_temp_file_to_s3() method of S3_Uploads exists to work around Core bug #29257.

This issue is marked as fixed for 4.4, so we should review whether we still need this method in the plugin. If we end up removing the plugin's method, we should put a check for the WordPress version requirement in place, and document this, similar to #69.

@lightningspirit
Copy link

In a recent installation with PHP 7.4 and WordPress 5.4.2, and using version 2.2.2 of S3-Uploads, I had to comment lines 55 and 66 to make sideload work.

FastCGI sent in stderr: "PHP message: PHP Warning:  copy(): The second argument to copy() function cannot be a directory in /<path-to-wp>/wp-content/plugins/s3-uploads/inc/class-s3-uploads.php on line 226" while reading response header from upstream, client: [REDACTED], server: [REDACTED], request: "POST /uploader HTTP/2.0", upstream: "fastcgi://unix:/run/php/php7.4-fpm.sock:", host: "[REDACTED]", referrer: "[REDACTED]"

@phpanos
Copy link

phpanos commented Apr 19, 2021

Any update on this? Still getting the issue using function "media_handle_sideload". At the moment we forked the plugin and removed the filter which solves our issue.

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

No branches or pull requests

3 participants