I've moved a legacy site on Wordpress 3.8 from one server to another. The new server is on PHP 7 and I continue to get the error below:
Your PHP installation appears to be missing the MySQL extension which is required by WordPress.
I've tried installing the Wordpress command line tool WP-CLI but still get the same error.
What should I try next?
You are going to need to do a manual update.
Download the current/or version you need and once you’ve downloaded it, extract the zip file to your computer. Then, open the folder that contains all of the WordPress files and delete the following items:
The wp-config-sample.php file.
The wp-config.php file (you might not see this file – just make sure to delete it if it’s there).
The wp-content folder.
Once you’ve deleted those items, upload the remaining files/folders to your server via FTP. When prompted about duplicate files by your FTP client, tell it to overwrite all files:
Facing an error while uploading images in Wordpress 5.3:
Post-processing of the image failed. If this is a photo or a large image, please scale it down to 2500 pixels and upload it again.
Fixed by increasing client_max_body_size to something like 100/200M(if you use nginx).
This same issue I faced after updating my WordPress to latest version 5.3. For a quick solution as of now, you can get over this by uploading the images to the media library first. Currently, if we are uploading images from anywhere else it’s showing the same issue.
I hope it helps.
I have tested it on my own website.
Hopefully, team WordPress will fix this soon.
WordPress 5.3 introduces this feature but it a bug. Until a WordPress update is released with a fix for the error, this is how you can disable this.
Simple add this line in your child theme functions.php file.
add_filter( 'big_image_size_threshold', '__return_false' );
Just encountered this bug. There was an apostrophe (') in the image's filename - once I removed it, all was fine.
Uploading from incognito window solved my problem.
WordPress 5.3
Here is one more step to help you debug. Have your inspector open to the network tab and look at the post request and its response.
In our case the issue was a bad AWS IAM policy not allowing uploads to the S3 bucket.
Only viewing the message there was what lead us in the right direction to fix the issue. The WordPress error is pretty generic for (server did not respond with success).
I recently received this error because I had already uploaded an image with the same filename. I don't know why it couldn't say something accurate like "duplicate file name" instead of something wrong and meaningless like "if this is a photo or a large image, please scale it down to 2500 pixels and upload it again."
I got this error but it wasn't a Wordpress nor a php problem. If you are using nginx be sure that the setting client_max_body_size is not set to the default 1M (which means 1Mb only for images passed in a POST not using multiform/part). I increased it and everything worked fine.
I have another solution for this, just had this problem gladly could figure how.
First see if your handling PHP 7.1 further
Then, you need enable mbstring in cPanel
In servers having a cPanel, it is easier to enable mbstring. So, for cPanel customers we enable mbstring as follows:
Firstly, we login to the cPanel account.
Next, we go to the Software section.
Here, we click the drop-down to Select the PHP version.
Now, select the PHP extension mbstring.
Finally, click the save button.
Image to what to select in PHP Version
Updating php to latest version , plus activating imagick module on from cpanel > select php version fixed the issue ...
Just thought I'd add my two cents since I stumbled across it looking for a solution myself before finding one. Now I've just experienced this exact same issue from around the web and it seems specifically related to Wordpress in versions of PHP 7.2+ or something which requires the installation of "Imagick" as well which for Redhat/Centos can be done like so:
dnf install php-pecl-imagick
I was able to use this to get the files to upload again though I still had some other issues which were resolved by updating the a lot of the limits of PHP via this guide: https://websiteforstudents.com/fix-file-upload-issues-with-wordpress-running-on-nginx-on-ubuntu/
Yet one more possibility ... after trying all these other solutions with no luck, I checked the console and was getting a 500 error on the js upload script. This was due to some code in functions.php that "worked" in older php versions but not 7.4. Non-helpful error message.
mageMagick (part of php) is causing the problem. So, i just added this lines to wp-includes/functions.php to tell WordPress to use GD editor instead.
add_filter( 'wp_image_editors', function() {
return array( 'WP_Image_Editor_GD'); } );
The simplest way to tackle this problem is to change the php version from 8 to 7.4. The complete details are in this article Post Processing of image failed
For SVG files, the number of these curves or shapes should not be too many.
I had the same error and tracked it down to my password-protected wp-admin directory. Removing the password-protection solved it. (The password protection adds lines in htaccess in wp-admin, you can also remove those).
But I did not want to take the password protection away. What solved it for me, while keeping wp-admin password-protected was adding the following in the .htaccess at site root level (so not in the htaccess file in wp-admin):
# Exclude the file upload and WP CRON scripts from authentication
<FilesMatch "(async-upload\.php|wp-cron\.php|xmlrpc\.php)$">
Satisfy Any
Order allow,deny
Allow from all
Deny from none
</FilesMatch>
Solution (and other solutions for other situations) found here:
https://docs.presscustomizr.com/article/229-fixing-errors-when-uploading-images-in-wordpress
I have a problem with my site. I migrate the website to another hosting provider and website not working now. I dont know why. I tried reinstalling the files, WordPress version, turn off the plugins and nothing happend.
Is there anybody with experience in this error?
Fatal error: Class 'Requests_Hooks' not found in
/data/www/22560/nejrychlejsiauta_cz/www/wp-includes/class-wp-http-requests-hooks.php
on line 17
This means that the folder "Requests" does not exist, try to get it from another WordPress installation of the same version, compress it and upload it to the site where the error is, then unzip it and it will work.
Regards..
this is what worked for me with this same exact error. I had the file Hooks.php that went missing. It is located here: wp-includes/Request/ With my install theres a file named Hooker.php and Hooks.php in that same directory. I had an identical install in another directory for a diff site and after cross checking the files, Hooks.php was missing on the broken website. After I installed it back on the site, the site works fine.
Hopefully this helps someone!
This happens in a case when you copy, e.g. in Total Commander, and have left the field "convert file names to lowercase" checked. As the path to the class file is not wp-includes/requests/hooks.php but wp-includes/Requests/Hooks.php
So uncheck this option.
I have a problem in my reponsive filemanager plugin. I am using this plugin. On my localhost version it running smoothly but after I upload on my Centos server I can't upload the documents running on MS Applications like (excel and ms word). It turns it into a zip folder.
My system runs on Codeigniter 3 HMVC and I also set the permissions of responsive filemanager (source and thumbs) permission to 777.
Images are working fine and txt. I also try to addType the ms application on my httpd.conf file and restart my server and it still same error.
Can you help me with my problem? I really want to use this plugin because it has a nice UI and settings. I don't know if it is a server problem.
I know its kinda late but this is how I solved this issue.
go into 'pathToFilemanager/include/mime_type_lib.php'
and comment or remove "application/zip" => "zip" from your $mime_types array.
Just installed the extension and it crashed my Magento site. I'm tried so but it not working Does anybody help what to do?
Just open app->etc->modules-> and find the .xml file that you currently installed. and Open this xml file and edit
<active>true</active>
to
<active>false</active>
then clean cache from var->cache
hope this will recover your problem.
thanks
Just delete the temperory file "maintenance.flag" from root directory then your website will works back.
Hope this will help :)
When an extension is being installed, a temporary file is created to set the magento website unavailable to the public. Check if the file is there and delete it. The file is named maintenance.flag and placed at the root folder of your magento installation.
Otherwise provide more information to get support but normally this place is for development problem and you should contact the author of the extension.