Another fine WP/Apache post

DMZ · June 15, 2008 at 8:00 am · Filed Under Mariners 

Below the fold to avoid inducing insomnia in most of our readership

Here’s the current issue:
We can get Apache 2.2.x up and running with PHP 5.2.5. And it’ll render the front page fine, or another sample php page. But it won’t render a page, like

http://ussmariner.com/2008/06/14/game-68-nationals-at-mariners/

The error log fills up with lines like
[Sat Jun 14 23:10:28 2008] [error] [client 70.71.8.206] File does not exist: /usr/home/ussmariner/www/2008

So running ye olde info.php I can see that mod_rewrite shows as on. But other than that, this is a stock install — so if there’s any funky stuff I need in httpd.conf, it’s likely not there: I just turned on symlinks and the rewrite engine…

Which brings me to the questions at hand:
– Is this a config issue?
– What needs to be in httpd.conf to get this to work?
– What else needs to get setup to get this to work?

Tags:

Comments

5 Responses to “Another fine WP/Apache post”

  1. jro on June 15th, 2008 8:11 am

    Derek – check the config. Start with the rewrite rules. Looks like /2008/* is being mapped to /2008. Maybe there’s a conflict with another rule.

    I’m not familiar with the WP stock rewrite entries, but that’s where I’d start.

  2. befara on June 15th, 2008 9:40 am

    The rewrite rules are not running. As I recall wordpress generates the rewrite rules in an .htaccess file. First, make sure that .htaccess file exists and is being created (if not, it’s a permissions issue but I think wordpress would tell you this). Then, in your apache conf you should do one or both of the following.

    Include this line which tells apache to look for an .htaccess file in each directory:

    AccessFileName .htaccess

    or/and make sure that your directory where the .htaccess file resides is allowing ovverride by including something like this in the apache conf.

    AllowOverride All

  3. befara on June 15th, 2008 9:41 am

    Sorry, that last include is:

    AllowOverride All

  4. Stephen R on June 15th, 2008 9:44 am

    My first thought is that WordPress could not write to your .htaccess file. This is what should be in that file:

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

    (hope that formats right….)

  5. Stephen R on June 15th, 2008 9:45 am

    Okay, it basicalyl formatted right. Should be within <IfModule mod_rewrite.c> </IfModule>

Leave a Reply

You must be logged in to post a comment.