kirkpete

Thanks! The answer on the plug-in forum was, if the site already has https, it is safe to click the Activate SSL button. The system will detect that SSL is active, and will make no changes.

Fixed! It turns out it had nothing to do with plugins or themes. Because I had followed exactly the previous advice given, “delete then replace your copies of everything except the wp-config.php file and the /wp-content/ directory with fresh copies,” I lost my .htaccess file. Luckily I’d kept a complete backup of my blog from before the upgrade on my hard drive and was able to retrieve it from there. Everything is working now.

Thanks for the quick response. The easy way didn’t help, I’ll try redownloading and installing tomorrow.

Thanks! It was a plug-in. I guess maybe I should keep them up to date.

OK, the web host can’t/won’t give me access to the server logs, but their tech support said I could create my own server error logs, and they sent me an email explaining how to do that.

The text of their email is posted below. I don’t know what PHP script they are referring to — I’ve seen things that I think may be PHP scripts accessible through my WordPress dashboard, but the dashboard is not currently functioning properly. I also have no clue what they mean by the following instruction:

Include the file using “include()”)

(email begins below)
—————–
Since we don’t provide access to Apache error logs on shared hosting packages for
technical reasons, you can create your own error logs for debugging PHP Scripts.

Please insert the following code in your PHP script (or create separate file and
and add the code in it. Include the file using “include()”)

error_reporting(0);
$old_error_handler = set_error_handler(“userErrorHandler”);

function userErrorHandler ($errno, $errmsg, $filename, $linenum, $vars)
{
$time=date(“d M Y H:i:s”);
// Get the error type from the error number
$errortype = array (1 => “Error”,
2 => “Warning”,
4 => “Parsing Error”,
8 => “Notice”,
16 => “Core Error”,
32 => “Core Warning”,
64 => “Compile Error”,
128 => “Compile Warning”,
256 => “User Error”,
512 => “User Warning”,
1024 => “User Notice”);
$errlevel=$errortype[$errno];

//Write error to log file (CSV format)
$errfile=fopen(“errors.csv”,”a”);
fputs($errfile,”\”$time\”,\”$filename:
$linenum\”,\”($errlevel) $errmsg\”\r\n”);
fclose($errfile);

if($errno!=2 && $errno!=8) {
//Terminate script if fatal error
die(“A fatal error has occurred. Script execution has been aborted”);
}
}
————
(end of email)

Thanks — I’m afraid I’m not familiar with server error logs. My FTP site has a /logs subdirectory, inside which I find files named mail.log, http://ftp.log and access.log.25.6 — are any of those what I’m looking for?

The http://ftp.log is a 2+ meg text file, runs more than 1000 pages when I paste it into Word. The statements are in this format:

##.###.###.## UNKNOWN u######## [26/Jun/2010:01:17:27 -0500] “CWD /blog/wp-content/plugins/all-in-one-seo-pack/” 250 –
##.###.###.## UNKNOWN u######## [26/Jun/2010:01:17:27 -0500] “RMD images” 250 –
##.###.###.## UNKNOWN u######## [26/Jun/2010:01:17:27 -0500] “DELE readme.txt” 250 3480
##.###.###.## UNKNOWN u######## [26/Jun/2010:01:17:27 -0500] “CWD /blog/wp-content/plugins/” 250 –
##.###.###.## UNKNOWN u######## [26/Jun/2010:01:17:27 -0500] “RMD all-in-one-seo-pack” 250 –

… where I’ve inserted ## symbols to hide my IP and database ID. It’s complete gibberish to me, but I did notice that there are a lot of references to the all-in-one-seo-pack plug-in, which I don’t think was even doing anything anyway, so I’ve deleted that plug-in, and now I can get to my WP 3.0 dashboard and (I think) my other plugins are working. But when I click a link to upgrade a plugin, I get the same Server Error message again.