Closed monsieur-z closed 3 months ago
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
fix/css-tidy-wraning
branch.
jetpack-mu-wpcom
changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true );
to your wp-config.php
file.To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack fix/css-tidy-wraning
bin/jetpack-downloader test jetpack-mu-wpcom-plugin fix/css-tidy-wraning
Interested in more tips and information?
jetpack rsync
command to sync your changes to a WoA dev blog.Thank you for your PR!
When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation :robot:
The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.
Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped. Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged. If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.
Jetpack plugin:
The Jetpack plugin has different release cadences depending on the platform:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.
Proposed changes:
On WordPress.com, the CSStidy library triggers a PHP warning:
Warning: Trying to access array offset on value of type
. This PR adds conditions inclass.csstidy-optimise.php
in thejetpack-mu-wpcom
package to prevent the warning. This PR alone doesn't fix the issue for WordPress.com. We'll need to ensure it loads CSStidy from thejetpack-mu-wpcom
package.Note: the changes are reflected in the Jetpack plugin as well for good measure, though the Custom CSS will soon be removed from the plugin.
Other information:
Jetpack product discussion
https://github.com/Automattic/vulcan/issues/362
Does this pull request change what data or activity we track or use?
No.
Testing instructions:
This one's hard to test. I don't know what path triggered a warning. Adding tests seems overkill as well, given the scope of the changes and that the method's not pure.
Code review should be sufficient.