![]() ![]() I will be eternally grateful to anyone who could help me solve this quickly, thank you very much! The weird part is all the rest of the images load fine but just the slider and the logo won’t load. At this point the file uploads issue isn’t even one of my main concerns but having the site load fully is all I could care about. I tried everything from changing permissions to uploading directly to the Wp-Uploads server and having a plugin read it but nothing works. It took me a while to understand what the client was saying because I was viewing a cached version of the page where everything was working. Lo and behold I wake up the next day to a very angry client because the top logo and main slider don’t even load! I go into the media library to try change the images and NONE of the new images I upload are read, it’s just a blank white square where the image thumbnail should’ve been. I took backups of everything and FTP’d into the server, downloaded all the files from the subdomain and uploaded everything into the Public_Html folder and changed the url in the configuration file. I created a subdomain (‘’) for testing on the hosting account and after I and the client was happy with everything, decided to move to the main domain replacing the old website. I’m wondering if someone could help me out with this issue I’m having because I just CAN’T figure out what’s happening □ This entry was posted in Web Development Tips. I genuinely hope I was able to help another soul get past such a silly default setting. I figure there are more people like me out there who want to solve problems like these, and search the Internet for solutions. And how much you’re willing to get things right. It just comes down to how much patience you have. I would have been done with my image uploads for this project.īut problems like this eat at my soul. You would have been done an hour ago.” And you would be right. You could say, “Nic, why not just knock down the image size in Photoshop first. Make Nginx happy, and your troubles go away. The Nginx layer comes before PHP so that’s why the error appeared so quickly after trying to upload, and that’s why it failed. Save the template (I do a Command-S) but I think closing the editor will save it as well. Most images bigger than that are just way too big as a starting point. ![]() You can set the value to whatever you want. Add another line with the following setting: client_max_body_size 10M Open up the Nginx template, and go to around line 18. In MAMP PRO, the global nginx settings (and PHP, etc) are located by going to File > Edit Template. Increase NGINX client_max_body_size !!!!!!!!!!!!!īy default, in MAMP PRO, this is set to something like 1MB. Disable the “ big image size threshold“: add_filter( ‘big_image_size_threshold’, ‘_return_false’ ) - I thought this would surely do it, but it didn’t fix the problemīut the one thing I didn’t do was the one thing I needed to do:.And it clocked in at 1.3 MB which is big for serving up on web, but not that big if you’re going to use an image optimization tool like EI started searching on Google and did everything everyone said to try, even though some of them didn’t seem to make sense: Yea, my file was a few pixels bigger than the recommended 2500px (2560px wide to be exact). Post-processing of the image failed likely because the server is busy or does not have enough resources. Today I ran into the image roadblock that WordPress provided. I still can run Grunt on my Mac from terminal and do things pretty much the same as if I was developing on a cloud server like AWS Lightsail. This new project is using a MAMP PRO with a hostname, https, Nginx, and MySQL 5 (because my version of MAMP does support MySQL 8 and I need to pay to update). But as I typically do, I persisted through and learned how it works. I’ve had MAMP PRO for a while, but never got the hang of it. While I have a cloud server dedicated for new builds and development work, I decided I’d try development for this next new project locally on my Mac, using MAMP. Why? Out of convenience in showing the client, and probably because it was easier for me to push them live (back then, circa 2013). I started building sites that way a long time ago, and it just stuck. Typically when I build out a new site, I do it on a real server hosted off-premises. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |