afwings
Forum Replies Created
-
Forum: Reviews
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Not compatible with 4.1I have filed a support ticket with them. I’ll let you know the result.
Forum: Reviews
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Not compatible with 4.1It’s crazy. I created a video so you can see (I paused the recording during the time I was connecting Jetpack to my WP.com account). Video’s 2:22, with no sound.
Forum: Reviews
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Not compatible with 4.1Ok, I got it to crash. My mistake earlier, it’s “Centralized Site Management” that causes it to crash. I still don’t have a debug.log in wp-content though.
Checking my Control Panel CGI logs, there are no fatals, and 3 warnings pertaining to this blog:
20150126T082108: www.fbgcofc.com/testing/wp-cron.php PHP Warning: Invalid argument supplied for foreach() in /hermes/waloraweb060/b2804/moo.fbgcofc/testing/wp-content/plugins/mojo-marketplace-wp-plugin/inc/user-experience-tracking.php on line 276 PHP Warning: Invalid argument supplied for foreach() in /hermes/waloraweb060/b2804/moo.fbgcofc/testing/wp-content/plugins/mojo-marketplace-wp-plugin/inc/user-experience-tracking.php on line 294 20150126T093517: www.fbgcofc.com/testing/wp-cron.php PHP Warning: Invalid argument supplied for foreach() in /hermes/waloraweb060/b2804/moo.fbgcofc/testing/wp-content/plugins/mojo-marketplace-wp-plugin/inc/user-experience-tracking.php on line 294This is a site hosted at FatCow, which I believe to be an awesome host, but every WP installation includes the Mojo Marketplace plug-in, which does seem to log a good many CGI errors. Not sure how this can be the cause of the crash when I try to implement the Centralized Site Management, but it’s all I’ve got.
Forum: Reviews
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Not compatible with 4.1I did that, but nothing exciting to report. I created a new blog strictly for the purpose of testing, and used that one for this debug test. I added
define( WP_DEBUG_LOG, true );
as the first line of code (beneath the <?php line), and never got the debug.log in the wp-content folder. I was able to activate single sign-on without error.Forum: Reviews
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Not compatible with 4.1Thanks. I did get my error logs, and although there are a good many of them labeled fatal, none of them relates to Jetpack. That’s strange though, because this has happened twice to me, the next thing that happens after I click the button to activate Single Sign On, the Admin control panel goes away, and is replaced by the 500 error. If it’s not Jetpack causing that, it’s awfully coincidental.
Here’s the typical fatal reference in my logs:
PHP Fatal error: Call to undefined function related_posts() in /hermes/waloraweb060/b2804/moo.<domain_name_here>/blog/wp-content/themes/orange-subway-10/index.php on line 22Since it was a new installation, I just deleted it and started over — and learned not to use Single Sign In.
Forum: Reviews
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Not compatible with 4.1I have the same issue, and I’ve seen TONS of posts all saying they’re getting a 500 error after enabling “Central Site Management”, yet I see no answers posted. Is that because (and I’m writing to Jeremy here, the Happiness Engineer) no one has followed your instructions and posted the error logs? I’ll be glad to do so — what am I looking for once I find the logs? They will no doubt be big.
Forum: Themes and Templates
In reply to: Heading HyperlinkThanks. I followed the instructions in your first reply and it worked like a champ.