WordPress.org

Ready to get started?Download WordPress

Forums

Upgraded to 3.2, now "No Input File Specified" for entire site (11 posts)

  1. amchambers
    Member
    Posted 3 years ago #

    Hi,

    I just upgraded to 3.2 and now only my home page works, when I click on everything else I get an error message saying "No Input File Specified."

    Also, when I'm in my Posts admin page, I can click on Edit and see my post. I can update them. But when I click on View, I get the same "No Input File Specified" error message.

    Help please, this is an ecommerce site, so I'm basically shut down from a business point of view.

    I've already deleted every plugin that I'm not using and isn't absolutely necessary. (yes, I deactived AND deleted the files thinking there may be a conflict with the new upgrade).

    Site is: http://www.MailMeACake.com

    Help please?

    Thanks so much in advance!
    anita

  2. Try resaving permalinks.

  3. amchambers
    Member
    Posted 3 years ago #

    Thanks lpstenu, I just rried after reading your message, but no luck. I still get the "No Input File Specified" message.

    Any other ideas?

  4. What's in your .htaccess?

  5. amchambers
    Member
    Posted 3 years ago #

    Strangely, I have 2 now, one entitled .htaccess and a second one entitled .htaccess 2.

    The .htaccess file includes:

    close edit hex TEXT viewer: /mailmeacake.com/.htaccess

    # BEGIN WordPress

    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]

    # END WordPress

    The .htaccess 2 file includes:

    # BEGIN WordPress

    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]

    # END WordPress

    Ideas?

  6. amchambers
    Member
    Posted 3 years ago #

    Oops, the .htaccess file begins with:

    # BEGIN WordPress

    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]

    # END WordPress

    Sorry, I accidentally copied the viewer info.

  7. The second one is just an old one :) S'okay to have a backup.

    We only care about the one JUST named .htaccess which ... looks just fine.

    Okay, try this:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress
  8. amchambers
    Member
    Posted 3 years ago #

    OK, tried that, but still doesn't work

  9. This isn't a 3.2 issue FWIW (search shows it's been around for a while), but I can't fathom what's gone wrong :(

  10. amchambers
    Member
    Posted 3 years ago #

    Strange, the only thing that I changed is doing the 3.2 upgrade, nothing else is new. Hmmmmm

  11. Are you on a Windows server?

Topic Closed

This topic has been closed to new replies.

About this Topic