Parse.ly 3.0 release as default and call for testing for 3.1

The 3.0 version of the Parse.ly WordPress plugin was released on December the 15th, 2021, and made available to VIP customers that same day. Versions 3.0.1, 3.0.2, and 3.0.3 which addressed minor bugs, got released afterwards and made available to VIP customers as well. The Parse.ly 3.0 plugin contains breaking changes.

Currently, the 2.6 branch is the default for VIP sites that have Parse.ly enabled through VIP’s mu-plugins and don’t have any version pinned. On January 19th, 2022 we will switch the VIP platform default to 3.0. This change does not affect customers who don’t use Parse.ly or have a custom version uploaded.

If you want to try the version before that release date, you can do it with the following snippet:

add_filter(
	'wpvip_parsely_version',
	function() {
		return '3.0';
	} 
);

add_filter( 'wpvip_parsely_load_mu', '__return_true' );

If you want to skip this version and stay on the 2.6 branch, you can do it with:

add_filter(
	'wpvip_parsely_version',
	function() {
		return '2.6';
	} 
);

add_filter( 'wpvip_parsely_load_mu', '__return_true' );

wp-parsely 3.1 and decoupled support

We are also happy to introduce the next iteration on the Parse.ly plugin, version 3.1. This version does not contain any breaking changes with respect to 3.0. Its main feature is the introduction of support for decoupled WordPress architectures.

The 3.1 version will be made available in the WordPress.org plugin repository by the end of the week and as an option to VIP customers shortly after that. It won’t be the default version yet, but we encourage our customers, especially the ones with decoupled setups, to upgrade to it and test it on their sites.