gpaciga

Thanks for finding that. I applied the patch given there to fix the problem (basically just correcting what looks like a typo in query.php).

Setting a “Posts page” brought up other problems, though, so I’m leaving it unset. I’m not sure what what it’s supposed to do. I have blank page with a special template to display my posts (at /blog/) and interestingly—I just noticed this a couple hours ago—the 404 page did come up properly when requesting a page like /blog/thisisnotapage.

Anyway, this seems to be resolved. Thanks again for your help.

My custom plugins were the first suspect, and the first to go. It still happens with them deactivated. They can’t do anything while deactivated can they?

I checked all the WordPress files and they have not been changed at all from those distributed with 2.5.1. To be sure I deleted and uploaded them again. That didn’t work.

So I dumped my whole database, installed WordPress again. Then when requesting a page that doesn’t exist, I was just shown the homepage again, both with the default theme and my custom theme. While this isn’t the same behaviour, it still wasn’t a 404 error page. From what I remember reading if a theme doesn’t have a 404.php then it just goes back to the homepage, but both these these *do* have a 404.php, so something still seems wrong.

From what I can tell it’s not plugins, it’s not the theme, it’s not the core files, and it’s not the database. I’ll contact my host and see if they changed anything on the server. What else could it be at this point?

1. I’m not sure about the hierarchy… but I made the theme just by copying the default one and tweaking it to suit my needs. The 404 page worked fine with the changes I made, and the only thing I changed since then is adding some page templates (by the names gallery.php and nosidebar.php).

2. It still happens with all plugins deactivated.

3. I have no sidebar widgets.

4. Default theme has the same problem.

I also saved the queries, with default theme and no plugins, and put them here: https://www.booberfish.com/queries-default.txt (the pastebin site refuses to load right now…). I noticed there was nothing about a 404 permalink like in your example, but I do have two requests that seem to reference all my pages: wp_get_obect_terms and update_postmeta_cache. There’s also one from get_pages that is asking for all published pages. How can I find where that is being called?

I have 69 static pages, a few of which are quite long by themselves. It is only pages that show up, not posts. The front page at booberfish.com is a static page and posts are shown with a special template page, but that was set up and working fine long before this happened.

My theme does have a 404.php but I hadn’t changed it, and removing it didn’t help. I suspect it is some ill-formed query at work… I dug around for something along those lines, but nothing turned up. It’s not the .htaccess file, the plugins, or the theme.

I tried using wget to request a page that doesn’t exist. It reported a 301 Moved Permanently, then requested the same address with a slash on the end , which returns 200 OK. If I request something with a slash on the end it just says 200 OK.

Exactly my point, rawalex. I know I can edit the permalink once it’s made, but when changing the title I have to make the same edit twice. You could change the permalink at any time during editing the old way, too, by setting the post slug.

Thanks, moshu. Information is much easier to come by when you know the terminology.

Well, there’s a grammatical difference between the two, so I’m not willing to fudge my punctuation to work around a bug.

I’d be happy having double quotations neutral, like in the font used here, so that there is no left or right quotes. However, in order to just change the font, I’d have to have the quotes appearing in the correct font in the first place. I’d still like some help with that.

The import is still *very* buggy… it freezes at different points, sometimes skips every entry, and is generally unrealiable all over.

Well, it didn’t work the first time, but switching to publish on BlogSpot and then publishing worked this last time. It froze halfway through so I didn’t get all my entries, but at least it’s working. One or two more runs and I should be able to get everything.

Fantastic! You’re right, that’s exactly what was happening. Even though it occured to me that my .html to .php rewrite rule might get applied first, I didn’t think that subsequent rules could also get applied… seems obvious in retrospect. Thanks.

My full htaccess file is:


# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule ^/wordpress/([0-9]{4})/([0-9]{1,2})/([^/]+).html$ /wordpress/$1/$2/$3/ [QSA,R]
RewriteBase /wordpress/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]
</IfModule>

# END WordPress

Everything except line 4 was put there by WordPress. I have tried my rule (line 4) with and without the /wordpress/ explicitly, and before the #BEGIN line (with its own RewriteEngine On). As I understand it RewriteRule . /wordpress/index.php is a catch-all, so I should at least have my rule before that.

I have in my root directory an htaccess with the rule

RewriteRule ^([^/.]+).html$ $1.php [L]

It has been my experience, however, that this does not affect any subdirectories (possibly because of the [^/] but I’m not sure), so it shouldn’t be conflicting with the WordPress rules. However, just to be safe, I did alter my rule to .php in case my requests for the .html were getting written to .php before going through the WordPress rules. This did not seem to be the case.

Can anyone see where I’m going wrong?

Well, getting the wordpress 404 at least means that it’s not rewriting to /2005/10/something… although you’re right that I’d still get the error if it wasn’t rewriting at all.

Yes, I did add the $4 when using (.*), and I also tried writing out “wordpress” at the beginning as you suggested. It still does not work.

I’m just testing it now in the wordpress directory until I move it.

I did try to take into account the fact that I have it installed in a subdirectory in a few ways without any effect. I have

RewriteBase /wordpress/

I also tried adding the subdirectory explicitly in the regular expression, as well as starting it with ^(.*)/. Maybe I’m just not using them correctly, but it’s not working.

At least I know that even though the rewrite goes to $1/$2/$3 without /wordpress/ explicitly, it’s still within the /wordpress/ directory since I get the wordpress 404 error and not the one for my site.

To which .htaccess file? One in your wordpress directory? That seemst to do nothing but cause a whole lot of Error 500’s for me.

Hmmm… I tried switching to blogspot too, but I still got the same errors.