As Meesha said, there is something conflicting. The code that’s in your .htaccess file is correct and should result in working permalinks.
Is that the only code in your .htaccess file or is there something else in it?
Can’t speak for smrtalex, but there’s nothing else in my .htaccess file, aside from the code quoted above.
Although I did try adding
Options +FollowSymLinks
to no avail.
Just to be clear, the 404 is within WP, not coming from Apache, and post links work again when switched back to default.
Thanks for all your help, everyone.
As with antiresearch, that is the only code in the .htaccess file. I have even cleaned it of any whitespace. And also just to be clear, like antiresearch, the 404 is within WP, not coming from Apache, and post links work again when switched back to default.
Same problem is here. A new clean installation. No .htaccess. No plugins. Getting 404 every time when go away from default links.
If it of any help, I checked error_log file in the root directory. It has a record repeated many times:
——————–
[22-Dec-2008 15:18:51] PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/extensions/no-debug-non-zts-20060613/pdo.so’ – /usr/local/lib/php/extensions/no-debug-non-zts-20060613/pdo.so: cannot open shared object file: No such file or directory in Unknown on line 0
———————
Regards,
gm
gm10gm10 – as suggested in the other thread, what does your host say about that error?
Michael,
I just opened a ticket. I did not mark it “urgent” so it may take a few hours. As soon as I get anything, I will post it in this thread.
I got an email from tech support found that they fixed 404 problem. It did not fix WP though. I guess I have to wait until WP fixes its bug. No hurry for me since I was only attempting my first blog for a toy project.
Gotta agree with gm10gm10! There’s a bug there somewhere. We’ll just wait for an updated version and give it a try! Until then, we stick with 2.6.5.
Well, it’s nice to not be alone…
What does one do to get this on the list? The Trac is daunting to a newer user like myself.
Reporting Bugs explains how to report bugs. Use your forum login/password to login at Trac.
>Well, it’s nice to not be alone…
I got 2.7 running flawlessly with another host and switched my account there.
I can’t blame the first host for the lack of attention, but the issue seems to needs higher level of support and a dedicated person. Instead I was getting a prompt reply day or night, but from different people. Some of them didn’t even read my original ticket.
One observation. The host where I could not get 2.7 working properly was ahead in upgrading its software. Linux kernel, PHP, MySQL all of them had slightly higher the version number. Just an observation since I don’t know anything about all that software except it’s involved in wp running.
gm
gm10gm10,
Would it be possible to post your Linux kernel, PHP, and MySQL versions, as well as the php settings, from your new hosting account?
Or if anyone would post their php4 and php5 settings for a working 2.7, that would be great!
I have completely removed ALL files (including .htaccess) and databases from the domain I am working on. Restarted mysql and apache. My root directory is htdocs and I have created two diretories (wp6 and wp7) in htdocs.
htdocs/
htdocs/wp6
htdocs/wp7
I have put a phpinfo() file in all three directories and compared them. They are all three identical!
I installed 2.6.5 in htdocs/wp6. Everything works as it should. Changed the permalinks settings in the admin area. .htaccess file is properly created. Tested the site and Permalinks functions as it should. No problems with 2.6.5.
I installed 2.7 in htdocs/wp7. Everything works as it should. Changed the permalinks settings in the admin area. .htaccess file is properly created. Tested the site and get Error 404 – Not found.
Does any one know if there anything in the database that could create the permalinks issue, or is permalinks completely controlled via the .htaccess file?
Here is what fixed this for me:
In the 2.6.5 and 2.7 installation Permalinks settings I had Day and Name selected.
I then went into the working 2.6.5 database wp_options table (via phpMyadmin) and searched for the “rewrite_rules” on the option_name field. I then copied the option_value of “rewrite_rules” (2.6.5) and then went to the 2.7 database and replaced the value that was in the 2.7 database with that of the 2.6.5 value.
I then checked to see if I could change to the other permalinks settings and the 404 problem came back. So I changed my Permalink settings back to Day and Name, modified the database as above and the permalinks worked again.
Seems like a bug to me.
I am using php 4.4.9, apache 2.2.3, mysql 4.1.22
Hope this helps others!
Hey everyone,
I’m having the same problems as most of you seem to have. my custom structure is:
/%category%/%postname%/
just to make sure that it wasn’t server sided, I emailed my hosting service and this was the answer they provided:
Dear anhosting. I want to use my wordpress to create “Pretty Links”. The requirements for this however are:
# Apache web server with the mod_rewrite module installed
# In WordPress’s home directory,
* The FollowSymLinks option enabled
* FileInfo directives allowed (e.g. AllowOverride FileInfo, AllowOverride All)
Does my hosting plan meet these requirements?
to which they replied:
Hello,
Modrewrite and Fileinfo directives are enabled in the server.
I don’t have a wordpress 2.6.5 set up so i cannot use phpMyAdmin to fetch the values from the database.
As far as I know, all the settings are correct. WP made a .htacces file into which I edited the line options +followsymlinks in to see if it had any effect.
this is my htacces file.
options +followsymlinks
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
/end rant, will keep checking back the topic and good luck to everyone with the same problem 🙂
