HELP....cannot access posts after installing new plugins
 

I am using WP 2.92 and atahualpa 3.4.01.
I installed PHP speedy plugin and cleanup wordpress plugin. The front page of my site still looks as usual but when I click on a post I get the following error message:

The requested URL /blog/4-tips-for-building-trust-online was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.2.11 (Unix) mod_ssl/2.2.11 OpenSSL/0.9.8i DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at automarker.net Port 80

I uninstalled and deleted the plugins, but the error is still there. What should I do?

I appreciate any and all input!

Thanks,
Karin.

Can you give us the full URL?

I found that PHP Speedy was not a good citizen the one time I tried it. I can't recall the error it caused, though.

the url is http://automarker.net/blog. I just put up a page that says my blog is undergoing maintenance, since none of the links are working. If you need me to remove that so you can see what is going on let me know, but you can see that all links are broken by clicking on the social bookmarking tools tab inbetween the 2 home tabs at the top.

THanks for helping.

Karin.

if you can get to the backend, set the permalinks back to the default and see if you can access things

look at your .htaccess file
If I use 'http://automarker.net/blog/?p=10' I get to a page, so the htaccess is probably messed up.

Thanks so much. Yes that solved my problem. Is there anything more I should do to prevent this from happening again?

It looks like you switched back to the default permalinks. You should be able to switch back to what you had. If it doesn't work, then try renaming your .htaccess file and switching the permalinks back and forth.

I suspect one of the plugins overwrote the .htaccess with something and that messed things up.

how to prevent....???...don't use bad plugins....(I know - how do you tell what a bad plugin is - research it)

I'll bet it was PHP Speedy.