Try re-saving your permalinks via Settings -> Permalinks in your blog’s Dashboard.
It sounds odd, but sometimes that needs to be kicked to re-generate the .htaccess file.
I have tried that a bunch! No good yet..
And you saved anything but default? Like, did you try “Day and name” for example?
At http://annapolisusnscc.org/seacadets/ every URL is presented as the default query string URL (like ?page_id=201).
If permalinks have been saved, even if .htaccess failed to update, the front-facing URLs would reflect the desired permalink (like /for-the-cadet/how-to-join/).
I tried to save as all other permalinks rather than the default to no avail. I see the URLs changing, but not getting rid of the redirect.
When you save the new permalinks, can you please check to see if a .htaccess file is created in the same directory as your wp-config.php file, and paste the contents of that in a reply here (use the “code” button when pasting it)?
You might need to enable invisible files in your SFTP or FTP client to see it.
I do not see the .htaccess file at all. I am using filezilla and I chose it to force showing hidden files. I also do not see a web.config file either. I only have wp-config.php…
When you re-save the permalinks, do you see a message about adding lines to your .htaccess file?
No, nothing it acts as if it was successful.
Try creating a text file titled .htaccess in the same directory as the wp-config.php file and /wp-content/ sub-directory with the following:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
Via: http://codex.wordpress.org/Using_Permalinks#Creating_and_editing_.28.htaccess.29
I have exactly the same problem but with me it was with a new website.
only the main page is visible and with the permalinks other than default the other page’s will not be found error 404 or redirect loop
checked with a older installation wordpress 3.8 and there was no problem so it must be 3.9.1
oh yes and i have a .htacces
running centos 6.5 with wordpress 3.9.1
