Hi…
Can you post the contents of your .htaccess file?
Have you used a redirect plugin by any chance? Has this behavior always existed or is it something new? If new, did you recently make a change.
We need more information.
🙂
Thank you for the quick reply, I will copy the .htaccess when GoDaddy fixes their server, ya – down again. No redirected plugins that I know. Do not know if this has been a problem in the past – all I know is some of my blogs are not indexing, and the other day I made a minor sentence change – went to preview it, and I noticed it was going homepage.
Is it safew to send .htacess file through this channel? no security issues with that?
Lee
Yes, safe to cut n’ paste your htaccess here. No security issues.
Let’s see what we have in that file.
Here is the plugins and settings
I’m gonna bet your “preview” issue has something to do with how large your .htaccess file is.
The original .htaccess for wordpress is very simple:
# 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
Source: http://codex.wordpress.org/htaccess
That’s it.
Compare to the file you pasted. BIG difference.
So, here’s what I would do. Save your current .htaccess somewhere safe. Then, create a new .htaccess, include just the snip above that we got from the codex and then see if that fixes your “preview” issue.
I betcha it will. And if it does, then you’ll know that your .htaccess is blowing something up. And more specifically, maybe it’s the BULLETPROOF .50.1 plugin that is modifying your .htaccess file.
Give that a shot and report back to us?
We’ll talk about plugins after you try the new .htaccess trick.
Cool?
I did what you asked and does the same thing. Sorry, was hoping it would work.
do you have logmein to see what I see
I did what you asked and does the same thing. Sorry, was hoping it would work.
Hrmmm…
Did you make sure you cleared out your cache on your browser _after_ you re-did the .htaccess file?
Gotta start with a clean slate.
No, Will do that . Thank you
Ok…so, let’s try this then:
Do you have a totally different browser you can use? Looks like you’re using FireFox…try “previewing” with Chrome or IE.
What happens?
