[wp-hackers] Help needed with two issues on established WP install

Vogel, Andrew (vogelap) VOGELAP at UCMAIL.UC.EDU
Tue Aug 29 19:12:53 GMT 2006


Please don't take my lack of posting as anything other than my schedule
has gotten very full in the last several days!

I still intend to follow the instructions we generated (from ALL these
posts!) to the letter to see if it fixes this issue.

The guidance is appreciated, and I will test these things out as my
schedule permits.

-andrew vogel
Manager of Professional Programs
University of Cincinnati
College of Pharmacy 
 

> -----Original Message-----
> From: wp-hackers-bounces at lists.automattic.com 
> [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of 
> Jamie Holly
> Sent: Friday, August 25, 2006 11:20 AM
> To: wp-hackers at lists.automattic.com
> Subject: RE: [wp-hackers] Help needed with two issues on 
> established WP install
> 
> I don't know what else to look for. You either got a server 
> problem going on or a problem being caused by a plugin or a 
> bad wordpress install. Since you got a white screen with that 
> plugin I wrote, I would almost have to say it is something 
> server related. I just tried that plugin code on my clean 
> install of wp2.0.4 and it dumped the array out on the 
> permalinks page. 
> 
> Your htaccess is fine, as evident from the rewrite log dumps. 
> Since your having to dump the database and restore it to get 
> the site working again, I am still going with the suspicion 
> that you have some kind of query caching going on in MySql 
> that is messing with everything.
> 
> The simplest route to troubleshoot it from here is to 
> deactivate all plugins. Set your permalink structure and see 
> if it works. If it doesn't then go through your server files 
> and disable all caching (opcode, apache
> 2.2 caching and mysql caching), then see if it is working 
> again. Once you get it to the point that it is working, 
> reactivate every thing one by one, starting with the server 
> changes first then going to the plugins and testing it 
> between each step to find out what is causing the problem.
> 
> It is obvious the problem isn't in the Wordpress core, 
> considering the number of sites running 2.0.4. (I personally 
> handle 11 WP sites running
> 2.0.4 with now problems on all kinds of different 
> servers/configurations).
> If it were in Wordpress then we would have seen a rush of 
> tickets put in on it LOL. 
> 
> Jamie Holly
> http://www.intoxination.net
> 
> -----Original Message-----
> From: wp-hackers-bounces at lists.automattic.com
> [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of 
> Vogel, Andrew
> (vogelap)
> Sent: Friday, August 25, 2006 10:55 AM
> To: wp-hackers at lists.automattic.com
> Subject: RE: [wp-hackers] Help needed with two issues on 
> established WP install
> 
> Here's the .htaccess I'm using:
> 
> # BEGIN Url Rewrite section
> # (Automatically generated.  Do not edit this section) 
> <IfModule mod_rewrite.c>
>     RewriteEngine On
> 
>     RewriteBase /
> 
>     RewriteCond %{REQUEST_FILENAME} -f [OR]
>     RewriteCond %{REQUEST_FILENAME} -d [OR]
>     RewriteCond %{REQUEST_FILENAME} gallery\_remote2\.php
>     RewriteCond %{REQUEST_FILENAME} !/wp-gallery2\.php$
>     RewriteRule .   -   [L]
> 
> 
>     RewriteCond %{THE_REQUEST} \ /d/([0-9]+)-([0-9]+)/([^\/\?]+)(\?.|\
> .)
>     RewriteCond %{REQUEST_FILENAME} !/wp-gallery2\.php$
>     RewriteRule .
> /gallery2/main.php?g2_view=core.DownloadItem&g2_itemId=%1&g2_s
erialNumbe
> r=%2&g2_fileName=%3   [QSA,L]
> 
>     RewriteCond %{THE_REQUEST} \ /f/([^?]+)(\?.|\ .)
>     RewriteCond %{REQUEST_FILENAME} !/wp-gallery2\.php$
>     RewriteRule .
> /wp-gallery2.php?g2_controller=permalinks.Redirect&g2_filename=%1
> [QSA,L]
> 
>     RewriteCond %{THE_REQUEST} \ /v/([^?]+)(\?.|\ .)
>     RewriteCond %{REQUEST_FILENAME} !/wp-gallery2\.php$
>     RewriteRule .   /wp-gallery2.php?g2_view=core.ShowItem&g2_path=%1
> [QSA,L]
> 
> </IfModule>
> 
> # END Url Rewrite section
> 
> # BEGIN worst-offenders
> Deny from 194.165.130.93
> Deny from 193.93.237.16
> <additional entries removed for space>
> Deny from 193.93.237.20
> # END worst-offenders
> 
> # BEGIN WordPress
> <IfModule mod_rewrite.c>
> RewriteEngine On
> RewriteBase /
> RewriteCond %{REQUEST_FILENAME} !-f
> RewriteCond %{REQUEST_FILENAME} !-d
> RewriteRule . /index.php
> </IfModule>
> 
> # END WordPress
> 
> -andrew vogel
> Manager of Professional Programs
> University of Cincinnati
> College of Pharmacy 
>  
> 
> > -----Original Message-----
> > From: wp-hackers-bounces at lists.automattic.com
> > [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf 
> Of Vogel, 
> > Andrew (vogelap)
> > Sent: Friday, August 25, 2006 10:54 AM
> > To: wp-hackers at lists.automattic.com
> > Subject: RE: [wp-hackers] Help needed with two issues on 
> established 
> > WP install
> > 
> > I made the change to httpd.conf and did "service httpd 
> restart". The 
> > site worked normally, so I went to 
> > www.drewvogel.com/wp-admin/options.php and edited the 
> > "permalink_structure" field to remove "/index.php", clicked "Update 
> > Structure" to save changes. Just for grins, I did another "service 
> > httpd restart". Visiting the site, I got a non-WP 404. I went to
> > Options->Permalink and clicked "Update Permalink Structure" with the
> > same result -- a broken site with non-WP 404.
> > 
> > I went BACK to www.drewvogel.com/wp-admin/options.php and added 
> > "/index.php" to the permalink_structure field and saved 
> changes. The 
> > site was still broken and I had to empty and restore the 
> database to 
> > get it working again.
> > 
> > I tried your plugin, but after activating it, the screen went white 
> > and the only way to get it back was to delete the plugin. Perhaps 
> > something is wrong in there?
> > 
> > -andrew vogel
> > Manager of Professional Programs
> > University of Cincinnati
> > College of Pharmacy
> >  
> > 
> > > -----Original Message-----
> > > From: wp-hackers-bounces at lists.automattic.com
> > > [mailto:wp-hackers-bounces at lists.automattic.com] On 
> Behalf Of Jamie 
> > > Holly
> > > Sent: Friday, August 25, 2006 9:04 AM
> > > To: wp-hackers at lists.automattic.com
> > > Subject: RE: [wp-hackers] Help needed with two issues on
> > established
> > > WP install
> > > 
> > > Change this:
> > > 
> > > DocumentRoot "/var/www/html"
> > > # First, we configure the "default" to be a very
> > restrictive set of #
> > > features.
> > > #
> > > <Directory />
> > >     Options FollowSymLinks
> > >     AllowOverride None
> > > </Directory>
> > > 
> > > To this:
> > > 
> > > DocumentRoot "/var/www/html"
> > > # First, we configure the "default" to be a very
> > restrictive set of #
> > > features.
> > > #
> > > <Directory />
> > >     Options FollowSymLinks
> > >     AllowOverride All
> > > </Directory>
> > > 
> > > That tells apache to process the .htaccess file. I don't 
> know if it 
> > > will make any difference. Your .htaccess file is being
> > processed, as
> > > evident by the output logs. It could be that the file was being 
> > > processed, but Apache wasn't actually reading the output since 
> > > overrides was denied.
> > > 
> > > I noticed you have it further down in the config file, 
> but it could 
> > > actually be that having it in there twice is screwing with apache.
> > > 
> > > Another quick test you can do is make a short and easy 
> plugin that 
> > > dumps the rewrite array. Just make a quick text/php file
> > with this in
> > > it:
> > > 
> > > <?php
> > > /*
> > > Plugin Name: Dump Permalink Structure Plugin URI:
> > > Version: 
> > > Description: 
> > > Author:
> > > Author URI:  
> > > */
> > > 
> > > add_filter("rewrite_rules_array", keywords_createRewriteRules,10);
> > > 
> > > function keywords_createRewriteRules($rewrite) {
> > > 
> > > 	echo "<pre>";
> > > 	print_r($rewrite);
> > > 	echo "</pre>";
> > > 	return $rewrite
> > > }
> > > ?>
> > > 
> > > Then upload it to your plugins and activate it. It will dump the 
> > > rewrite array on the top of every page, so you don't want
> > to keep it
> > > activated long.
> > > Try getting rid of the /index.php/ in your rewrite rules
> > then reload
> > > the page and make sure that the /index.php/ is gone from
> > the beginning
> > > of the rewrites. If it isn't then you got a query cache that is 
> > > throwing the monkey wrench in everything.
> > > 
> > > 
> > > Jamie Holly
> > > http://www.intoxination.net
> > > 
> > > -----Original Message-----
> > > From: wp-hackers-bounces at lists.automattic.com
> > > [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf
> > Of Vogel,
> > > Andrew
> > > (vogelap)
> > > Sent: Friday, August 25, 2006 8:56 AM
> > > To: wp-hackers at lists.automattic.com
> > > Subject: RE: [wp-hackers] Help needed with two issues on
> > established
> > > WP install
> > > 
> > > Thanks for your attention and energy on this problem.
> > > 
> > > So, it seems that permalinks are actually working (even 
> though they
> > > don't) -- so that's not the problem.
> > > 
> > > I wonder if it might be something in my httpd.conf... 
> > Here's the lines
> > > I think may be relevant... Can you take a look at them to
> > verify that
> > > I've got things correctly configured? Thanks!
> > > 
> > > DocumentRoot "/var/www/html"
> > > # First, we configure the "default" to be a very
> > restrictive set of #
> > > features.
> > > #
> > > <Directory />
> > >     Options FollowSymLinks
> > >     AllowOverride None
> > > </Directory>
> > > 
> > > # Note that from this point forward you must specifically ALLOW # 
> > > particular features to be enabled - so if something's not
> > working as #
> > > you might expect, make sure that you have specifically 
> enabled it # 
> > > below.
> > > #
> > > <Directory "/var/www/html/cgi-bin">
> > >         Options ExecCGI Includes
> > >         AddHandler cgi-script .cgi .pl
> > >         AllowOverride None
> > > </Directory>
> > > 
> > > <Directory "/var/www/html/gallery2">
> > >         AllowOverride Options FileInfo </Directory>
> > > 
> > > # This should be changed to whatever you set DocumentRoot to.
> > > #
> > > <Directory "/var/www/html">
> > > # Possible values for the Options directive are "None", 
> "All", # or 
> > > any combination of:
> > > #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI
> > > Multiviews
> > > #
> > > # Note that "MultiViews" must be named *explicitly* ---
> > "Options All"
> > > # doesn't give it to you.
> > > #
> > > # The Options directive is both complicated and important.  
> > > Please see # 
> http://httpd.apache.org/docs-2.0/mod/core.html#options
> > > # for more information.
> > > #
> > >     Options Indexes FollowSymLinks Includes ExecCGI
> > > 
> > > # AllowOverride controls what directives may be placed in 
> .htaccess 
> > > files.
> > > # It can be "All", "None", or any combination of the keywords:
> > > #   Options FileInfo AuthConfig Limit
> > > #
> > >     AllowOverride All
> > >     AcceptPathInfo On
> > > 
> > > # Controls who can get stuff from this server.
> > > #
> > >     Order allow,deny
> > >     Allow from all
> > > </Directory>
> > > 
> > > #
> > > # Disable autoindex for the root directory, and present a 
> # default 
> > > Welcome page if no other index page is present.
> > > #
> > > <LocationMatch "^/$>
> > >     Options -Indexes
> > >     ErrorDocument 403 /error/noindex.html </LocationMatch>
> > > 
> > > -andrew vogel
> > > Manager of Professional Programs
> > > University of Cincinnati
> > > College of Pharmacy
> > >  
> > > 
> > > > -----Original Message-----
> > > > From: wp-hackers-bounces at lists.automattic.com
> > > > [mailto:wp-hackers-bounces at lists.automattic.com] On
> > Behalf Of Jamie
> > > > Holly
> > > > Sent: Thursday, August 24, 2006 3:43 PM
> > > > To: wp-hackers at lists.automattic.com
> > > > Subject: RE: [wp-hackers] Help needed with two issues on
> > > established
> > > > WP install
> > > > 
> > > > Everything looks good in the logs. They are both passing to
> > > /index.php
> > > > and nothing is stopping in the way.
> > > > 
> > > > ************************
> > > > BROKEN
> > > > ************************
> > > > (2) init rewrite engine with requested uri 
> /2006/05/01/quicklinks/
> > > > (3) applying pattern '.*' to uri '/2006/05/01/quicklinks/'
> > > > (4) RewriteCond: input='GET' pattern='^TRACE' => not-matched
> > > > (1) pass through /2006/05/01/quicklinks/
> > > > (3) [perdir /var/www/html/] add path info postfix: 
> > > > /var/www/html/2006 -> /var/www/html/2006/05/01/quicklinks/
> > > > (3) [perdir /var/www/html/] strip per-dir prefix:
> > > > /var/www/html/2006/05/01/quicklinks/ -> 2006/05/01/quicklinks/
> > > > (3) [perdir /var/www/html/] applying pattern '.' to uri 
> > > > '2006/05/01/quicklinks/'
> > > > (4) [perdir /var/www/html/] RewriteCond: 
> > input='/var/www/html/2006'
> > > > pattern='-f' => not-matched
> > > > (4) [perdir /var/www/html/] RewriteCond: 
> > input='/var/www/html/2006'
> > > > pattern='-d' => not-matched
> > > > (4) [perdir /var/www/html/] RewriteCond: 
> > input='/var/www/html/2006'
> > > > pattern='gallery\_remote2\.php' => not-matched
> > > > (3) [perdir /var/www/html/] add path info postfix: 
> > > > /var/www/html/2006 -> /var/www/html/2006/05/01/quicklinks/
> > > > (3) [perdir /var/www/html/] strip per-dir prefix:
> > > > /var/www/html/2006/05/01/quicklinks/ -> 2006/05/01/quicklinks/
> > > > (3) [perdir /var/www/html/] applying pattern '.' to uri 
> > > > '2006/05/01/quicklinks/'
> > > > (4) [perdir /var/www/html/] RewriteCond: input='GET 
> > > > /2006/05/01/quicklinks/ HTTP/1.1' pattern='\
> > > /d/([0-9]+)-([0-9]+)/([^\/\?]+)(\?.|\ .)' => not-matched
> > > > (3) [perdir /var/www/html/] add path info postfix: 
> > > > /var/www/html/2006 -> /var/www/html/2006/05/01/quicklinks/
> > > > (3) [perdir /var/www/html/] strip per-dir prefix:
> > > > /var/www/html/2006/05/01/quicklinks/ -> 2006/05/01/quicklinks/
> > > > (3) [perdir /var/www/html/] applying pattern '.' to uri 
> > > > '2006/05/01/quicklinks/'
> > > > (4) [perdir /var/www/html/] RewriteCond: input='GET 
> > > > /2006/05/01/quicklinks/ HTTP/1.1' pattern='\ /f/([^?]+)(\?.|\
> > > .)' => not-matched
> > > > (3) [perdir /var/www/html/] add path info postfix: 
> > > > /var/www/html/2006 -> /var/www/html/2006/05/01/quicklinks/
> > > > (3) [perdir /var/www/html/] strip per-dir prefix:
> > > > /var/www/html/2006/05/01/quicklinks/ -> 2006/05/01/quicklinks/
> > > > (3) [perdir /var/www/html/] applying pattern '.' to uri 
> > > > '2006/05/01/quicklinks/'
> > > > (4) [perdir /var/www/html/] RewriteCond: input='GET 
> > > > /2006/05/01/quicklinks/ HTTP/1.1' pattern='\ /v/([^?]+)(\?.|\
> > > .)' => not-matched
> > > > (3) [perdir /var/www/html/] add path info postfix: 
> > > > /var/www/html/2006 -> /var/www/html/2006/05/01/quicklinks/
> > > > (3) [perdir /var/www/html/] strip per-dir prefix:
> > > > /var/www/html/2006/05/01/quicklinks/ -> 2006/05/01/quicklinks/
> > > > (3) [perdir /var/www/html/] applying pattern '.' to uri 
> > > > '2006/05/01/quicklinks/'
> > > > (4) [perdir /var/www/html/] RewriteCond: 
> > input='/var/www/html/2006'
> > > > pattern='!-f' => matched
> > > > (4) [perdir /var/www/html/] RewriteCond: 
> > input='/var/www/html/2006'
> > > > pattern='!-d' => matched
> > > > (2) [perdir /var/www/html/] rewrite '2006/05/01/quicklinks/' 
> > > -> '/index.php'
> > > > (2) [perdir /var/www/html/] trying to replace prefix
> > /var/www/html/
> > > > with /
> > > > (1) [perdir /var/www/html/] internal redirect with /index.php 
> > > > [INTERNAL REDIRECT]
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > *******************
> > > > working
> > > > ******************
> > > > (2) init rewrite engine with requested uri 
> > > > /2005/06/02/funny-sign-in-new-york/
> > > > (3) applying pattern '.*' to uri
> > > '/2005/06/02/funny-sign-in-new-york/'
> > > > (4) RewriteCond: input='GET' pattern='^TRACE' => not-matched
> > > > (1) pass through /2005/06/02/funny-sign-in-new-york/
> > > > (3) [perdir /var/www/html/] add path info postfix: 
> > > > /var/www/html/2005 ->
> > > /var/www/html/2005/06/02/funny-sign-in-new-york/
> > > > (3) [perdir /var/www/html/] strip per-dir prefix:
> > > > /var/www/html/2005/06/02/funny-sign-in-new-york/ -> 
> > > > 2005/06/02/funny-sign-in-new-york/
> > > > (3) [perdir /var/www/html/] applying pattern '.' to uri 
> > > > '2005/06/02/funny-sign-in-new-york/'
> > > > (4) [perdir /var/www/html/] RewriteCond: 
> > input='/var/www/html/2005'
> > > > pattern='-f' => not-matched
> > > > (4) [perdir /var/www/html/] RewriteCond: 
> > input='/var/www/html/2005'
> > > > pattern='-d' => not-matched
> > > > (4) [perdir /var/www/html/] RewriteCond: 
> > input='/var/www/html/2005'
> > > > pattern='gallery\_remote2\.php' => not-matched
> > > > (3) [perdir /var/www/html/] add path info postfix: 
> > > > /var/www/html/2005 ->
> > > /var/www/html/2005/06/02/funny-sign-in-new-york/
> > > > (3) [perdir /var/www/html/] strip per-dir prefix:
> > > > /var/www/html/2005/06/02/funny-sign-in-new-york/ -> 
> > > > 2005/06/02/funny-sign-in-new-york/
> > > > (3) [perdir /var/www/html/] applying pattern '.' to uri 
> > > > '2005/06/02/funny-sign-in-new-york/'
> > > > (4) [perdir /var/www/html/] RewriteCond: input='GET 
> > > > /index.php/2005/06/02/funny-sign-in-new-york/ HTTP/1.1'
> > > > pattern='\ /d/([0-9]+)-([0-9]+)/([^\/\?]+)(\?.|\ .)' =>
> > not-matched
> > > > (3) [perdir /var/www/html/] add path info postfix: 
> > > > /var/www/html/2005 ->
> > > /var/www/html/2005/06/02/funny-sign-in-new-york/
> > > > (3) [perdir /var/www/html/] strip per-dir prefix:
> > > > /var/www/html/2005/06/02/funny-sign-in-new-york/ -> 
> > > > 2005/06/02/funny-sign-in-new-york/
> > > > (3) [perdir /var/www/html/] applying pattern '.' to uri 
> > > > '2005/06/02/funny-sign-in-new-york/'
> > > > (4) [perdir /var/www/html/] RewriteCond: input='GET 
> > > > /index.php/2005/06/02/funny-sign-in-new-york/ HTTP/1.1'
> > > > pattern='\ /f/([^?]+)(\?.|\ .)' => not-matched
> > > > (3) [perdir /var/www/html/] add path info postfix: 
> > > > /var/www/html/2005 ->
> > > /var/www/html/2005/06/02/funny-sign-in-new-york/
> > > > (3) [perdir /var/www/html/] strip per-dir prefix:
> > > > /var/www/html/2005/06/02/funny-sign-in-new-york/ -> 
> > > > 2005/06/02/funny-sign-in-new-york/
> > > > (3) [perdir /var/www/html/] applying pattern '.' to uri 
> > > > '2005/06/02/funny-sign-in-new-york/'
> > > > (4) [perdir /var/www/html/] RewriteCond: input='GET 
> > > > /index.php/2005/06/02/funny-sign-in-new-york/ HTTP/1.1'
> > > > pattern='\ /v/([^?]+)(\?.|\ .)' => not-matched
> > > > (3) [perdir /var/www/html/] add path info postfix: 
> > > > /var/www/html/2005 ->
> > > /var/www/html/2005/06/02/funny-sign-in-new-york/
> > > > (3) [perdir /var/www/html/] strip per-dir prefix:
> > > > /var/www/html/2005/06/02/funny-sign-in-new-york/ -> 
> > > > 2005/06/02/funny-sign-in-new-york/
> > > > (3) [perdir /var/www/html/] applying pattern '.' to uri 
> > > > '2005/06/02/funny-sign-in-new-york/'
> > > > (4) [perdir /var/www/html/] RewriteCond: 
> > input='/var/www/html/2005'
> > > > pattern='!-f' => matched
> > > > (4) [perdir /var/www/html/] RewriteCond: 
> > input='/var/www/html/2005'
> > > > pattern='!-d' => matched
> > > > (2) [perdir /var/www/html/] rewrite 
> > > > '2005/06/02/funny-sign-in-new-york/' -> '/index.php'
> > > > (2) [perdir /var/www/html/] trying to replace prefix
> > /var/www/html/
> > > > with /
> > > > (1) [perdir /var/www/html/] internal redirect with /index.php 
> > > > [INTERNAL REDIRECT]
> > > > 
> > > > 
> > > > Just out of curiosity - do you have some sort of query
> > > cache running
> > > > on your site? Perhaps that is causing the problem.
> > > > 
> > > > Also do you have any directories within your root directory
> > > that could
> > > > be causing a problem (ie. /2006/ or /2005/). Since you
> > > sometimes get a
> > > > standard
> > > > 404 and other times get a wp-404, it is almost acting 
> like it is 
> > > > finding a directory and looking inside of there.
> > > > 
> > > > I would start by disabling any caching you might have
> > (query, apc,
> > > > wp-cache,
> > > > etc.) and see if the problem persists. This is about all I
> > > can think
> > > > of at this point.
> > > > 
> > > > Jamie Holly
> > > > http://www.intoxination.net
> > > > 
> > > > -----Original Message-----
> > > > From: wp-hackers-bounces at lists.automattic.com
> > > > [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf
> > > Of Vogel,
> > > > Andrew
> > > > (vogelap)
> > > > Sent: Thursday, August 24, 2006 3:18 PM
> > > > To: wp-hackers at lists.automattic.com
> > > > Subject: RE: [wp-hackers] Help needed with two issues on
> > > established
> > > > WP install
> > > > 
> > > > It should be noted, however, that simply visiting the
> > > > Options->Permalink page still breaks the site.
> > > > 
> > > > -andrew vogel
> > > > Manager of Professional Programs
> > > > University of Cincinnati
> > > > College of Pharmacy
> > > >  
> > > > 
> > > > > -----Original Message-----
> > > > > From: wp-hackers-bounces at lists.automattic.com
> > > > > [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf
> > > > Of Vogel,
> > > > > Andrew (vogelap)
> > > > > Sent: Thursday, August 24, 2006 2:25 PM
> > > > > To: wp-hackers at lists.automattic.com
> > > > > Subject: RE: [wp-hackers] Help needed with two issues on
> > > > established
> > > > > WP install
> > > > > 
> > > > > Thanks for helping out so far, Jamie. I really do
> > appreciate your
> > > > > assistance!
> > > > > 
> > > > > I apologize for my ignorance, but I'm not sure what I'm
> > > > looking for in
> > > > > the rewrite log file, so I've posted the whole thing from
> > > both the
> > > > > working site (56K) and non-working (84K) configurations.
> > > > > 
> > > > > Here's what I did...
> > > > > 
> > > > > * I enabled the rewrite log on my functioning site and
> > > visited the
> > > > > main page and one article. The results of that test are here:
> > > > > http://www.drewvogel.com/apache_rewrite_working.txt
> > > > > 
> > > > > Then, I...
> > > > > * Went to http://www.drewvogel.com/wp-admin/options.php
> > > and removed
> > > > > the "/index.php" from the permalink_structure line and
> > click the
> > > > > "Update Settings" button.
> > > > > 
> > > > > * "service httpd restart" to restart Apache.
> > > > > 
> > > > > * I visited the main page and one article. The results of
> > > that test
> > > > > are
> > > > > here: http://www.drewvogel.com/apache_rewrite_broken.txt. I
> > > > received a
> > > > > non-WP 404 when attempting to view the article.
> > > > > 
> > > > > On (an exciting) side note, I went back to 
> > > > > http://www.drewvogel.com/wp-admin/options.php, re-added the 
> > > > > "/index.php"
> > > > > to the permalink_structure field, clicked "Update
> > > > Settings", and did
> > > > > "service httpd restart" and my site worked again -- I
> > > > didn't need to
> > > > > roll it back from the database backup! That's progress,
> > I suppose!
> > > > > 
> > > > > Please let me know how to proceed from here.
> > > > > 
> > > > > -andrew vogel
> > > > > Manager of Professional Programs University of Cincinnati 
> > > > > College of Pharmacy
> > > > >  
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: wp-hackers-bounces at lists.automattic.com
> > > > > > [mailto:wp-hackers-bounces at lists.automattic.com] On
> > > > Behalf Of Jamie
> > > > > > Holly
> > > > > > Sent: Wednesday, August 23, 2006 4:35 PM
> > > > > > To: wp-hackers at lists.automattic.com
> > > > > > Subject: RE: [wp-hackers] Help needed with two issues on
> > > > > established
> > > > > > WP install
> > > > > > 
> > > > > > At this point, I would suggest enabling the mod_rewrite
> > > > log to make
> > > > > > certain that mod_rewrite is fully firing. For some reason
> > > > > it needs the
> > > > > > index.php instead of mod_rewrite automatically 
> appending the 
> > > > > > index.php.
> > > > > > 
> > > > > > Jamie Holly
> > > > > > http://www.intoxination.net
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > wp-hackers mailing list
> > > > > > wp-hackers at lists.automattic.com 
> > > > > > http://lists.automattic.com/mailman/listinfo/wp-hackers
> > > > > > 
> > > > > _______________________________________________
> > > > > wp-hackers mailing list
> > > > > wp-hackers at lists.automattic.com
> > > > > http://lists.automattic.com/mailman/listinfo/wp-hackers
> > > > > 
> > > > _______________________________________________
> > > > wp-hackers mailing list
> > > > wp-hackers at lists.automattic.com
> > > > http://lists.automattic.com/mailman/listinfo/wp-hackers
> > > > 
> > > > _______________________________________________
> > > > wp-hackers mailing list
> > > > wp-hackers at lists.automattic.com
> > > > http://lists.automattic.com/mailman/listinfo/wp-hackers
> > > > 
> > > _______________________________________________
> > > wp-hackers mailing list
> > > wp-hackers at lists.automattic.com
> > > http://lists.automattic.com/mailman/listinfo/wp-hackers
> > > 
> > > _______________________________________________
> > > wp-hackers mailing list
> > > wp-hackers at lists.automattic.com
> > > http://lists.automattic.com/mailman/listinfo/wp-hackers
> > > 
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> > 
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
> 
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
> 


More information about the wp-hackers mailing list