• I am no longer able to upload images to a number of my websites.
    I recently updated to 4.3.1

    I’ve looked at your answers to the questions of a missing .ini file and everything seems very old– 5+ years old– so I’m reluctant to just try some of the suggestions.

    Just got off the phone with GoDaddy who says its a WordPress problem.

    I am on a cpanel account with multiple wordpress sites and they are all having the same problem.

    When I try to upload a new image, I get this message: Missing a temporary folder.

    GoDaddy suggested I need to create a php.ini file (or .user.ini file) to tell the systems where to upload my images to. And I need to create one and upload it into every one of my wordpress sites. I this right?

    I would have thought that would be standard with the installation, if its necessary.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Same issue… just since upgrading to the latest WordPress Version.

    Same issue, website working fine Friday, come back Monday and none of my wordpress installations on my testing server are working. Checked with my ISP names.co.uk and nothing has changed on their server. My sites were already running WP version 4.3.1 and working fine.

    I’m seeing quite a few others asking this question around the forum, but no fix.

    I would have thought that would be standard with the installation, if its necessary.

    A php.ini file is a server file and, as such, is well outside the remit of WordPress and is never part of a WP install. Despite what GD say, this is a hosting issue and is something that they need to investigate & fix.

    I spent about 45 minutes yesterday on the phone with Hosting Support at GoDaddy regarding this issue. I had a couple of pieces of information that seemed to hold a clue to what’s causing this ‘can’t upload images’ problem. First, any site I have that was done in WordPress BEFORE GoDaddy’s server migration (this past month or two) works fine; I can upload images, files, etc. using WordPress 4.3.1 with no problems. However, the site I was creating new in WordPress AFTER the server migration is the one that gives the “missing temporary folder” error. The only resolution the tech could come up with was to have me upgrade the hosting package to ‘cPanel’ which would put the website on their ‘newer’ Linux servers. The comment from the tech was that the servers hosting the cheaper hosting packages were up to 10 years old and probably had “issues” of their own. So I did the hosting upgrade, and now I’m able to upload images. I tried to convince the tech that this IS a GoDaddy problem and we as subscribers shouldn’t have to upgrade to get WordPress to work, but he successfully skirted admitting that. No choice on my side… my client’s site had to be updated and this was the only way. Unfortunately I have three more to go, so will need to notify my customers that this will probably cost them to fix it. Ack!

    What worked for me:

    1. Literally nothing else on these forums
    2. Creating a .user.ini inside my WP root folder (which happened to be a subfolder) via FTP
    3. Creating a “tmp” folder inside subdomain root folder with 777 permissions via FTP
    4. Found the correct path to use for “upload_tmp_dir” by creating a wtf.php file
    5. Double checked whether my previous “fixes” were working by constantly referring to phpinfo.php – created in my subdomain root folder via FTP

    Here’s what’s in my .user.ini file:

    upload_max_filesize = 64M
    upload_tmp_dir /home/content/PUTYOUROWNSTUFFHERE/html/tmp/
    upload_tmp_dir = on
    display_errors = off
    log_errors = on
    error_log = /logs/

    Here’s what’s in the wtf.php file:

    <html>
        <body>
           <div>Your current path is: <?php echo getcwd() . "\n"; ?></div>
    <div>No, it is here <?php echo getcwd(); ?> </div>
        </body>
    </html>

    Here’s how I double checked if my other “fixes” were working (phpinfo.php):
    <? phpinfo(); ?>

    My setup:

    • WP installation within a subfolder of another WP installation
    • That subfolder installation is accessed via subdomain
    • …so there’s some redirection magic happening which may be why I ran into issues
    • Using GoDaddy shared hosting
    • Changed our GoDaddy hosting to a <b>Linux</b> server instead of Windows

    <b>Things to look out for before you give up and say nothing work for you</b>:

    • GoDaddy shared hosting “refreshes” your .user.ini file about every 5 minutes. That means you need to wait a hot second before deciding whether whatever fix you applied works or not.
    • GoDaddy shared hosting “refreshes” your php5.ini files about every squillion minutes on average. Wait forever. Or use .user.ini instead.
    • Your setup may not be the same as my setup. See ‘My setup’ above.
    • Don’t give up! Or, if you’re really at the end of your rope, ditch GoDaddy get a new web host.


    Things I tried or other resources that didn’t totally fix it for me, but might work for you:

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘missing php.ini or .user.in’ is closed to new replies.