Fixing WordPress Directory Cannot Be Created Error
Recently, there have been cases where customer companies often requested corrections because they were encountering “Unable to create directory” or “wordpress upload could not moved to wp-content/upload” message errors while managing their portfolio.
The method I usually used every time was to connect to FTP and make changes, but I felt dizzy because there was another type of anomaly.
If you are not using a large capacity plan from the beginning, in this article, I would like to suggest your daily content management habits along with two ways to resolve errors.
If you have already uploaded a lot of content, I would like to introduce a free WordPress image optimize plugin.
Troubleshooting WordPress directory creation using FTP
When uploading media content, “wordpress upload could not moved to wp-content/upload/…” .” An error occurs or “The directory cannot be created” when installing the plugin. There are two main causes of errors.
This is because the media connection Croatia Mobile Number List path is incorrect or you do not have write permission.
Most likely it’s the second reason. Therefore, turn on FTP (I tend to use Filezilla ), connect, and then change the ‘file permission’ number of the wp-content/upload/media folder to 775.
Alternatively, you can change the upload itself to 775. If you install it yourself, 755 is suitable.
If the file path is incorrect, there are ways to correct it using a separate server command.
Second case number, check web capacity
This is an example of a WordPress directory creation issue that I experienced this time.
Our client was using the Cafe24 build-up plan. In fact, if you are not uploading a lot of portfolios, 1G of web space is sufficient.
However, many of the photos uploaded by our customers were over 16MB, and with about 400 photos uploaded, all 1G of space was used up.
When the problem was not resolved even after trying all methods such as changing file permissions and installation path, I asked the customer to check the hosting status just in case.
As a result, all web capacity was exhausted and no more content could be stored.
The client had already uploaded many photos, and it was very difficult to delete them and upload them again.
So, I first installed the Image optimize plugin EWWW Image Optimizer and ran the bluk optimize function.
