I was editing the .htaccess file to include the following (to track php errors)

# Catching PHP errors:
php_flag register_globals off

php_value error_reporting 2047
php_value display_errors true
php_flag display_startup_errors true
php_flag track_errors true

php_flag display_errors on
php_value error_reporting 7

And found the following code present, which I commented out as follows:

# php_flag display_errors on
# php_value error_reporting 6143
# Action php-cgi /cgi-bin/php4
# AddType application/x-httpd-php .php
# AddHandler php-cgi .php .phtml .php3

# Zend Optimizer htaccess handlers#
# AddHandler ZendOptimizer .php
# Action ZendOptimizer /cgi-bin/php-cgi-Oct-31-2011
# End of Zend Optimizer htaccess handlers#

I was then able to connect and login into wordpress.com.

I can't say for sure where this code came from. I will leave this open for another day, and then it can be marked resolved. Thank you.

That is unfortunate, and an unfortunate position to take. Since the error is unique to Jetpack, I would expect WordPress to take more interest in it.

We are actually very interesting in solving this issue, but unfortunately we need the server error logs in order to do so. If you ever manage to get those from the host, we'd be glad to take another look. Please start a new thread if that's the case, linking back to this one.

Nevertheless, I thank you personally for your followup on this (as yet) unresolved issue.

You're very welcome.

Of course I am also disappointed with the host, but they were previously selected by the client, so that is another issue. It may indeed be that I need to switch hosts, or at least host the WordPress portion on a different host.

Nevertheless, I thank you personally for your followup on this (as yet) unresolved issue.

I'm very sorry we couldn't resolve this for you.

Can you tell me if this escalation is in an "active" queue? That is, can you estimate when someone will look at this issue (days, weeks, months)?

Thanks.

http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

Depending on your server setup you may need to ask for your host's assistance, as not all hosts allow memory to be increased using this method.

Let me know if this helps.

Facebook (official) 1.1.5 (current version)
Twitter Widget Pro 2.4.1 (current version)

The appear to function correctly, that is, I can access their configuration pages.

Is there possibly a debug version of the compatibility test plug in, or could we include a BREAK in it for diagnosis?

I'll report back after I try another plug in.

So far, no plugins have run without some sort of error, is that right? Jetpack won't connect, the compatibility test doesn't work, and Akismet shows errors in your log. If you aren't able to successfully run any plugins on the site, it seems likely there's a configuration issue on your server, which your host would be best placed to diagnose.

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, or webmaster and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

(end)

I never see anything that would allow me to perform the compatibility test itself (configure parameters, start, etc.)

Could you please confirm that your Site URL and WordPress URL are both set to http://www.sportsactivitymd.com/blog - exactly that, with no trailing slash - under Settings > General?

Full data from debug.log:

[22-Nov-2012 00:06:38] PHP Notice: Undefined index: HTTP_REFERER in /services10/webpages/s/p/sportsactivitymd.com/public/blog/wp-content/plugins/akismet/akismet.php on line 323

[22-Nov-2012 00:06:41] PHP Warning: Cannot modify header information - headers already sent by (output started at /services10/webpages/s/p/sportsactivitymd.com/public/blog/wp-content/plugins/akismet/akismet.php:323) in /services10/webpages/s/p/sportsactivitymd.com/public/blog/wp-trackback.php on line 20

Paul

I now suspect that perhaps it is trying to write a file and failing? Maybe? Please see my earlier comment about trying unsuccessfully to enable debug.

Thanks for all for your assistance, I appreciate it greatly. Paul

1) Download the plugin from http://plugins.svn.wordpress.org/jetpack/branches/jetpack-compatibility-test.zip
2) Upload the plugin to your site via Dashboard -> Plugins -> Add New.
3) Activate the plugin and go to Plugins -> Jetpack Compatibility Test.
4) Click the "Select All" button.
5) Send the results of the test back in a reply.

I have attempted to enable debug using the following from word press documentation, but I find that the debug.log size remains at 0 bytes. (So I am suspicious that something is incorrectly configured.)

/**
* This will log all errors notices and warnings to a file called debug.log in
* wp-content only when WP_DEBUG is true. if Apache does not have write permission,
* you may need to create the file first and set the appropriate permissions (i.e. use 666).
*/

define('WP_DEBUG', true); // false
if (WP_DEBUG) {
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
define('SCRIPT_DEBUG', true);
@ini_set('display_errors',0);
}