skadu

Issue still exists, we ran into this today when upgrading to the latest version. Has to roll back to the prior release.

Thanks Brian. I tried the prior version as well 4.300000013 and that was missing the entire quiz file I think? We are indeed running PHP 8 on this server. Do you need anything else from me to help? We wanted to evaluate this before we purchased the premium version.

Wow! That is awesome. Thank you very much for the quick reply and even faster resolution.

I will be sure to try it out when the next update comes along and let you know if it works. Really appreciate your help.

I also experienced this when using the standard plugin update process (not manually removing and installing as suggested), that should not need to happen for minor updates like this.

I can’t easily clear any transients since this breaks the entire admin interface…

I am running an OpCode cacher on my server, so my guess is that cache needed to be cleared (I commented out the UpSell feature calls in the plugin…selling me shouldn’t cause the plugin to break).

Got it. Thanks. I didn’t realize the security patches were available in 3.9.7, should have read the blog post closer:

We have prepared and shipped point releases for all twenty-one vulnerable branches of the Jetpack codebase: 2.0.7, 2.1.5, 2.2.8, 2.3.8, 2.4.5, 2.5.3, 2.6.4, 2.7.3, 2.8.3, 2.9.4, 3.0.4, 3.1.3, 3.2.3, 3.3.4, 3.4.4, 3.5.4, 3.6.2, 3.7.3, 3.8.3, 3.9.7, and 4.0.3. Downloads for each branch can be found here.

Sorry about that.

Thanks for the update Jeremy, although how are you sure that the files have actually updated? When I go look at the jetpack.php file, it still says that this is version 3.9.7:

/*
 * Plugin Name: Jetpack by WordPress.com
 * Plugin URI: https://jetpack.com
 * Description: Bring the power of the WordPress.com cloud to your self-hosted WordPress. Jetpack enables you to connect your blog to a WordPress.com account to use the powerful features normally only available to WordPress.com users.
 * Author: Automattic
 * Version: 3.9.7
 * Author URI: https://jetpack.com
 * License: GPL2+
 * Text Domain: jetpack
 * Domain Path: /languages/
 */

define( 'JETPACK__MINIMUM_WP_VERSION', '4.3' );

define( 'JETPACK__VERSION',            '3.9.7' );
define( 'JETPACK_MASTER_USER',         true );

That would explain the update nag, the update process is actually stuck going out and getting 3.9.7. Right?

Hi barates, I think your issue is actually slightly different. Your website is looking for the correct version (4.0.3 compared to your installed version of 4.0.2), but there is a connection failure over a secure channel. The issue being discussed here by myself and MrMountian is that Jetpack is downloading the same version that is installed

Is your website s.w.org?

Having the same exact issue. Running Jetpack 3.9.7. WordPress says update available, so I update it and receive the following:

The update process is starting. This process may take a while on some hosts, so please be patient.

Enabling Maintenance mode…

Updating Plugin Jetpack by WordPress.com (1/1)
Downloading update from https://downloads.www.ads-software.com/plugin/jetpack.3.9.7.zip…
Unpacking the update…
Installing the latest version…
Removing the old version of the plugin…
Plugin updated successfully.
Jetpack by WordPress.com updated successfully. Hide Details
Disabling Maintenance mode…

All updates have been completed.

The files are indeed downloaded and unpacked (the timestamps match on the server) but it just keeps download 3.9.7 instead.

WordPress version is 4.5.2, I was hoping to update to the latest version of Jetpack due to the security issue recently identified.

UPDATE 2014-08-18
It looks like the beta version of this plugin available here fixes the issue identified by this post, as well several other bugs.

This is certainly a bug with the plugin. By taking a look at the add_google_analytics function, I can see that the options for the “before code” is placed before the new Universal Analytics GA snippet is even placed on the page.

It’s a pretty simple matter of moving the conditional that checks to see if you have put any text in the “before code” box below the line that creates the tracker, and above the line that sends the pageview (which is where this “before code” should actually reside).

Now I know modifying a plugin is a terrible idea, however without the ability to provide patches, and since I have a desire to use a plugin and not just add the code to the head of my template, I will provide below a working chunk of code to fix this issue.

Here is the original section, with the incorrect placement (starting at line 1170 from the most recent version of the plugin, version 6.4.7.3):

# Add any tracking code before the trackPageview
    do_action('google_analyticator_extra_js_before');
    if ( '' != $extra )
            echo "	$extra\n";
	?>
	(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
	(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
	m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
	})(window,document,'script','//www.google-analytics.com/analytics.js','ga');

	ga('create', '<?php echo $uid; ?>', 'auto');
<?php if(get_option(key_ga_enhanced_link_attr) == ga_enabled): ?>
	ga('require', 'linkid', 'linkid.js');
<?php endif; ?>
	ga('send', 'pageview');
<?php if ($need_to_annon == '1' ): ?>
	ga('set', 'anonymizeIp', true);
<?php endif; ?>

Here is the updated version, with the code placed in the correct spot:

?>
	(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
	(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
	m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
	})(window,document,'script','//www.google-analytics.com/analytics.js','ga');

	ga('create', '<?php echo $uid; ?>', 'auto');
	<?php
	# Add any tracking code before the trackPageview
    do_action('google_analyticator_extra_js_before');
    if ( '' != $extra ){
    	echo "$extra\n";
    }
	?>
<?php if(get_option(key_ga_enhanced_link_attr) == ga_enabled): ?>
	ga('require', 'linkid', 'linkid.js');
<?php endif; ?>
	ga('send', 'pageview');
<?php if ($need_to_annon == '1' ): ?>
	ga('set', 'anonymizeIp', true);
<?php endif; ?>

Here is a diff file, if anyone is interested in patching the plugin:

--- google-analyticator/google-analyticator.php	Mon Aug 18 10:21:44 2014
+++ google-analyticator-new.php	Mon Aug 18 10:33:20 2014
@@ -1167,17 +1167,20 @@ function add_google_analytics()
 	})();
 <?php
 }else{
-	    # Add any tracking code before the trackPageview
-    do_action('google_analyticator_extra_js_before');
-    if ( '' != $extra )
-            echo "	$extra\n";
-	?>
+?>
 	(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
 	(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
 	m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
 	})(window,document,'script','//www.google-analytics.com/analytics.js','ga');

 	ga('create', '<?php echo $uid; ?>', 'auto');
+	<?php
+	# Add any tracking code before the trackPageview
+    do_action('google_analyticator_extra_js_before');
+    if ( '' != $extra ){
+    	echo "$extra\n";
+    }
+	?>
 <?php if(get_option(key_ga_enhanced_link_attr) == ga_enabled): ?>
 	ga('require', 'linkid', 'linkid.js');
 <?php endif; ?>

Hope this helps.