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:
WPPATH/wp-content/themes/WP-Binary-Blue-v110/single_comments.php
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…
http://www.thecodecave.com/wp-content/themes/WP-Binary-Blue-v110/single_comments.php
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 http://www.thecodecave.com/?p=105# A couple redirects I want to keep from when I’ve tried different permalink
formats
Redirect
/2006/05/26/copy-as-text-link-and-copy-as-image-link-blogging-tools/
Redirect /Article68 http://www.thecodecave.com/article68
Redirect /2006/05/28/lg-vx5200-lg-vx6000-lg-vx7000-lg-vx8100-stuff/
http://www.thecodecave.com/article113# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPressThe 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…
WHAT AM I MISSING?????
Please tell me it is something simple so I can smack myself on the head and
put this to rest!
WP-Contract-Form 0.3 released
EasyWPUpdate ver 2.0 RC 1 – Just in time for WordPress 2.0.7
Upgrade your sites to the latest WordPress in 35 seconds.
About Author
—–Original Message—–
From: wp-hackers-bounces On Behalf Of Sam Angove
Sent: Wednesday, June 07, 2006 10:15 AM
To: wp-hackers
Subject: Re: [wp-hackers] Funky Four-O-Four
On 6/7/06, Brian Layman wrote:
>
> Please tell me it is something simple so I can smack myself on the head and
> put this to rest!
The .htaccess is a red herring.
single_comments.php loads wp-blog-header.php, which in turn attempts
to find content matching the request parameters. It fails and returns
a 404. A WordPress 404 page isn\\\\\\\\\\\\\\\’t returned because WP_USE_THEMES isn\\\\\\\\\\\\\\\’t
defined.
Compare:
http://www.thecodecave.com/ … /single_comments.php?p=152
HTH. 🙂
Processing….
Soooo, my 249 related 404s are ones that, for some odd reason, don\’t have a
parameter specified? or have an invalid parameter specified?
Perhaps the theme can\’t handle my customized permalink structure? Hmmm…
If that\’s the problem, and I won\’t change my perma link structure again; I\’ll
have to fix the code… If that\’s the problem…
Processing….(thanks!)
(BTW: I chose to use the /article structure because having a seemed to be a good compromise.)
non-default permalink structure allows AWStats to track the hits to the
individual posts, and yet the SEO advantages of including the post name in
the link is probably outweighed by the fact that no one can easily copy and
paste your links in emails or posts – especially if you like long post
titles and I do. /article
UPDATE – Switching to BB 1.1.1 Fixed the 404 error that caused the comments not to expand in line…. The More switch is still broken. It works from work but not from home… I believe I do have a different Java Virtual Machine at home… That could have something to do with it…
Note that adding the USE_WP_THEMES define at the the beginning of the comments file simply made the whole WP 404 comments page come up again inline… That was NOT an improvement…
I just need to track down the difference between 1.1.0 and 1.1.1 in this area and apply it to the Single_Content file. But right now, I’m not yet seeing the difference…