Check Cached Resources Structure

[n7studios]

Summary

Fixes this reported issue, where the site in question had cached Kit Forms in a flat array, introduced in 1.6.0 and superseded by a more detailed array of form data in 1.9.6:

Example of how this should look:

3003590 => [
	'id'         => 3003590,
	'name'       => 'Third Party Integrations Form',
	'created_at' => '2022-02-17T15:05:31.000Z',
	'type'       => 'embed',
	'format'     => 'inline',
	'embed_js'   => 'https://cheerful-architect-3237.kit.com/71cbcc4042/index.js',
	'embed_url'  => 'https://cheerful-architect-3237.kit.com/71cbcc4042',
	'archived'   => false,
	'uid'        => '71cbcc4042',
],
2780977 => [
	'id'         => 2780977,
	'name'       => 'Modal Form',
	'created_at' => '2021-11-17T04:22:06.000Z',
	'type'       => 'embed',
	'format'     => 'modal',
	'embed_js'   => 'https://cheerful-architect-3237.kit.com/397e876257/index.js',
	'embed_url'  => 'https://cheerful-architect-3237.kit.com/397e876257',
	'archived'   => false,
	'uid'        => '397e876257',
],

This appears to happen when a creator either:

• upgrades from Plugin version 1.6.0 through 1.9.5.x to 1.9.6 or higher, or
• previously installed the Plugin version 1.6.0 through 1.9.5.x, uninstalled it and later installed a Plugin version 1.9.6 or higher

This PR resolves by:

• using the latest Kit WordPress Libraries, which won't load any cached resources and return exists() as false, if the cached resource structure is invalid,
• performing a check each time the Plugin is upgraded to ensure the cached resources are stored in the correct, expected array structure, removing them if not.

Testing

• UpgradePathsCest: Added tests to mimic the above screenshot example of cached resources from between 1.6.0 and 1.9.5.x, ensuring they're removed/updated as necessary, depending on whether the Plugin has a connection to Kit.

Checklist

• I have written a test and included it in this PR
• I have run all tests and they pass
• The code passes when running the PHP CodeSniffer
• Code meets WordPress Coding Standards for PHP, HTML, CSS and JS
• Security and Sanitization requirements have been followed
• I have assigned a reviewer or two to review this PR (if you're not sure who to assign, we can do this step for you)

[github-actions]

WordPress Playground

🚀 Your PR has been built and is ready for testing in WordPress Playground!

Click here to test your changes in WordPress Playground