First, a little background: I’m a copywriter by nature and trade, but in the spirit of expanding my services since the 2008 economic collapse, I’ve found it more difficult to make a decent living from spinning words alone. Over the last year, I decided to expand my services by spinning some WordPress love; that is, making content-driven websites by utilizing WordPress as its non-label use as a content management system (CMS) rather than just a blog. It started with using basic themes and plugins, of course, but it has evolved into getting deeper into the coding side of things. I still have quite a bit to learn, but I’ve found a couple common problems here and there that are rather difficult to find adequate answers to. In the spirit of community, I’ll share some of the problems and solutions here with the hope that the next person’s project will be a bit more manageable.
A Word on Shared Servers for WordPress, including BlueHost
I’ve been building my own sites and client sites via BlueHost for awhile now. I’ve had some use with GoDaddy (when forced to by a client), but whether you’re using WP’s five-minute install or the one-click install offered by BlueHost and GoDaddy, there is one key difference in my user experience thus far. BlueHost updates most of their files in real-time; this means that when you install WordPress, via either method, the installation and usability of the application is instant: you can get right to work and dig in. With GoDaddy, it is not instantaneous. They work on a cycle system, so if you install WordPress, the installation won’t take effect and be ready for use until the next cycle process (depending on the time you install WP, this could be anywhere from an hour to 24 hours). If you’re like me and like to get to work on a site immediately after installing WordPress, then this can be a bit frustrating if a client is forcing you to use GoDaddy. While I would love to use my very own server, I don’t have this luxury at the moment, so all my work has been done using BlueHost. I never had even the slightest issue with them until recently.
WordPress Max File Size Limit with BlueHost
A client project I took on required me to build a site that hosts 1.7G worth of files, with the biggest file being 560M. This normally doesn’t sound like a problem, right? The standard WP Max Upload File Size is generally set to 10M, though some shared hosting companies bump it down to 8M or even 2M. BlueHost had theirs set at 10M. Now, this can be edited from your php.ini file, but many hosting companies (even those whom advertise “unlimited space”) don’t particularly care for users messing with those values. I’ve read numerous issues regarding BlueHost being one of those companies. After adjusting the settings in my php.ini file a few times, I found they were overwritten with the default values nearly instantaneously. Not wanting to sour my relationship with BlueHost, and wanting to check on their “do not use us as file storage” policies, I placed a call to their tech support.
A Solution for BlueHost Users
During my call, the tech support guy ok’d my use of the space in reference to the Terms of Service, and then told me I could adjust my space limits in the php.ini file. After I told him that it was overwritten several times, he asked my username, followed by denying that BlueHost did it, but he strongly suggested that I try it again. After the phone call, I adjusted my php.ini again, and – voila! – no more overwriting; though that never happened to begin with, right?
I reset my values yesterday to 100M per file, before I realized the biggest client file was 560M. I then adjusted it a second time to 600M, hoping that BlueHost wouldn’t overwrite this change. They didn’t, and besides the downtime in uploading the new files, there’s no trouble.
How to Edit Your php.ini File
All values for WordPress’ max upload file size limit are held in the php.ini file in the root directory of your server. There’s not separate php.ini files for each WP installation, rather, there’s one that covers them all. Instructions:
1. Call BlueHost, tell them your username, and that you need to edit your php.ini file. They may tell you to go ahead and that you didn’t need to make the call, but this was not the case for me and a few others. Their answering time is fairly quick, so it shouldn’t be more than a 5 minute call.
2. Log onto your CPanel. Click on File Manager under Files.
3. Locate php.ini file in your /public_html/ directory and click to edit (doesn’t matter if you use the standard editor or the code editor).
4. Under Resource Limits, up them. I changed mine to the following, but depending on your project, you may not need anything this big (keep in mind I was working with a 560M file here, that was already compressed). My new limits: max_execution_time = 12000, max_input_time = 1000, memory_limit is 600M.
5. Under Data Handling, you’ll find the called out phrase “Maximum size of POST data that PHP will accept”. Directly underneath this, change your post_max_size to equal your new memory_limit from above (600M for me).
6. Under File Size, you’ll see the following phrase called out: “Maximum allowed size for uploaded files”; underneath this, change your upload_max_filesize to an amount equal to your post_max_size (again, for me, 600M).
7. Save the file; you may need to refresh the admin panel on your WP install for the change to take hold. If you’re on with BlueHost, this should be instantaneous. If you’re on GoDaddy or another shared server, this could take a spell.
8. If this change isn’t immediate, call BlueHost.
Hope that helps! Happy uploading!



