Maybe my readers can help me out…

I posted this over on the WP-Hackers list, but maybe I can get some help from my own readers… (Thanks btw It’s nice to see that, after only three short months, I already have a number of regular readers. I hope my posts have helped!)

I think you all would be the ones to answer this, even if I posted it there.
Besides, perhaps there is something /deep/ in the WP code that is
specifically blocking this action… Though I don’t see how it would even
get into WP’s realm of influence (this should be all Apache), /something/ is
happening. I’ve provided screen shots as proof of my statements.

My problem centers around a file in my themes directory:
I’ve gotten some 249 404s for that file this month. I have an additional 14
for single_content.php which is called by the MORE function… I’ve removed
most of my MORE references. That’s why that count is so low…

The file clearly exists:

but when I connect to it from the browser, I get a 404…

I have one .htaccess file in that entire directory branch. It is located in
my root WP directory and currently contains:

IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*

# Showing off
Redirect /csrf.txt

# A couple redirects I want to keep from when I’ve tried different permalink

“Copy as Text Link” and “Copy as Image Link” Blogging Tools

Redirect /Article68
Redirect /2006/05/28/lg-vx5200-lg-vx6000-lg-vx7000-lg-vx8100-stuff/

# BEGIN WordPress

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

# END WordPress

The behavior is identical, whether .htaccess contains the above, or if I
blank it out and have nothing in .htaccess.

The rights on the directory structure and the file itself are 755:

I have all of my capitalization correct…


Please tell me it is something simple so I can smack myself on the head and
put this to rest!


Add a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.