Intresting that I am having the same problem, but I know that I have mod_rewrite apache mod working.
It seems that it is a 2.0 problem, it only occured when I upgraded, when I was using 1.5 my .htaccess file was always 5 times as long, now I get the exact same .htaccess file output no matter what configuration I use. I am familiar with rewrite rules, the wordpress seems to not be generating the correct thing.
I have reinstalled my wordpress twice to make sure that everything is working correctly and to try and regenerate the ‘default’ htaccess file.
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php
</IfModule>
# END WordPress
now I get the exact same .htaccess file output no matter what configuration I use.
For WP 2.0, the .htaccess should look just like you’ve printed above: no more. That’s because WP 2.0 handles internally all those rewrite rules, which used to make 1.5’s .htaccess so long.
This thread is still open to discuss, and it is not resolved yet.
I installed the patches, redid the .htaccess and now while my page-level permalinks work my post-level permalinks still do NOT work. This problem did not begin until I CHMOD’d my .htaccess to 777 in order to allow WP to write it. Now, even though I set it back to 644 before deleting and re-uploading, the problem is STILL THERE. I should note that it is NOT my WP-generated 404 that is showing.
Example: http://cathcoll.net/contact works (this is a page). http://cathcoll.net/blog/2006/shout-out-for-suggestions/ (this is a post) does NOT work.
That page looks like a WP generated 404 page. In that case the Debug Env plugin will be helpful.
I notice that your page is in / while your post is /blog/. Typically both live in the same root. Debug Env will help me fix permalinks for your setup.
/blog is a virtual directory, the only thing on the site that’s not in root is the photo gallery. (cf. http://codex.wordpress.org/Pages#Making_your_blog_appear_in_a_non-root_folder)
I’ll send the information to you in a few minutes.
I get a similar problem, If I go to Options and select any setting for Permalinks other then the “Default”, the .HTACCESS file is written with the info above and I am prevented from accessing anything from the website, either surfing in to view the site or accessing the admin control panel. I have to delete the .HTACCESS file, then select the default settings for permalinks in the options panel and then I have full access to wordpress..
Rudeseal, does “prevented from accessing” mean you are getting 404s? Did permalinks work for you with 1.5.2? Can you give me Debug Env output?
Ryan: I get 403 (Forbidden) errors consistantly on all pages and I can duplicate it. I will install the Debug Env Plug in and get back to you.. The page is located on the Netfirms server.. and yes, permalinks worked in the earlier version.
Ryan, I am not getting any dumps for your Dump_ENV plugin, do I have to use a tag somewhere or does it automatically dump to my footer?
I am having the same problem… permalinks give a 404 error regardless of the permalink stucture I set up. I have tried the updated files that ryan posted, as well as the .htaccess tips in this thread.
If I use the default permalink stucture, I get the “404” section from within single.php (i.e. the Loop falls through to the error).
If I use a custom permalink such as /%postname%/ I get the 404 page that’s at the root of my theme.
The big clue that I have is that if I log in to wp-admin, the 404 errors go away! Right now I am logged in in Firefox, and the pages display fine, but in Safari, with my cookies cleared, the 404 errors appear.
i am aware that i have a strange hosting situation.
they won’t let me use a .htaccess file.
i can do some re-write rules via my hosting control center.
but in WP 1.52 none of the permalink re-writes would work.
so had to opt for the ole /index.php/%post_id%/%postname%/
in my test WP 2.0 install i tested permalinks and saw that now the simplest re-write rule works fine even on my server, the one only using /%postname%/
however after now upgrading to WP 2.0 i had to realise that my old structure, the one that always worked before, /index.php/%post_id%/%postname%/ is no longer working = 404 errors.
can this somehow be a cache issue? because i did notice that at one point i managed to get name date based to work [= /%year%/%monthnum%/%day%/%postname%/, ]and now that one won’t work any longer.
ironically the one that does work [/%postname%/ is also a bit problematic as indicated in the instructions on codex.
i also want to add that i have the /%post_id%/ in there that a few people have said is causing problems for them.
Your not the only person with this problem because I have the exact same issue!
I upgraded my from 1.5.2 and had the problems so I had to revert back to the old one. The patch also did not work for me.
I’ve been following the forums for a while now and there’s been no solution. I hope the developers know this is a problem and will address it with a patch.
I have upgraded to 2.0 and can’t get the permalinks working. They will work with /index.php/, but not without.
I get a wordpress (not server) 404 on the single entries, but the dev_dump plugin doesn’t add anything to the code of the 404 page.
do have I have to to anything other than to active the dev_dump plugin for it to work?
