I tried making it 777, then 644 and deleting all of the content of it. Neither changed the pages from ?=99 to /about
Is mod_rewrite running on the server?
Aha. Good question. I’m not able to see that, but I’ve asked the client. We’ll see what the answer is. I appreciate your assistance esmi!
Esmi, it is running and active. Any other ideas?
Have you checked the contents of the .htaccess file? Is it in the WP folder? Is this a Linux server?
“This is a new Red Hat Linux install with their version of Apache, in case that helps.”
.htaccess was in www/html/ but now seems to be gone. What should it say?
Upload an empty .htaccess file to the WP folder and ensure that it is writeable. Then set the reset the custom permalink structure up again via Settings->Permalinks.
it’s permission was set to 666, I tried to change permalink and still no luck. Any ideas? HTACCESS just say begin wordpress, end wordpress with #’s.
Sounds like it’s not being written to. Can you try changing the permissions on the file to 777 while you set up the custom permalinks?
it’s still not working. Is there anything else to try?
Try adding:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]
</IfModule>
# END WordPress
to the .htaccess file manually.
That didn’t help. I also tried
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
both at 777
One other thing you might check would be to just make sure that the FollowSymLinks option and AllowOverride directive have been added to, and properly configured in the virtual host container.
@claytonjames — How would I do that?
I know that AllowOverride is on and we rebooted the server after we switched it on…
but I’m not having any luck
