Calypso editor: do not set Calypsoify on Jetpack 9.2

[jeherve]

Changes proposed in this Pull Request

Calypsoify is currently broken in Jetpack 9.2:
Automattic/jetpack#17939

Until a point release is available, this may avoid creating Fatal errors on sites that do not have Calypsoify enabled yet.

Testing instructions

• Start from a Jetpack site (not Atomic) connected to WordPress.com and running Jetpack 9.2.
• Go to Jetpack > Settings and enable SSO
• Go to WordPress.com > Posts for that site
• Click on the button to start a new post.
• You should be redirected to the wp-admin editor without any Calypsoify styling.
• Now try the same thing with an Atomic site; the iFramed block editor should load instead of the redirection.

[matticbot]

Test live: https://calypso.live/?branch=update/gutenberg-editor-no-calypsoify

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~79 bytes added 📈 [gzipped])

name              parsed_size           gzip_size
gutenberg-editor       +212 B  (+0.0%)      +79 B  (+0.1%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[pablinos]

This pretty much works as we want, but I had Calypsoify activated and with this change, I was still getting the fatal error until I added &calypsoify=0 to the URL.

We might need to add this version check to getGutenbergEditorUrl as well (or instead) and ensure that parameter is added to the URL when necessary.

[jeherve]

We might need to add this version check to getGutenbergEditorUrl as well (or instead) and ensure that parameter is added to the URL when necessary.

I'm not quite sure how to do that. I tried adding the parameter there earlier, but that didn't seem to be taken into account. :\

[kbrown9]

I did a quick test on a Jetpack site, and it worked well on a site that did not already have Calypsoify enabled.

As expected, the fatal did occur if Calypsoify was already enabled on the site.