loushou

Found the trac ticketing system. sorry.

Hrmm. Well, I originally only checked it in FF3.6; however, since you mentioned that it worked for you, I tried it in another browser, IE6, and voila! Perhaps I have a wonky plugin for FF installed. Meh. Ok I guess it works after all. LOL. Thanks for the help. ??

What he said. That would also be my last stitch effort.

does he have Javascript disabled by chance? Because the results you are getting sound very similar to what you would be if you have JS disabled.

The idea is to reset the wp_option that tells WP what plugins to activate. I would prefer if MacManX backed me up on this query, just to have a second set of eyes on it, but here is the query to run:

delete from wp_options where option_name = 'active_plugins' limit 1;

Remember that it is VERY VERY important to run exactly this query, even the ‘;’ because if you leave any one part out, the results could be catastrophic.

Once again, I would like MacManX to confirm it before you run it too, just because two eyes are better than one.

Do you have direct access to your database? This is a risky move, but we could do a master reset of your active plugins (in case one of them is the culprit). But know that you have to do it exactly right, especially if you have never logged directly in a database before. Just a last stitch option, you know.

??

Well, unfortunately, I still have not come up with any solutions for this on my own, nor through searching the internet for similar problems. So any expertise in this area at all, would be much appreciated.

Well, unfortunately, I still have not come up with any solutions for this on my own, nor through searching the internet for similar problems. So any expertise in this area at all, would be much appreciated.

Ok. So this is good news. So the next thing that I personally suspect with a 500 error is that something in the .htaccess file could be having an infinite loop. I know you said you did not change anything, but the next thing I would try, and only for a very short (2 minutes max) is rename your .htaccess file to something else like .htaccess.old . Then while it is changed, test your site. Then after your test rename the file back to .htaccess.

Now if it worked when you renamed the file, then the .htaccess is at fault, for sure. If you got the same result, then I would suggest exactly what MacManX suggested.

create a bogus file in your WP root folder called ‘test.html’, with the following:

hello there

then try to access that file via a browser at:

https://desired-sin.net/test.html

The reason for this, is because your web-server may not know where to find your WP install. At least with a test like this you can rule that option out.