paul

balbert, i have been over all that. I wonder if the fact the Codex points to the Apache 1.3 manual and I have been using 2.x (2.2 now) for years has anything to do with it? I have AllowOverride All set on both sites I have been testing: no joy.

following this thread in hopes of an answer. I have the same problem, even on a test server running 2.5. No plugins, just an out of the box installation.

The results are the same with WP, versions 2.5 through 2.7, on Apache 2.2 and php5 with MySQL 5 on either FreeBSD or OS X.

Categories don’t work (they never have, for some reason).

I wish you and the rest of the moderators were as quick to figure out why permalinks are broken in 2.7 for quite a few of us: lots of posts and unresolved threads on that. I just set up a fresh install of 2.7 on a test server and out of the box, permalinks are not working.

After using W since 1.5, this is the first, perhaps only, upgrade that has been problematic and bland assurance like 2.7 is complete and works just fine with a fresh install make me wonder if someone making them is actually using it.

This also fails to work with wp 2.7 (all the way back to 2.5, in fact) with Apache 2.2 and FreeBSD 6 and OS X. It used to work. I have a couple of other glitches as well: the UI never shows the active theme and while I have a couple of Pages working, I can’t add anymore.

Not having the same success. I set up a testbed on a different system and have found the same problem in 2.6.1. I plan to work back until I find a version that works and see if it’s possible to figure out what it is.

You’d think this would be something that would have shown up in the release process.

Seconding the vote for jaxn as supreme oligarch.

Now maybe I can work out why permalinks have FAIL written all over them.

Not a useful answer. I have finally run out of patience with a lot of small issues with my WP install and hoped to export and re-import after verifying that things were fixed. The content is what it is but there are some config issues I can’t quite solve.

As for a database dump and restore, that’s great if you want to perpetuate the same issues.

I get so few comments [snif] I disabled this. It seems to add a lot of log lines and pages seem to load faster without it. I wish I needed it ??

I have mod_rewrite and I don’t use IIS.

This should work, but doesn’t for me. according to apache.org, I shouldn’t use .htaccess if I can edit httpd.conf (I can). But no matter what I do, I can’t get permalinks w/o index.php to work properly nor can I get category or tag-based archives to work. What ends up happening is, no matter what post is requested, the most recent one is displayed.

Any ideas?

I wasn’t having any luck with this, until I changed the permissions on the wordpress files to be owned by/writeable by the webserver. Then it’s all about the one-button upgrade.

Just to resolve this, the answer is here.

The synopsis: the rules are stored in the database, as the field “rewrite_rules” in the table wp_options. Simply cleaning out that field and forcing a rebuild through the usual steps was all it took.

That sounds like a misfeature to me: not everyone is going to be thrilled at the prospect of monkeying with their database directly.

If I am reading this right, I never did have “pretty printed” permalinks, but PATHINFO. I always had index.php in there.

So how do I get back to that?

mod_rewrite works. there is a valid .htaccess file.

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]
</IfModule>

What needs to happen to make these permalinks work again?

wordpress/index.php/archives/%year%/%month%/%day%/%postname%

If this isn’t handled in the .htaccess file it must live in the database. Else how would these setting survive a restart?

Well, then why does this page exist if .htaccess is static and all the magic happens internally?

I’m not saying it doesn’t happen that way: my old .htaccess contained nothing more that the mod_rewrite invocation. But it does seem confusing to have a lot of stuff on manually maintaining a file that never needs to be changed.

Hmm, it looks like no matter what I change in the UI, .htaccess never changes. My guess is that’s not the correct behavior.

Yes, I just made a lot of changes via the UI and the .htaccess file never changes (though mod times is updated). I can move it aside and have WP create a new one, same as the old.

is that a feature?